similar to: [LLVMdev] llvm-gcc4 on Debian

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 On 8/14/06, Scott Michel <scottm at rushg.aero.org> wrote: > I know that Al Stone has compiled llvm-gcc4 successfully and I can > report the same. The problem I consistently run into is that llvm-gcc > ends up producing native

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

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

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, On 12/11/06, Scott Michel <scottm at rushg.aero.org> wrote: > Here's where my issue about DTRT with llvm-gcc (or whatever your prefix > to llvm tools happens to be) resurfaces. I'm keenly aware that Chris > thinks that one really ought to be careful with having llvm-gcc emit > bytecode. But frankly, if that's the case, what's the point of emitting > byte

Hi, I'm able to build the llvm tools on the MinGW platform: burg, fpcmp, tblgen, llvm-as, llvm-dis, opt, gccas, llc, llvm-link, lli, gccld, llvm-stub, analyze and extract. I wonder if these tools are sufficient to start build the cfrontend? Henrik. _________________________________________________________________ Undg� pop-ups med MSN Toolbar - http://toolbar.msn.dk hent den gratis!

Maybe it's because I've got a lot of two machine operand instructions and have to rely on the tied-to constraint, but I'm seeing a lot of dead reg-to-reg copy instructions, e.g.: ori $3, $3, 0 (Cell SPU's version of reg-to-reg copy, looks a lot like PPC, no?) Is there any way I can detect when this occurs, or is there code where this detection takes place in the target to which

Thank you, Reid, I tried llvm-gcc -lcrtend ary3.c -o ary3, but I get gccld: warning: Cannot find library 'crtend' gccld: warning: Cannot find library 'c' I have the libraries in my llvm directory: llvm/runtime/GCCLibraries/crtend Well, how do I link this to the LLVM runtime stuff? Before building from the source, I had copied all the .h from my old gcc 4.0 to

On Tue, 2 Nov 2004, Jeff Cohen wrote: > The problem with building the frontend on Windows is that gcc cannot be > bootstrapped using Window's native compiler -- i.e. VC++ -- unlike every > other platform. It can be built on Windows using gcc, of course, but > even then only if the entire GNU environment is present. Yeah, annoying. Unfortunately we're not up to fixing GCC :)

The problem with building the frontend on Windows is that gcc cannot be bootstrapped using Window's native compiler -- i.e. VC++ -- unlike every other platform. It can be built on Windows using gcc, of course, but even then only if the entire GNU environment is present. The real problem is that the bootstrapped frontend binaries built using gcc may not properly link with LLVM binaries built

On 1/18/07, Scott Michel <scottm at rushg.aero.org> wrote: > Is there any way I can detect when this occurs, or is there code > where this detection takes place in the target to which I can > refer? have you implemented InstInfo::isMoveInstr to recognize those? The register allocator uses that to find copies it can remove. Andrew

Reid Spencer wrote: > Yes, but its a bit verbose. The variables that control this are all > defined in the Makefile.config file. The variables are: > > PROJ_prefix := /proj/llvm/install-1 > PROJ_bindir := /proj/llvm/install-1/bin > PROJ_libdir := /proj/llvm/install-1/lib > PROJ_datadir := /proj/llvm/install-1/share > PROJ_docsdir :=

> Rebuilding llvm-gcc4 from source should work fine. Please see the > directions in the file README.LLVM at the top level src directory. You > can check llvm-gcc4 out from Subversion with the command: Dear guys, I've rebuild my llvm-gcc3 (not llvm-gcc4) from source, and now it can find stdlib.c and all the other sources, but I am having some other problems with the new

On 11/27/06, Scott Michel <scottm at rushg.aero.org> wrote: > Anton Korobeynikov wrote: > >>the official cutover. Granted, you might need darcs to pull the current > >>version out of its repo, since it was originally designed with darcs in > >>mind. > > > > I can confirm, that tailor converts LLVM CVS with all history preserved > > to mercurial

This didn't work as I tried with 197.parser. it works without "-Wl,-disable-opt" switch though. [197.parser]$ llvm-gcc analyze-linkage.c and.c build-disjuncts.c extract-links.c fast-match.c idiom.c main.c massage.c parse.c post-process.c print.c prune.c read-dict.c utilities.c xalloc.c word-file.c strncasecmp.c -Wa,-disable-opt -Wl,-disable-opt -lm -o llvm_parser [197.parser]$

On Sat, 1 May 2004, [koi8-r] "Valery A.Khamenya[koi8-r] " wrote: > there are two issues concerning invoking optimizations: > > 1. > this document: > http://llvm.cs.uiuc.edu/docs/GettingStarted.html > is very nice, it would be good though to add in a section > > An Example Using the LLVM Tool Chain > > examples on optimization step. That's an

Try adding -lcrtend to the gcc link line. You need to link in the LLVM runtime stuff. Reid. On Sun, 2006-08-20 at 14:30 -0700, Fernando Magno Quintao Pereira wrote: > > Rebuilding llvm-gcc4 from source should work fine. Please see the > > directions in the file README.LLVM at the top level src directory. You > > can check llvm-gcc4 out from Subversion with the command: >

Hi Erick, On Thu, 2006-12-07 at 23:31 -0800, Erick Tryzelaar wrote: > Hello, > > I'm updating the macports build of llvm, and I'm running into an issue > trying to stage llvm into a temporary directory. It builds fine, but > when I try to install it into a temporary location, it insists on > installing into the final location. Okay. > The only reference I saw

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

Branches have been created. You are free to checkin to cvs head again. I'll send mail once I have the prerelease tar balls up. Please continue to review and revise the documentation. I can fold this into the release later. Thanks, Tanya On Thu, 13 Apr 2006, Tanya Lattner wrote: > > I will be creating the release branch at 1:00pm PDT. Please refrain from > checking in from