similar to: [LLVMdev] Bootstrapping llvm-gcc4 on Mingw

Hello, Everyone. I'm currently trying to bootstrap llvm-gcc4 on mingw32 platform. Everything (except some small fixes) seems to be fine: stage1 finished successfully. I'm linking with debug variant of LLVM, since linker bug prevents release builds. Unfortunately, stage2 failes immediately with this cryptic message: $/f/tmp/llvm/gccbuild/gcc/xgcc -B/f/tmp/llvm/gccbuild/gcc/

At the last step of building llvm for arm target, I am unable to build llvm-gcc. I am trying the follwing options:   $ ../llvm-gcc/configure --target=arm-linux --enable-pic --program-prefix=llvm- --prefix=/llvm/install --disable-multilib --disable-optimized --enable-bindings =none --enable-llvm=$PWD/../llvm-2.8 --enable-languages=c,c++ --disable-bootstr ap   Then I get the following error when I

Hi, I can''t install eventmachine on Debian Lenny. ruby-dev and build-essential are installed. Where''s the problem? My (awful) logs: ============================= # gem i eventmachine Building native extensions. This could take a while... ERROR: Error installing eventmachine: ERROR: Failed to build gem native extension. /usr/bin/ruby1.8 extconf.rb checking for

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

Anton Korobeynikov <asl at math.spbu.ru> writes: [snip] > 2) Problem: Complains about gthr-default.h file. > Resolution: Grab gcc/gcc/gthr-win32.h file and copy it to gthr-default.h ... so --enable-threads=win32 is broken... good to know. > 3) Problem: Complains about "CL_ObjCXX" and simular ("CL_") during > compilation

Hello, all. Just found this file in my e-mail atchive, hope it will be useful for somebody. ===cut=here=== Some small rules: 1) No blankspace in the paths to the top-level directories. 2) Add paths to binaries to your system PATH variable. 3) Use short paths to top-level directories. 1. Some checks & preparations. 1) Be sure, that you're using right make version: $ make

Andrew Lenharth wrote: > Interestingly, in the .i file there are 2 __builtin_alloca, and > EmitBuiltinAlloca is only being called once. > > Hmm, here EmitBuiltinAlloca gets called twice, but it looks like validate_arglist is rejecting the args both times. I have 2 calls to alloca generated: $ grep alloca x.bc|grep call %tmp21 = call i8* @alloca( i64 %tmp20 ) nounwind

I'm trying to build an app with clang against libraries that are using GCC 4.1 ABI. I'm getting an error "weakref declaration must have internal linkage" Now I'm stumped though, perhaps it is an incompatibility between clang trunk and gcc 4.1 include files? - I've built clang from trunk - fixed include paths to point to gcc 4.1 include paths When I modify clang to use

Evan Cheng wrote: > Hi, > > Here is the follow on patch for this problem. Please apply this from > the top of the tree and rebuild. With the patch from Chris and then the patch from you combined, the previous error disappeared, but I get another error, reduced to this: ./cc1 -fpreprocessed libgcc2.i -quiet -dumpbase libgcc2.c -mtune=pentiumpro -auxbase-strip libgcc/./_clz.o -g -O2

See the bug for a reduction and the gimple trees. validate_arglist definately is rejecting the arglist in EmitBuiltinAlloca. (try: bool TreeToLLVM::EmitBuiltinAlloca(tree exp, Value *&Result) { tree arglist = TREE_OPERAND(exp, 1); if (!validate_arglist(arglist, INTEGER_TYPE, VOID_TYPE)) { debug_tree(arglist); return false; } Value *Amt = Emit(TREE_VALUE(arglist), 0); Amt =

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,

I am new to LLVM, what do you mean by Duncan? Btw, I installed llvm from the repository: sudo apt-get install llvm llvm-gcc Eric Christopher-2 wrote: > > Looks like something wonky with DragonEgg. > > Duncan? > > -eric > > On Mar 21, 2011, at 7:05 PM, stackunderflow wrote: > >> >> Hi Eric, >> >> here is my -emit-llvm -S -v output:

On Oct 30, 2008, at 11:02 PM, Chris Lattner wrote: > On Oct 30, 2008, at 5:23 PM, Jack Howarth wrote: >> ps We do have one oddity left in llvm-gfortran from current llvm >> svn. I find everytime I compile something with llvm-gfortran that >> I get a series of warning messages... >> >> f951: warning: command line option "-Wformat" is valid for C/C++/

Hi Eric, > Looks like something wonky with DragonEgg. you need to use -fplugin-arg-dragonegg-emit-ir or -flto with dragonegg, not -emit-llvm. Also, you currently have to use -S (getting human readable IR) rather than -c because with -c gcc will run cc1 with -S (getting human readable IR) then pass the result to the system assembler which of course barfs. This is documented on the web-page

dear community, sorry for posting again a beginner's question but i can't find a solution on my own. i installed all llvm and llvm-gcc4 in a directory called "~/programs/llvm/install" in my home folder. i can build a test c - file as follows: ~/programs/llvm/install/bin/gcc -v -o test test.c Using built-in specifications. Target: i686-pc-linux-gnu Configured with:

Looks like something wonky with DragonEgg. Duncan? -eric On Mar 21, 2011, at 7:05 PM, stackunderflow wrote: > > Hi Eric, > > here is my -emit-llvm -S -v output: > > Using built-in specs. > COLLECT_GCC=gcc-4.5 > COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-linux-gnu/4.5.1/lto-wrapper > Target: i686-linux-gnu > Configured with: ../src/configure -v

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 Eric, here is my -emit-llvm -S -v output: Using built-in specs. COLLECT_GCC=gcc-4.5 COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-linux-gnu/4.5.1/lto-wrapper Target: i686-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 4.5.1-7ubuntu2' --with-bugurl=file:///usr/share/doc/gcc-4.5/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr

Hi, I am new to LLVM, so I am sorry if the question I am going to ask has already been raised before. I will be thankful if anyone can describe me a quick way to search relevant topics within the list archive, When I am trying to compile a simple code, containing access to std::string, with clang: #include <string> int main() { std::string s; return

On Fri, Oct 31, 2008 at 10:38:50AM -0700, Mike Stump wrote: > On Oct 31, 2008, at 9:40 AM, Jack Howarth wrote: >> However in current llvm svn, when I compile code with llvm-gfortran, I >> get these warning >> flags passed by default so that I get bogus warnings of... >> >> f951: warning: command line option "-Wformat" is valid for C/C++/ >>