similar to: [LLVMdev] Dumping SVN Repository

No, you can't generate a dump file from only a certain path in the repository, but each revision is a global (IE whole-repo) revision, even if we hide this well :) On 7/18/07, Bill Wendling <isanbard at gmail.com> wrote: > Hi all, > > I'm trying to dump the llvm-gcc repository so that it can be loaded > into the llvm.org repository instead of the mirror. However, I need

Hmm...okay. This poses a bit of a problem. The repository has a lot of other stuff in it. This begs the question, are we mega interested in the repository history of LLVM-GCC 4.0? If not, then we can just shove it into the normal repository without worrying about it. If we are, then... -bw On Jul 18, 2007, at 3:02 PM, Daniel Berlin wrote: > No, you can't generate a dump file from

The third 3.5 release candidate is now available. Please pick up sources and binaries here: https://llvm.org/pre-release/3.5 Run it through its phases and report any bugs you find! Share and enjoy! -bw

Looking forward to these changes! Thanks for working on it. On Fri, Oct 11, 2013 at 10:32 PM, Bill Wendling <isanbard at gmail.com> wrote: > Hi Dmitry, > > I can try my best, but it would be a bit tricky to get it all finished by > then... > > -bw > > On Oct 11, 2013, at 4:10 AM, Dmitry Babokin <babokin at gmail.com> wrote: > > Bill, > > Are there

On Wed, Jul 15, 2009 at 3:43 PM, Eli Friedman<eli.friedman at gmail.com> wrote: > On Wed, Jul 15, 2009 at 3:01 PM, Bill Wendling<isanbard at gmail.com> wrote: >> The core problem, in my opinion, is that people *don't* pay attention >> to the build bot failure messages that come along. > > That's largely because of the number of false positives. > There

FYI: http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-October/066389.html Please read and let me know you comments. -bw On Oct 11, 2013, at 2:47 PM, Dmitry Babokin <babokin at gmail.com> wrote: > Looking forward to these changes! Thanks for working on it. > > > On Fri, Oct 11, 2013 at 10:32 PM, Bill Wendling <isanbard at gmail.com> wrote: > Hi Dmitry, > > I

After several years as LLVM release manager, I’ve decided to step down as release manager. I recently haven’t been able to focus as much time on LLVM development as I should, and I don’t want the releases to suffer because of that. I’ve enjoyed all of the releases I’ve done. We have a great team of testers. And the community as a whole really helps out so that we can produce a great produce. I my

Have you been sleeping poorly worried about the Clang 3.5 release? Well, this may help! The plan right now is to start testing in July with August as the target release month. There isn’t a schedule yet, of course. But it should be a goodly amount of time for all y’all to prepare for the release process. If you have any questions, please let me know. If you’d like to volunteer to be a tester,

On 9/25/07, Daniel Berlin <dberlin at dberlin.org> wrote: > On 9/24/07, Bill Wendling <isanbard at gmail.com> wrote: > > On Sep 24, 2007, at 3:15 PM, Dale Johannesen wrote: > > > > Weird. I see a potential problem, though. The code is like this: > > > > void dumpToDOUT(SparseBitVector<> *bitmap) { > > dump(*bitmap, DOUT); > > } >

Hi all, In the last few days, some change introduced an internal compiler error. On my G4 (PPC), I'm getting this: $ cat testcase.i struct A {}; struct B { struct A c[0]; }; extern const struct B *pB; void bork(void) { const struct A *pA = pB->c; } $ /Users/wendling/llvm/llvm-gcc-4.2.obj/./gcc/xgcc -B/Users/wendling/ llvm/llvm-gcc-4.2.obj/./gcc/ -B/Users/wendling/llvm/llvm-

On Sep 24, 2007, at 3:15 PM, Dale Johannesen wrote: > > On Sep 24, 2007, at 3:07 PM, Bill Wendling wrote: > >> A debug or release build? >> >> -bw > > Both, actually. Weird. I see a potential problem, though. The code is like this: void dumpToDOUT(SparseBitVector<> *bitmap) { dump(*bitmap, DOUT); } where dump expects an llvm::OStream& for the

Hi Developers, This is to clarify which patches may be merged into the 3.5 branch. * All doc changes may go in. In fact, you’re encouraged to update the branch's ReleaseNotes.rst file! :-) * All non-documentation patches should first receive approval from the appropriate code maintainer. (A blanket approval is acceptable for the first phase of testing.) * If your patch fixes a major bug,

Bill, Are there any chances that you complete it before 3.4 is branched? On Thu, Oct 10, 2013 at 10:16 PM, Bill Wendling <isanbard at gmail.com> wrote: > On Oct 10, 2013, at 4:22 AM, Dmitry Babokin <babokin at gmail.com> wrote: > > > Bill, > > > > Thanks for answering. To make sure that we are on the same page, let's > agree on definitions :) Here, by

Hi, Attached is the final version of the patch, adding the requested FIXME. If this is ok, can somebody check it in ? thanks Zoltan On Tue, Dec 9, 2008 at 9:58 PM, Bill Wendling <isanbard at gmail.com> wrote: > On Tue, Dec 9, 2008 at 6:11 AM, Zoltan Varga <vargaz at gmail.com> wrote: >> Hi, >>

Thanks Bill! But it does not work. I get the error given below when I try to load LLVMExecutionEngine.o in the opt command. Error opening '../../../build/Release/lib/LLVMExecutionEngine.o': ../../../build/Release/lib/LLVMExecutionEngine.o: only ET_DYN and ET_EXEC can be loaded -load request ignored. Any ideas?? Please help me out here. Thanks, Bhavani --- On Sun, 10/26/08, Bill

Hello again! I took a stab at PR4898[1]. The attached patch improves Clang's __builtin_constant_p support so that the Linux kernel is happy. With this improvement, Clang can determine if __builtin_constant_p is true or false after inlining. As an example: static __attribute__((always_inline)) int foo(int x) { if (__builtin_constant_p(x)) return 1; return 0; } static

Yes, this is me. I'll look at this tonight when I have access to a machine. Evan On Jan 27, 2008, at 1:01 AM, Bill Wendling <isanbard at gmail.com> wrote: > Hi all, > > In the last few days, some change introduced an internal compiler > error. On my G4 (PPC), I'm getting this: > > $ cat testcase.i > struct A {}; > struct B { > struct A c[0]; > };

Hi Dmitry, I can try my best, but it would be a bit tricky to get it all finished by then... -bw On Oct 11, 2013, at 4:10 AM, Dmitry Babokin <babokin at gmail.com> wrote: > Bill, > > Are there any chances that you complete it before 3.4 is branched? > > > On Thu, Oct 10, 2013 at 10:16 PM, Bill Wendling <isanbard at gmail.com> wrote: > On Oct 10, 2013, at

Hi all, The OCaml stuff is failing during the "make install" command: $ make install llvm[0]: Installing HTML documentation llvm[0]: Building ocamldoc documentation make[2]: Nothing to be done for `ocamldoc'. make[2]: Nothing to be done for `ocamldoc'. make[2]: Nothing to be done for `ocamldoc'. make[2]: Nothing to be done for `ocamldoc'. make[2]: Nothing to be done for

This is just a reminder that the 3.5 release will be starting up in July. Most likely the 2nd week. Details will come later. But you can help things along. * Be sure to update the READMEs! * Try to get your new features in good working condition. * Tackle some of the bugs in the bugzilla. Focus on mis-compilations. * And update the READMEs!! Share and enjoy! -bw