similar to: [LLVMdev] gcc 4 frontend binary for mac os x x86

> 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

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

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

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

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 all, I've run into problems compiling the llvm-gcc frontend on x86_64. Is this not supported, or am I making an error somewhere? The procedure I followed was: 1. Download LLVM 2.0 source as a tarball (from a few days ago, during the testing phase). 2. Download the llvm-gcc4 source today, as a tarball. 3. Extract both. 4. Configure LLVM as: ../src/configure --prefix=`pwd`../install

Hi Warren, You have the -m32 flag set, but it's still giving you this: > Warning: Generation of 64-bit code for a 32-bit processor requested. > Warning: 64-bit processors all have at least SSE2. But are you sure you want to compile the LLVM-GCC source? You should use the binaries unless absolutely necessary. -bw On May 24, 2007, at 10:34 PM, Warren Armstrong wrote: > Hi all,

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

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 package, a couple sections describing the front end don't cover the gcc4 package. Here are the couple things I'd wish could be fleshed out a bit more: Under "Getting Started Quickly (A Summary)", it'd be nice

This is an libpath problem. When xgcc runs it wants to dynamically link the libgcc.so. When you run it from the command line it will find your system libgcc.so (which works) and so you don't see the segfault. When you run xgcc from the Makefile, it will have set LD_LIBRARY_PATH to get your <cfebuilddir>/gcc directory which will find the libgcc.so that it just built, which is the one

Hi Robert, On Mon, 2006-11-06 at 12:45 -0800, Robert Mykland wrote: > Reid, > > Here's the backtrace you asked for: > > (gdb) bt > #0 0x0862d65c in llvm::LiveVariables::runOnMachineFunction () Hmm, this is a little strange. Your LLVM build is non-debug (there's no line numbers or arguments in any of the llvm related calls). However, your llvm-gcc build seems to have

Hi Robert, Please make sure that you: 1. Completely rebuild LLVM (make clean; make reconfigure; make tools-only) 2. Completely rebuild llvm-gcc (wipe out the build dir with rm -rf, configure llvm-gcc and rebuild it) If you've done that, then please enter the debugger and get a stack trace for us. You will need to: 1. Capture the xgcc compile command that failed 2. Run that command

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=utf-8" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Reid,<br> <br> Here's the backtrace you asked for:<br> <br>

Thank you Patrick! For anyone interested, I was able to get the mainline version of DSA to compile with the mainline version of LLVM. As Patrick pointed out, the mainline version of PoolAllocate does not compile with the mainline version of LLVM. So, I made a small change to llvm-poolalloc/lib/Makefile in which I removed PoolAllocate from the line: PARALLEL_DIRS=DSA PoolAllocate After

On Nov 14, 2006, at 1:07 AM, Nico Moser wrote: >> If you want to emit >> llvm bytecode be sure to pass -emit-llvm to llvm-gcc. > > Thats the next point: > $ llvm-gcc4-1.8-x86-darwin/bin/gcc -v -emit-llvm main.c > .... > /usr/bin/ld: unknown flag: -emit-llvm > collect2: ld returned 1 exit status The linker does not know how to link llvm-byte code. If you add -c on

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=us-ascii" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> <b>Reid,<br> <br> I followed the steps but got stuck as described

I was having video problems, so upgraded my Linux box from SUSE 9.3, where LLVM frontend 4 source built fine, to SUSE 10.1, where I got the error message: ../../llvm-gcc4-1.8-source/gcc/libgcc2.c:541: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://llvm.org/bugs> for instructions. This version of SUSE