[LLVMdev] llvm-gcc bootstrap failure

Duncan Sands baldrick at free.fr
Wed Aug 13 11:09:16 PDT 2008


Hi Andrew,

> > /ptmp/dag/build.llvm-gcc-4.2.trunk.official.opt/x86_64-unknown-linux-gnu/./gcc/xgcc 
> > -B/ptmp/dag/build.llvm-gcc-4.2.trunk.official.opt/x86_64-unknown-linux-gnu/./gcc/ 
> > -B/cray/iss/compiler/cost/tools/llvm-tools/llvm/install.trunk.official.opt/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/bin/ 
> > -B/cray/iss/compiler/cost/tools/llvm-tools/llvm/install.trunk.official.opt/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/lib/ 
> > -isystem /cray/iss/compiler/cost/tools/llvm-tools/llvm/install.trunk.official.opt/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/include 
> > -isystem /cray/iss/compiler/cost/tools/llvm-tools/llvm/install.trunk.official.opt/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/sys-include  
> > -O2  -O2 -g -O2  -DIN_GCC    -W -Wall -Wwrite-strings -Wstrict-prototypes 
> > -Wmissing-prototypes -Wold-style-definition  -isystem ./include  -fPIC -g 
> > -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  -I. -I. 
> > -I/ptmp/dag/llvm-project.official/llvm-gcc-4.2/trunk/gcc 
> > -I/ptmp/dag/llvm-project.official/llvm-gcc-4.2/trunk/gcc/. 
> > -I/ptmp/dag/llvm-project.official/llvm-gcc-4.2/trunk/gcc/../include 
> > -I/ptmp/dag/llvm-project.official/llvm-gcc-4.2/trunk/gcc/../libcpp/include  
> > -I/ptmp/dag/llvm-project.official/llvm-gcc-4.2/trunk/gcc/../libdecnumber 
> > -I../libdecnumber 
> > -I/ptmp/dag/build.llvm.trunk.official.opt/x86_64-unknown-linux-gnu/include 
> > -I/ptmp/dag/llvm-project.official/llvm/trunk/include -DL_popcountsi2 
> > -c /ptmp/dag/llvm-project.official/llvm-gcc-4.2/trunk/gcc/libgcc2.c -o 
> > libgcc/./_popcountsi2.o
> > cc1: /ptmp/dag/llvm-project.official/llvm/trunk/lib/Support/StringMap.cpp:177: 
> > void llvm::StringMapImpl::RemoveKey(llvm::StringMapEntryBase*): Assertion `V 
> > == V2 && "Didn't find key?"' failed.
> > /ptmp/dag/llvm-project.official/llvm-gcc-4.2/trunk/gcc/libgcc2.c:809: internal 
> > compiler error: Aborted
> 
> Unless this is in something like an inline asm, an internal compiler
> error is always a gcc bug.  You should probably upgrade your gcc: you
> don't say exactly what version it is.

after the new compiler is built (llvm-gcc, named xgcc at this point), it
is used to build various libraries.  As you can see in the above line from
the build log, xgcc crashed while building libgcc2.c.  Since our own compiler
crashed, it is up to us to fix it :)  The system compiler should not be
relevant, unless xgcc is crashing because it was miscompiled by the system
gcc.

Best wishes,

Duncan.



More information about the llvm-dev mailing list