similar to: [LLVMdev] Multiple Returns

Hi all, I just wanted to know if anyone's looked into using the free version of Microsoft's Visual C++ toolkit for LLVM: http://msdn.microsoft.com/visualc/vctoolkit2003/ -bw -- || "If wishes and buts were clusters of nuts, we'd all have a bowl of || granola!" - Mr. Jellineck

Chris Lattner wrote: } > I tend to agree. I'm a strong advocate of XML myself (on other } > projects). However, introducing XML would make LLVM dependent on some } > kind of XML parser. We could probably get away with expat (small, fast) } > for our purposes in LLVM, but there is still the issue of dependency. To } } To me, it's not a matter of "one more

Henrik Bach wrote: } Hi John, } } configure still exits, when checking for uint64_t. I've attached a patch, } that properly will fix it. Either uint64_t or u_int64_t will succeed: } } Index: configure.ac } =================================================================== } RCS file: /var/cvs/llvm/llvm/autoconf/configure.ac,v } retrieving revision 1.106 } diff -u -r1.106 configure.ac } ---

Hi all, I had a quick question. I think it's possible to do this, but just wanted to make sure. It is possible to extend LLVM to add, say, matrix operations at a higher level and then "lower" them into some version of LLVM "proper" after performing any transformations on them, right? Also, it's possible to have any custom-made types (like "matrix") as well?

Hi Reid, > Since there's been little feedback on the design document I sent out, > some decisions are being made in order to progress the work. If you have > strong feelings about any of these, voice them now! > > 1. Name = llvmcc I like llvmcc, but really have no strong opinion. > 2. The config file format will resemble Microsoft .ini files > (name=value in

Hi all, I get this warning during compilation: make[3]: Entering directory `/home/wendling/llvm/llvm/lib/ExecutionEngine/JIT' Compiling Emitter.cpp Emitter.cpp:44:1: warning: "_POSIX_MAPPED_FILES" redefined In file included from /usr/include/unistd.h:171, from /usr/include/c++/3.3.1/i586-mandrake-linux-gnu/bits/gthr-default.h:38, from

On Mon, 2 Aug 2004, Reid Spencer wrote: > Hi Bill, > On Mon, 2004-08-02 at 21:31, Bill Wendling wrote: > > Hi Reid, > > > > > Since there's been little feedback on the design document I sent out, > > > some decisions are being made in order to progress the work. If you have > > > strong feelings about any of these, voice them now! > > >

Hi John, configure still exits, when checking for uint64_t. I've attached a patch, that properly will fix it. Either uint64_t or u_int64_t will succeed: Index: configure.ac =================================================================== RCS file: /var/cvs/llvm/llvm/autoconf/configure.ac,v retrieving revision 1.106 diff -u -r1.106 configure.ac --- configure.ac 2 Sep 2004 18:44:44 -0000

LLVM Developers, We've added a page to the main web site that provides links to each LLVM Developer's home page and/or personal LLVM Notes page. You can find it here: http://llvm.org/Developers.html or just click the link titled "LLVM People" on the left of the main page. The list isn't complete but contains pictures and links for everyone that responded in IRC this morning

Hello, is there any documentation for LLVM codebase other than produced by doxygen? The reason I'm asking is that doxygen docs are (1) not very complete at the moment, as lot of classes don't even have a description (2) is generally not the best way to get high-level view of a big codebase. As an example, consider this code: %tmp.1 = setgt int %i, 0 br bool %tmp.1, label

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

An Investor ALERT is being issued starting right N0W. Keep your eyes glued on PSUD!! Explosive pick for our members! PETROSUN DRILLING (PSUD) Current Price: 1.13 Don't get caught in the dust, start watchin today because this company has been known to release major news at any time which could bring the st0ck up!! Current News PetroSun Named Title Sponsor of The Independence Bowl

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 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); > > } >

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

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

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

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,

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-