similar to: [LLVMdev] New GCC4-based C/C++/ObjC front-end for LLVM

Chris Lattner wrote: > > Hi Everyone, > > I just pushed out the latest version of my new GCC4-based llvm-gcc here: > http://gcc.gnu.org/ml/gcc/2006-01/msg00931.html > This email includes status and instructions for use. The instructions seem to have one path wrong. It says to get: svn://gcc.gnu.org/svn/gcc/branches/apple/trunk/gcc, revision 108127. but the patch

On Wed, 1 Mar 2006, Vladimir Prus wrote: >> I just pushed out the latest version of my new GCC4-based llvm-gcc here: >> http://gcc.gnu.org/ml/gcc/2006-01/msg00931.html >> This email includes status and instructions for use. > > The instructions seem to have one path wrong. It says to get: I'll put together a tarball today. That will be easier than dealing with a

Chris Lattner wrote: > On Wed, 1 Mar 2006, Vladimir Prus wrote: >>> I just pushed out the latest version of my new GCC4-based llvm-gcc here: >>> http://gcc.gnu.org/ml/gcc/2006-01/msg00931.html >>> This email includes status and instructions for use. >> >> The instructions seem to have one path wrong. It says to get: > > I'll put together a

On Fri, 17 Mar 2006, Vladimir Prus wrote: > Finally, will it be possible to provide an updated snapshot of the frontend, > so that I don't have to apply several patches to get it building? Sorry for the delay, yes, here you go: http://nondot.org/sabre/2006-03-23-llvm-gcc-4.tar.gz -Chris -- http://nondot.org/sabre/ http://llvm.org/

Chris Lattner wrote: > On Mon, 6 Mar 2006, Vladimir Prus wrote: >> ../../2006-03-02-llvm-gcc-4/gcc/llvm-convert.cpp:1305: error: parse > error >> before `__attribute__' > > Can you send me the preprocessed .i file for this file? Sure, I've sent it by private email (180K is too big for list). > To work around the above error, just remove

Chris Lattner wrote: > On Thu, 16 Mar 2006, Vladimir Prus wrote: >> Ah, hell, as soon as I've send this email I've updated from CVS to find >> that the issue was fixed by Jim several hours after I reported the crash, >> by making MachineDebugInfo don't check for empty name of type. > > :) > >> Here's what I get now: >> >>

On Mon, 6 Mar 2006, Vladimir Prus wrote: > ../../2006-03-02-llvm-gcc-4/gcc/llvm-convert.cpp:1305: error: parse error > before `__attribute__' Can you send me the preprocessed .i file for this file? To work around the above error, just remove "ATTRIBUTE_UNUSED" from that line. > ../../2006-03-02-llvm-gcc-4/gcc/llvm-convert.cpp: In function `tree_node* >

On Thu, 16 Mar 2006, Vladimir Prus wrote: > Ah, hell, as soon as I've send this email I've updated from CVS to find that > the issue was fixed by Jim several hours after I reported the crash, by > making MachineDebugInfo don't check for empty name of type. :) > Here's what I get now: > >

Vladimir Prus wrote: > So, it looks either the snapshot is not in stable state, or there's > something seriously wrong with type name handling. At this point I gave up > on quickly fixing this, so I've applied the third attached patch to LLVM, > which "fixes" this issue completely. Ah, hell, as soon as I've send this email I've updated from CVS to find that

Chris Lattner wrote: > Here's a new snapshot of the front-end: > http://nondot.org/sabre/2006-03-14-llvm-gcc-4.tar.gz > > This: > > 1. Fixes the inline asm problem you have above. > 2. Includes patches to make it better on Alpha's (thanks to patches by > Andrew Lenharth). > 3. Sync's it up with debug info changes in LLVM CVS (by Jim Laskey). > 4.

Chris Lattner wrote: > On Thu, 2 Mar 2006, Chris Lattner wrote: >>> Any ideas what could be wrong? >> >> Sorry for the delay, please try this tarball: >> http://nondot.org/sabre/2006-03-02-llvm-gcc-4.tar.gz > > Actually, do to a recent change in CVS, this tarball will probably not > work anymore. Please apply the attached (small) patch on top of it in >

On Thu, 2 Mar 2006, Chris Lattner wrote: >> Any ideas what could be wrong? > > Sorry for the delay, please try this tarball: > http://nondot.org/sabre/2006-03-02-llvm-gcc-4.tar.gz Actually, do to a recent change in CVS, this tarball will probably not work anymore. Please apply the attached (small) patch on top of it in the gcc directory. Worth noting, this front-end only works

Chris Lattner wrote: > On Thu, 2 Mar 2006, Vladimir Prus wrote: >>>> The instructions seem to have one path wrong. It says to get: >>> >>> I'll put together a tarball today. That will be easier than dealing >>> with a patch, and it will include a bunch of bugfixes since the previous >>> email. >> Further into process, I get this error:

>> Sorry for the delay, please try this tarball: >> http://nondot.org/sabre/2006-03-02-llvm-gcc-4.tar.gz > > There's some confusion with --enable-llvm configure parameter. I've built > LLVM to a separate build dir. The source is ~ghost/Work/llvm-cvs and build > dir is /space/p2/ghost/build/llvm-cvs ... > So, it seems like, at the same time: > > 1. buildir

Hi, Here is the follow on patch for this problem. Please apply this from the top of the tree and rebuild. -------------- next part -------------- A non-text attachment was scrubbed... Name: op Type: application/octet-stream Size: 2548 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20060315/eee8a766/attachment.obj> -------------- next part

Evan Cheng wrote: > Hi, > > Here is the follow on patch for this problem. Please apply this from > the top of the tree and rebuild. With the patch from Chris and then the patch from you combined, the previous error disappeared, but I get another error, reduced to this: ./cc1 -fpreprocessed libgcc2.i -quiet -dumpbase libgcc2.c -mtune=pentiumpro -auxbase-strip libgcc/./_clz.o -g -O2

On Wed, 15 Mar 2006, Vladimir Prus wrote: >> Please give it a try and let me know if it works any better for you! > > Here we go: Wow, you are good at finding problems! Thanks! > -fvisibility=hidden -DHIDE_EXPORTS > -c ../../2006-03-14-llvm-gcc-4/gcc/libgcc2.c -o libgcc/./_fixunsxfdi.o > cc1: /space/p2/ghost/build/llvm-cvs/include/llvm/Instructions.h:72: void >

On Thu, 2 Mar 2006, Vladimir Prus wrote: >>> The instructions seem to have one path wrong. It says to get: >> >> I'll put together a tarball today. That will be easier than dealing with >> a patch, and it will include a bunch of bugfixes since the previous email. > Further into process, I get this error: > In file included from

I'm getting a build error when trying to build gcc4 from sources. This is for the recent 1.9 release. How I built llvm-1.9: ----------------------------- tar zxf llvm-1.9.tar.gz cd llvm-1.9/ ./configure --prefix=/custom/llvm-1.9 make ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION='-O2' tools-only make install How I built gcc4: ----------------------------- export

There was a patch that went thru for this recently from Rafael Espindola. The fix is on the mirror. Index: gcc/dwarf2out.c =================================================================== --- gcc/dwarf2out.c (revision 120589) +++ gcc/dwarf2out.c (working copy) @@ -14361,9 +14361,8 @@ s->refcount++; /* Avoid unnecessarily putting strings that are used less than twice in the hash