search for: llvmgcc4

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...

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...

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...

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/...

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,...

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 > routines to ge...

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 t...

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, pleas...

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 Chris, is there any chance that the new frontend will support dynamic loading of backends? I.e: llvm-g++ -load my_backend.so -march=my_arch a.c ? Thanks, Volodya

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. >...

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

This should build with mainline, includes some performance tweaks, better build support for mingw, detects a faulty --enable-llvm configure option, and has better support for the Darwin/X86 ABI: http://nondot.org/sabre/2006-05-20-llvm-gcc-4.tar.gz -Chris -- http://nondot.org/sabre/ http://llvm.org/

On Sat, 2006-05-20 at 19:22 -0500, Chris Lattner wrote: > This should build with mainline, includes some performance tweaks, better > build support for mingw, detects a faulty --enable-llvm configure > option, and has better support for the Darwin/X86 ABI: Any functional changes for non-Darwin or am I ok continuing to use the last snapshop? Andrew

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

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

...horrible and ugly options like -Wa,-disable-opt. The new front-end is a step in a much better direction. :) The equivalent to: $ llvm-gcc3 -Wa,-disable-opt hsat.c -o hsat.bc -c is now: $ llvm-gcc4 -O0 hsat.c -o hsat.bc -c -emit-llvm To turn on (some) optimizations, you can pass -O[123] to llvmgcc4. Beware that I haven't gotten around to installing the full optimization pipeline in llvm-gcc4 though, so to get the equivalent of: $ llvm-gcc3 hsat.c -o hsat.bc -c I suggest using: $ llvm-gcc4 -O3 hsat.c -o - -S -emit-llvm | gccas > hsat.bc This will run exactly the same set of optimi...

...) > And I personally think it may possiblely puzzle other users, > maybe it deserves its place in FAQ or in man page for LLVM. I agree that this is an ugly issue. You've basically fallen into the "llvmgcc3 doesn't work the way a normal compiler does" problem. If you use llvmgcc4, it is completely transparent, and works just like a native compiler, unless you provide the -emit-llvm switch. If you'd like for this stuff to work, I'd suggest *not* using the gccld "-native*" switches. They are really only built to work when the whole program is compiled w...

Hi Reid, I am using llvmgcc4-1.9 for x86 linux, and I got my version of LLVM from CVS repository. Are these versions not compatible? Thanks, Joy. -- Joy W. Kamunyori Graduate Student - Computer Science Dept. University of Virginia jkamunyori at cs.virginia.edu "Life must be understood backwards; but... it must be liv...

Hi, I have tried another way: ar rcs libsysdeputil.a sysdeputil.o gccld seems to recognize the file type. However, it stills find unresoved symbols which are actually the functions in sysdeputil.o (can be find out with `nm libsysdeputil.a`) The problem disappears if native gcc/ld tool chain is used. As another test, main.c: ----------------- extern void foo(); int main() { foo(); return

On Fri, 16 Jun 2006, James Supancic wrote: > I am having some trouble getting llvm to build. > I found some strange stuff going on in gcc/f/com.* This sounds like you enabled the fortran frontend, which isn't supported. Please read the README.LLVM file in the root directory of the llvmgcc4 source distro. -Chris > In com.h I find > ffeinfoKindType ffecom_gfrt_basictype ( ffecomGfrt ix); > yet, in com.c I see > ffeinfoBasicType ffecom_gfrt_basictype ( ffecomGfrt gfrt) > > I tried changing the line in com.h to > ffeinfoBasicType ffecom_gfrt_basictype ( ffecomGfrt...