similar to: [LLVMdev] Re: Patches and some potential bugs

Hi, i tried compiling llvmgcc4 on x86_64-linux. The two changes i needed to apply to llvm and llvmgcc4 are attached. Those two patches tell llvmgcc4 to use the x86 code-generator for x86_64 and give x86_64-* targets a score of 10 for the x86 backend when trying to find appropriate backends. Now i'm getting stuck during the compile when an assertion is triggered: make[3]: Leaving

llvmgcc4 emits LLVM byte code before executing GCC optimizations, so one can say that llvmgcc4 disables all GCC optimizations. On Jul 31, 2006, at 11:01 AM, Zhiru Zhang wrote: > Hi, > I am trying to turn on the new GCC auto-vectorization feature > within llvmgcc4. Below is the command I used, but nothing was > vectorized. Does it mean that llvmgcc4 has disabled this >

On Jul 31, 2006, at 11:14 AM, Vikram Adve wrote: > Does llvmgcc4 convert the high-level AST to LLVM (like llvmgcc3x) > or does it go from GIMPL to LLVM? If the latter, would it be > possible to allow some TreeSSA optimizations before emitting LLVM? llvmgcc4 intercepts high-level GCC trees to GIMPLE tree transformation routines to get trees that are suitable for LLVM byte code.

Does llvmgcc4 convert the high-level AST to LLVM (like llvmgcc3x) or does it go from GIMPL to LLVM? If the latter, would it be possible to allow some TreeSSA optimizations before emitting LLVM? --Vikram http://www.cs.uiuc.edu/~vadve http://llvm.cs.uiuc.edu/ On Jul 31, 2006, at 1:10 PM, Devang Patel wrote: > llvmgcc4 emits LLVM byte code before executing GCC optimizations, > so one

Hi, I am trying to turn on the new GCC auto-vectorization feature within llvmgcc4. Below is the command I used, but nothing was vectorized. Does it mean that llvmgcc4 has disabled this optimization and all I can do is to embed SSE intrinsics in the source code by hand? Thanks! ./llvm-gcc4-x86/bin/llvm-gcc -c -O2 -ftree-vectorize -msse -ftree-vectorizer-verbose=5 -emit-llvm vec.c -o vec.bc

On Mon, 31 Jul 2006, Devang Patel wrote: > On Jul 31, 2006, at 11:14 AM, Vikram Adve wrote: >> Does llvmgcc4 convert the high-level AST to LLVM (like llvmgcc3x) or does >> it go from GIMPL to LLVM? If the latter, would it be possible to allow >> some TreeSSA optimizations before emitting LLVM? > llvmgcc4 intercepts high-level GCC trees to GIMPLE tree transformation

On Thu, 16 Nov 2006, Tanya M. Lattner wrote: >> * I don't think this is ready for release. In particular the llvm-gcc4 >> binary >> seg faults on FC 5 for most of llvm-test programs. >> * I'm going to re-try without using the binaries and building >> everything from scratch. > > Does llvm-gcc4 seg fault for make check? I've done extensive

Chris Lattner wrote: > > Hi All, > > There's a new snapshot of llvmgcc4 available here: > > http://nondot.org/sabre/2006-05-08-llvm-gcc-4.tar.gz > > This release includes the various portability fixes contributed on > llvmdev, includes fixes to build with mainline CVS (and, thus, *requires* > mainline CVS), and includes various other bug fixes. > > If

Hi All, There's a new snapshot of llvmgcc4 available here: http://nondot.org/sabre/2006-05-08-llvm-gcc-4.tar.gz This release includes the various portability fixes contributed on llvmdev, includes fixes to build with mainline CVS (and, thus, *requires* mainline CVS), and includes various other bug fixes. If you're interested, please try it out. Thanks, -Chris --

I am trying to compile the cfrontend for gcc3, not gcc4. I did ./configure --prefix=/opt/llvmgcc --enable-languages=c,c++ After adding the --enable-languages flag I get "xgcc: installation problem, cannot exec `gccas': No such file or directory" It is true, I don't have gccas in my PATH, nor does the file gccas appear in my cfrontend directory. Is my configuration wrong, yet

