similar to: [LLVMdev] gcc4 or gcc3?

Hi Hendrik, On Mon, 2006-08-07 at 14:35 -0400, Hendrik Boom wrote: > I just downloaded the CVS version of llvm and llvm-test. Presumably > this is the one that's scheduled to become 1.8 in a few days. Not really. The current CVS head is quite a ways past release 1.8 at this point. If you want to get the release 1.8 preview, please check out the release_18 branch: cvs co -rrelease_18

On Mon, 07 Aug 2006 11:45:04 -0700, Reid Spencer wrote: > Hi Hendrik, > > On Mon, 2006-08-07 at 14:35 -0400, Hendrik Boom wrote: >> I just downloaded the CVS version of llvm and llvm-test. Presumably >> this is the one that's scheduled to become 1.8 in a few days. > > Not really. The current CVS head is quite a ways past release 1.8 at > this point. If you

Hello Hendrik Mon, 07 Aug 2006 14:35:25 -0400 you wrote: > (1) To install llvm, do I really need the llvm version of the gcc > front end? I have no special interest in yet another c/c++ conmpiler. No. This will only need, if you want to turn your C\C++ sources to LLVM bytecode. > (4) The page http://llvm.org/docs/GettingStarted.html#checkout says > to get the gcc 3.4 source code.

On Tue, 2007-16-01 at 02:50 +0000, Reid Spencer wrote: > > The build instructions provided tell me to build llvm-gcc first from > > the source. > > The source for that tells me to build llvm first from the source. I'm > > not sure where to go from this point. > You should build llvm first, then llvm-gcc. When I build LLVM first, however, I get told that it

On Wed, Aug 23, 2006 at 06:38:36PM -0700, Scott Michel wrote: > There should also be a large notice in 40 point font and bold that says, > "gcc4 does not produce byte code by default: you must use the -emit-llvm > flag to get LLVM byte code." =) Where -is- that documented? The only reason I know about it is because of how many times it's come up on the list. =) (Which

On Aug 23, 2006, at 7:00 PM, Emil Mikulic wrote: > Where -is- that documented? > > The only reason I know about it is because of how many times it's come > up on the list. =) http://llvm.org/docs/GettingStarted.html ? ... Example with llvm-gcc4 First, create a simple C file, name it 'hello.c': #include <stdio.h> int main() { printf("hello

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

Devang Patel wrote: > > On Aug 23, 2006, at 7:00 PM, Emil Mikulic wrote: > >> Where -is- that documented? >> >> The only reason I know about it is because of how many times it's come >> up on the list. =) > > http://llvm.org/docs/GettingStarted.html ? > > ... > Example with llvm-gcc4 > First, create a simple C file, name it

Chris Lattner wrote: > Patches welcome. Please send a patch, or even just some suggested > text, and we'll be happy to include it. Remember that the people who > usually end up writing the FAQ's already know all the answers, so it's > hard for us to see things from fresh perspectives sometimes :) > > -Chris > Actually, my request for more info in the

Erick Tryzelaar wrote: > Actually, my request for more info in the "Getting Started" had some > hidden questions, as I don't know the answer to them :) So to be a > little more clear, here are the two I had: > > Does the gcc4 no longer need the "fixheaders" script that the gcc3.4 > frontends uses? > > Is it possible to install both the gcc4 and

Hi, On Nov 13, 2006, at 9:17 PM, Tanya M. Lattner wrote: > I assume you have an Mac with an Intel processor. Yes. Sorry, I forgot to mentioned it in the mailbody. > Download this: > http://llvm.org/releases/1.8/llvm-gcc4-1.8-x86-darwin.tar.gz I think that is the same tarball I used before. > Let me know if that doesn't work. Again: there is no fixheader-script like you

Hi! Apparently there are no precompiled binaries for llvm-gcc 4.0 for Linux. I've tried downloading the sources and building according to http://llvm.org/docs/CFEBuildInstrs.html (except I'm not an elite gcc hacker). I tried following the guidelines and got what looks like a gcc for x86 with no traces of LLVM. I tried passing --enable-llvm with various llvm root pathnames and got ICEs.

Chris Lattner wrote: > > This looks like you're compiling llvm-gcc3, which is quite dead by now. > Please follow these instructions: > http://llvm.org/docs/CFEBuildInstrs.html > > Oups, sorry for that. Here is the error message with the latest svn version: gcc -c -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic

>> I assume you have an Mac with an Intel processor. > > Yes. Sorry, I forgot to mentioned it in the mailbody. > >> Download this: >> http://llvm.org/releases/1.8/llvm-gcc4-1.8-x86-darwin.tar.gz > > I think that is the same tarball I used before. Ok. I'm confused. Do you want llvm-gcc3 or llvm-gcc4? The tarball above is a binary for llvm-gcc4 for Mac x86. You

I'm trying to get LLVM1.9 working on my Ubuntu 6.10 system. The LLVM version in the repositories is 1.7 and I've never managed to get it successfully working because whoever packaged it thought it would be fun to rename everything. This means I can't use it to build 1.9 and I've therefore decided to try bootstrapping a 1.9 build. Yes, I've looked at the docs where it said

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

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. The only reference I saw to the standard gnu DESTDIR was in the llvm.spec file, but none of the generated Makefiles have that value. Is

Scott Michel wrote: > That part about "native" -- yeah, it's there. The existence predicate > returns true. IT'S SOMETHING THAT IS EASILY SKIPPED OVER WHEN SKIMMING > THE DOCUMENT BECAUSE, HECK, THE GCC3 DRIVER COMPILES DIRECTLY TO > BYTECODE SO WHY DOESNT GCC4? > > It's a "least surprise" issue. If gcc3 produces bytecode directly, why > did the

> Well, it depends on the configure parameter used while building llvm- > gcc. Hmm, there are other pages on the the website that tell you how you should configure gcc, e.g. you're led from "How to build the C/C++ Frontend" at http://llvm.org/docs/CFEBuildInstrs.html to Subversion HEAD (by virtue of an "svn co"). Then you're supposed to look at README.LLVM. And

Hi Michael, On Tue, 2007-01-16 at 10:24 +0800, Michael T. Richter wrote: > I'm trying to get LLVM1.9 working on my Ubuntu 6.10 system. The LLVM > version in the repositories is 1.7 and I've never managed to get it > successfully working because whoever packaged it thought it would be > fun to rename everything. This means I can't use it to build 1.9 and > I've