similar to: [LLVMdev] __used__ attributes in llvm-gcc's crtstuff.c

Hello, > __used__ attributes in llvm-gcc/gcc/crtstuff.c. > GCC compiles crtstuff.c with -fno-toplevel-reorder option, which ensures > that > unused static globals are not removed during optimization. However, since > LLVM does not support that option, The problem is not that LLVM does not support this option. Though, this is indeed so due to certain reason. All the code is

Am Sonntag, den 30.03.2008, 10:28 -0700 schrieb Tanya Lattner: > On Mar 30, 2008, at 10:07 AM, Joachim Durchholz wrote: > > Look at how $LLVM_CONFIGURE is built, the final value is > > > > --prefix=/home/jo --enable-optimized --build=i686-pc-linux-gnu > > --host=i686-pc-linux-gnu --target=i686-pc-linux-gnu" > > > > This looks likes its missing some

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,

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 routinely fetch the latest LLVM and LLVM-GCC4 and recompile, perhaps every few days or so. I've not had success in some cases building LLVM-GCC4 on a Gentoo Linux host, for perhaps the last week or so. My system compiler is GCC 4.1.1. >>> cc1: /usr/src/llvm/llvm/include/llvm/Target/TargetInstrInfo.h:151:const llvm::TargetInstrDescriptor&

Andrew Purtell wrote: > I routinely fetch the latest LLVM and LLVM-GCC4 and recompile, perhaps every few days or so. I've not had success in some cases building LLVM-GCC4 on a Gentoo Linux host, for perhaps the last week or so. My system compiler is GCC 4.1.1. > > > cc1: /usr/src/llvm/llvm/include/llvm/Target/TargetInstrInfo.h:151:const llvm::TargetInstrDescriptor&

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

I get the output below on Ubuntu Hardy on ia32 from svn 56984. John make[2]: Entering directory `/home/regehr/llvm-gcc/build/gcc' /home/regehr/llvm-gcc/build/./gcc/xgcc -B/home/regehr/llvm-gcc/build/./gcc/ -B/home/regehr/i686-pc-linux-gnu/bin/ -B/home/regehr/i686-pc-linux-gnu/lib/ -isystem /home/regehr/i686-pc-linux-gnu/include -isystem /home/regehr/i686-pc-linux-gnu/sys-include -O2 -O2

Hi all, I'm having some trouble building llvm-gcc as of today, with and without bootstrap. The error I get is: /home/kooijman/src/llvm-gcc/obj/./gcc/xgcc -B/home/kooijman/src/llvm-gcc/obj/./gcc/ -B/home/kooijman/src/llvm-gcc/obj/../install/i686-pc-linux-gnu/bin/ -B/home/kooijman/src/llvm-gcc/obj/../install/i686-pc-linux-gnu/lib/ -isystem

Thanks, I've been through the documentation, and if I visit main, i think everything will turn out correctly... Printing out the Call graph reveals that main is calling this external node i think you are making reference to. Could this be the problem? Dave On Fri, 6 Dec 2002, Chris Lattner wrote: > > if you take the time to print out the function each non-looping node iter >

everyone-- I'm trying to build LLVM-GCC as a cross-compiler for a new target. I've successfully patched binutils, the FSF GCC, LLVM and Clang to build for this new target-- they work fine, but the LLVM-gcc build is failing for me. All my llvm.org sources are tracking the Subversion trunk, but my problem is probably not related to any ongoing churn there. I'm doing something

> if you take the time to print out the function each non-looping node iter > traverses, it never reaches main... Ok, first note that the CallGraph class does really stupid (but correct) things for function pointers, so you're not going to see anything remarkably nice here... Make sure to read the CallGraph.h comments to understand exactly what is going on. Despite that, I can verify

Test Cases: (attached) Iteration code: (...) typedef TarjanSCC_iterator<CallGraph*> MyTarjan; CallGraph& callGraph = getAnalysis<CallGraph>(); MyTarjan iter = tarj_begin(&callGraph); MyTarjan end = tarj_end(&callGraph); while(iter!=end) iter++; (...) if you take the time to print out the function each non-looping node iter traverses, it never reaches main...

> > ./configure in the llvm package will work on my amd64 machine > with this command line: > > ./configure --prefix=$HOME --enable-optimized \ > --build=i686-pc-linux-gnu CC=gcc-4.2 CXX=g++-4.2 > > Note that the CC and CXX flags are set on the command line, not as > environment variables - trying to submit them via the environment got me > all kinds of

(Apologies if this appears twice, it seems to not have made it into the list. I added an update for SVN trunk.) Just a quick heads-up for 2.2 and SVN trunk: ./configure in the llvm package will work on my amd64 machine with this command line: ./configure --prefix=$HOME --enable-optimized \ --build=i686-pc-linux-gnu CC=gcc-4.2 CXX=g++-4.2 Note that the CC and CXX flags are set on the command

Albert Graef wrote: > Jeff Kuskin wrote: >> Correct? If not, how do I call a LLVM JIT-generated fastcc function >> from a function statically compiled by GCC? > > Well, you can always generate a little wrapper function with C calling > convention which just calls the fastcc function. > I use the fastcall convention all the time. LLVM-jitted code calling GCC-compile

I'm creating a structure type which has a variable component. I'm not clear on the correct way to ensure the alignment of the variable part is correct and how to get the offset. For example, I have a wrapping structure format that looks like this: struct wrap: int32 ref_count PointerType(FunctionType) func_ptr T data Where 'T' is the desired extra data. I need to ensure that

On Mar 30, 2008, at 10:07 AM, Joachim Durchholz wrote: > > Am Sonntag, den 30.03.2008, 12:23 -0400 schrieb Daniel Berlin: >> To clarify, >> >> configure --host=i686-pc-linux-gnu --target=i686-pc-linux-gnu >> --target=i686-pc-linux-gnu >> >> I do this all the time on my 4 core amd64 box and it works fine. > > There must be some other difference, as

I try to build a cross powerpc compiler, but llvm-gcc fails. Eric Christopher wrote: > Looks like you don't have an assembler for your target installed that > llvm-gcc can find. I have binutils installed for powerpc and verified they are working with a simple hello world program. $ powerpc-750-linux-gnu-as --version GNU assembler 2.16.1 However, the xgcc build during the seems to

On Mar 30, 2008, at 12:39 PM, Joachim Durchholz wrote: > > Am Sonntag, den 30.03.2008, 10:28 -0700 schrieb Tanya Lattner: >> On Mar 30, 2008, at 10:07 AM, Joachim Durchholz wrote: >>> Look at how $LLVM_CONFIGURE is built, the final value is >>> >>> --prefix=/home/jo --enable-optimized --build=i686-pc-linux-gnu >>> --host=i686-pc-linux-gnu