The gcc4 tree is in svn. We believe it should be straight forward to create a public svn image but it will be late next week before we can set it up (minimal svn experience between Chris and myself.) Cheers, -- Jim On May 15, 2006, at 3:12 AM, Vladimir Prus wrote: > Chris Lattner wrote: > >> On Sat, 13 May 2006, Vladimir Prus wrote: >>>> If you're

Hi, Last night's attempt to build llvmgcc4 with svn head ends in this . This is on an x86 FC5 environment. /home/ramana/llvm/llvmgccfrontend/llvmgcc4-source/build-llvmgcc/gcc/xgcc -B/home/ramana/llvm/llvmgccfrontend/llvmgcc4-source/build-llvmgcc/gcc/ -B/home/ramana/llvm/install-llvm/i686-pc-linux-gnu/bin/ -B/home/ramana/llvm/install-llvm/i686-pc-linux-gnu/lib/ -isystem

On Sat, 13 May 2006, Vladimir Prus wrote: >> If you're interested, please try it out. > I get this with LLVM CVS: > Adding: > #include "llvm/Target/TargetData.h" > Fixed this. Right, thanks. > Chris, any change you'll make gcc4 frontend source available from some CVS? > Then, I can put together a script to build it every night, to make sure > things

Chris Lattner wrote: > On Sat, 13 May 2006, Vladimir Prus wrote: >>> If you're interested, please try it out. >> I get this with LLVM CVS: >> Adding: >> #include "llvm/Target/TargetData.h" >> Fixed this. > > Right, thanks. > >> Chris, any change you'll make gcc4 frontend source available from some >> CVS? Then, I can

Reid Spencer wrote: > Chandler/Domagoj, > > On Sun, 2006-12-10 at 10:53 -0500, Chandler Carruth wrote: > >>Unless I'm missing something, the problem lies directly with the fact >>that you are trying to do a link-stage operation with the GCC >>frontend. GCC, by default, probably runs "ld" or another system >>linker, which grabs the executable from

Chandler/Domagoj, On Sun, 2006-12-10 at 10:53 -0500, Chandler Carruth wrote: > Unless I'm missing something, the problem lies directly with the fact > that you are trying to do a link-stage operation with the GCC > frontend. GCC, by default, probably runs "ld" or another system > linker, which grabs the executable from binutils. This linker hasn't > been modified

Hi, I connected a multi-homed Win95 machine (carrot, see below) to two networks (ankh-net and morpork-net) which a multi-homed Linux machine running Samba 1.9.18p10 (or whatever the latest <2 is) was also connected to (vimes) and wanted to see which of the two interfaces Win95 would pick... --------------------------------- ankh-net 134.225.241.0/24 | |

First, thanks for testing this! > Here's the results for GNU/Linux, 2.6.18-1.2200.fc5smp (Fedora Core 5) > > HIGH LEVEL COMMENTS > * The llvm-1.9.tar.gz file unpacks to a dir named "llvm". Shouldn't > that be llvm-1.9? We have always labeled the dir just llvm which is fine. If you build llvm it will know its version 1.9. > * LLVM was built in Release mode

Ryan Brown wrote: > I don't think llvm-gcc4 uses gccas or gccld, but it can emit bytecode > if you give it the --emit-llvm option: > llvm-gcc --emit-llvm -c -o foo.bc foo.c That's a bit asymmetric with the previous gcc3 version, isn't it? That would mean that the "An Example Using the LLVM Tool Chain" section needs to be updated for the gcc4 frontend. OTOH, I could

On Fri, 2 Jun 2006, Nai Xia wrote: > And the command lines: > > llvm-gcc -c -o main.o main.c > gcc -o foo.o foo.c > ar rcs libfoo.a foo.o > llvm-gcc -Wl,-native main.o -L. -lfoo > > It's *OK* > > Thanks in advance for solving my problem. :) > And I personally think it may possiblely puzzle other users, > maybe it deserves its place in FAQ or in man page for