similar to: [LLVMdev] updating the "Getting Started" page with more info about the gcc4 frontend

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

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." Erick Tryzelaar wrote: > Hello, > > It looks like the "Getting Started" is missing some info about the gcc > 4.0 frontend. Since it doesn't follow the setup of the cfrontend/gcc3.4 >

Erick Tryzelaar wrote: >> It's a "least surprise" issue. If gcc3 produces bytecode directly, why >> did the gcc4 driver create such a large departure from original, >> expected functionality? It's a rhetorical question, BTW. >> > > I actually know this one :) I believe the powers that be decided that > having a gcc-compatible interface was

On Thu, 24 Aug 2006, Scott Michel wrote: > That's why I would either make sure that the difference is highlighted > in the FAQ and that the difference is highlighted in the "Getting > Started" pages. Otherwise, it'll remain a mailing list FAQ. Patches welcome. Please send a patch, or even just some suggested text, and we'll be happy to include it. Remember that

Hi, I wanted to install llvm 1.8 and the frontend at my MacBook Pro but I think the gcc4 frontend doesn't work (gcc3 and llvm 1.8 works fine on my old ppc-based mac). There are no fixheaders-script and no include directories ... Are there working gcc 4 binaries? Did I miss some informations on the llvm-webpage? Or do I have to build my own gcc frontend? Thank you Nico

> I wanted to install llvm 1.8 and the frontend at my MacBook Pro but I > think the gcc4 frontend doesn't work (gcc3 and llvm 1.8 works fine on > my old ppc-based mac). There are no fixheaders-script and no include > directories ... > Are there working gcc 4 binaries? Did I miss some informations on the > llvm-webpage? > Or do I have to build my own gcc frontend? I assume

http://trac.xiph.org/cgi-bin/trac.cgi/ticket/583 looking at why gcc4 could increase vorbis so much, i first had a look at the compiler options, and i saw -O20, as far as i know there is -O0, .. -O3 and -Os but no -O20. changing that to -O2 (patch attached) one gets close to the result of gcc-3.4. gcc3.4-O20.ogg 20423 gcc4-O20.ogg 54623 gcc4-O3.ogg 54623 gcc4-O2.ogg 20423 looking

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

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

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

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

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

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

Hi there, Is it possible to use GCC 3.4 with LLVM 2.0? I tried to compile GCC 3.4 with LLVM 2.0 and get following error message: /scratch/spa_llvm-2.0/llvm-gcc3.4-1.9.source/build/gcc/xgcc -B/ scratch/spa_llvm-2.0/llvm-gcc3.4-1.9.source/build/gcc/ -B/scratch/ spa_llvm-2.0/llvm-gcc3.4-1.9.source/install/i386-pc-solaris2.11/bin/ - B/scratch/spa_llvm-2.0/llvm-gcc3.4-1.9.source/install/i386-pc-

On Nov 14, 2006, at 8:30 AM, 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. > > Ok. I'm

Thank you for the help. There seem to be several things in my makefiles that are messed up as a result of switching from the gcc3.4 front end to the gcc4 frontend. Is there any documentation listing the things that have changed? Thanks, Ryan Ryan M. Lefever [http://www.ews.uiuc.edu/~lefever] On Fri, 1 Dec 2006, Reid Spencer wrote: > Hi Ryan, > > On Fri, 2006-12-01 at 18:06

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 format output; it does not produce bytecode, nor does it invoke gccas or gccld. I'm using the latest svn, and my configure args are: --prefix=/work/scottm/llvm-cfrontend/obj/../i686-pc-linux-gnu \

Hi Warren, you can try to configure with the following export CFLAGS="-m64" export LDFLAGS="-L/usr/lib64" LLVM: ../src/configure --prefix=`pwd`../install --enable-optimized --enable-jit --enable-targets=host-only make LLVM-GCC: ../llvm-gcc4-2.0.source/configure --prefix=`pwd`../install --program-prefix=llvm- --enable-llvm=/home/warren/llvm/obj/ --enable-languages=c,c++

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