similar to: [LLVMdev] Fwd: PPC Nightly Build Result

Hi Bill, this might be a latent bug related to PPC. I have no such machine to access atm., but I shall be able to reproduce the problem when back at home. (In about 4 hours). I keep you informed. Cheers, Gabor On Mar 4, 7:57 pm, Bill Wendling <wendl... at apple.com> wrote: > Something last night broke the build on Darwin PPC. Possible Gabor's   > check-in? > > -bw

FYI: It also showed up for ARM yesterday, but only for a non-debug build. On Mar 5, 2009, at 4:32 AM, Gabor Greif wrote: > Hi Bill, > > this might be a latent bug related to PPC. I have no such > machine to access atm., but I shall be able to reproduce the > problem when back at home. (In about 4 hours). > > I keep you informed. > > Cheers, > > Gabor >

Hi all, There's been a recent bootstrap failure that might be covered up because of another failure. I just wanted to point this out so that people can take a look: -bw Here's the failure from our buildbot: Assertion failed: (DestReg == VirtReg && "Unknown load situation!"), function RewriteMBB, file /Volumes/Sandbox/Buildbot/llvm/build.llvm-

g++ -m32 -c -g -O2 -mdynamic-no-pic -DIN_GCC -W -Wall -Wwrite-strings - pedantic -Wno-long-long -Wno-variadic-macros -Wmissing-format- attribute -Werror -mdynamic-no-pic -DHAVE_CONFIG_H -Wno-unused - DTARGET_NAME=\"i686-apple-darwin9\" -DNDEBUG -I. -I. -I/tmp/ llvmgcc42.roots/llvmgcc42~obj/src/gcc -I/tmp/llvmgcc42.roots/ llvmgcc42~obj/src/gcc/.

Can you bootstrap llvm-gcc (configure with --enable-bootstrap)? Ciao, Duncan.

Hello, I’m trying the following thing: • build and install llvm with mgcc (system compiler) • build and install llvm-gcc with mgcc • build llvm with llvm-gcc • deinstall llvm(old), install llvm(new) • build llvm-gcc with llvm-gcc(old) • deinstall llvm-gcc(old), install llvm-gcc(new) However, I have the problem that the llvm-gcc(new) does not work: after it is compiled, it tries to build libgcc2

Hi sir, I have built the test suits in following steps: 0. $cd LLVM_GCC_DIR; $gunzip --stdout llvm-gcc-4.2-*version*-* platform*.tar.gz | tar -xvf - 1. $cd SRC_DIR/llvm-2.8/projects 2. $svn co http://llvm.org/svn/llvm-project/test-suite/trunk test-suite 3.$cd OBJ_DIR; 4. $SRC_DIR/configure --prefix=INS_DIR --enable-debug-runtime --disable-optimized --enable-debug-symbols

While attempting to build llvm-gcc-4.2 from llvm-2.7 release branch, I am finding that the build fails at... c++ -g -O2 -mdynamic-no-pic -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wmissing-format-attribute -mdynamic-no-pic -DHAVE_CONFIG_H -o f951 \ fortran/arith.o

llvm itself is built with gcc-4.0, but the run line is: // RUN: %llvmgxx -S -O0 -emit-llvm %s -o - | grep retval | grep S242 | grep {i32 1} | count 2 According the log: FAIL: /Volumes/Muggles/LLVM/nightlytest-pic/build/llvm/test/C+ +Frontend/2008-02-13-sret.cpp Failed with exit(1) at line 1 while running: /usr/local/bin/llvm-gcc -emit-llvm -S -O0 -emit-llvm /

Hi all, I was installing a package *RBGL* of bioconductor. However, I had some issues while installing it. I asked the devel group of bioconductor and they told me to consult this group. Here is my conversation with the bioconductor group related to the problem *Me->* I was trying to install the RBGL package using the following command biocLite("RBGL") However, I got the

Hi, > I am confused. Shouldn't the gcc 4.2 front-end build behave > just like the FSF gcc build. The first stage builds the compilers > and the second stage rebuilds them using those from the first > stage? the FSF gcc requires you to build the C compiler (I think - will check). Thus a newly built C compiler is always available to build later stages. We can't reasonably

I'm still trying to debug the validator buildbot. I'm getting this error when building some variants of llvm-gcc-4.2: /bin/sh ../../src/gcc/mkconfig.sh bconfig.h gcc -c -g -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wmissing-format-attribute -fno-common

Duncan, I am confused. Shouldn't the gcc 4.2 front-end build behave just like the FSF gcc build. The first stage builds the compilers and the second stage rebuilds them using those from the first stage? Jack On Mon, Aug 11, 2008 at 03:56:23PM +0200, Duncan Sands wrote: > > I don't be that can be the cause because I have... > > > >

The curent llvm svn (r54623) is unable to link the gfortran compiler in llvm-gcc-4.2 svn. I am getting the error... c++ -g -O2 -mdynamic-no-pic -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wmissing-format-attribute -mdynamic-no-pic -DHAVE_CONFIG_H -o f951 \

See below. This is on Ubuntu Hardy on ia32. Thanks, John make[3]: Entering directory `/home/regehr/llvm-gcc/build/gcc' gcc -c -g -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wmissing-format-attribute -DHAVE_CONFIG_H -I. -I. -I../../gcc -I../../gcc/.

As you all have undoubtedly noticed, I recently did Yet Another Merge to Apple's GCC top-of-tree. This merge was prompted by several important fixes in the "blocks" implementation. There are still many testcases that need to be moved over, but those can come at our leisure. I compiled both the "Apple way" and the "FSF way". It also passed the tests in

On 2009-04-03 18:39, David Greene wrote: > I'm still trying to debug the validator buildbot. > > I'm getting this error when building some variants of llvm-gcc-4.2: > > /bin/sh ../../src/gcc/mkconfig.sh bconfig.h > gcc -c -g -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes > -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros >

I first install the gcc-4.2.4 . then I set CC and CXX export CC= "path of my gcc-4.2.4" export CXX="path of my g++-4.2.4" after that , I config and make . error occur like this : /home/ws/software/gcc-4-2/bin/gcc -c -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros

Hi, every body, I get stuck when trying to build llvm-gcc4.2-2.4 on x86_64 Linux with GCC-4.3.3. I meet this error: make[3]: Entering directory `/home/wangtielei/TOOLS/llvm/llvm-gcc-obj/gcc' /home/wangtielei/TOOLS/llvm/llvm-gcc-obj/./prev-gcc/xgcc -B/home/wangtielei/TOOLS/llvm/llvm-gcc-obj/./prev-gcc/ -B/usr/local/x86_64-unknown-linux-gnu/bin/ -c -g -O2 -DIN_GCC -W -Wall -Wwrite-strings

I'm getting the error below on Ubuntu Hardy on ia32 on r55688. John make[3]: Entering directory `/home/regehr/llvm-gcc/build/gcc' gcc -c -g -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wmissing-format-attribute -DHAVE_CONFIG_H -I. -I. -I../../gcc