Closed llvmbot closed 13 years ago
LLVM-GCC has reached its end of life as far as llvm.org releases go. Please migrate to Clang or DragonEgg when possible. The llvm-gcc SVN repo will still continue to exist, so additional patches can go into it if you so desire, but since we have no more releases of it coming, it doesn't make sense to track bugs for it anymore.
If this is a problem that still exists with clang or DragonEgg, please file a new bug to track it. Thanks!
-Chris
Did you build LLVM with assertions enabled? If not, I suggest you do so and try again.
This didn't seem to change anything:
I just realized that I didn't specify --disable-multilib and --disable-bootstrap to configure. Just for kicks, I tried adding both. This leads the build to fail differently:
Did you build LLVM with assertions enabled? If not, I suggest you do so and try again.
Will do. Thanks for the help!
Did you build LLVM with assertions enabled? If not, I suggest you do so and try again. Probably ice is related to f128 stuff. At least this goes from the file name....
Did you build LLVM with assertions enabled? If not, I suggest you do so and try again.
If you try running the failing command /tmp/mfs/2.8/build/./gcc/xgcc -B/tmp/mfs/2.8/build/./gcc/ ... by hand in the correct directory, does it still crash if you add -emit-llvm to the command line?
Unfortunately, with --emit-llvm I have the exact same error:
If you try running the failing command /tmp/mfs/2.8/build/./gcc/xgcc -B/tmp/mfs/2.8/build/./gcc/ ... by hand in the correct directory, does it still crash if you add -emit-llvm to the command line?
The bug also occurs when using gcc 4.4.1 on Solaris/x86. And even though the exact error is "internal compiler error", which would imply a gcc bug, Yes, but not your system gcc, it's during the libgcc compilation, where newly-built llvm-gcc is already used.
Any advice would be greatly appreciated! Noone is working on any solaris support right now, so any breakage is definitely expected.
Extended Description
I am unable to build llvm-gcc-4.2-2.8 on Solaris/x86.
I successfully built llvm-gcc-4.2-2.7 and llvm-2.7 on Solaris/x86. I can also build llvm-2.8 itself on Solaris/x86. The break occurs only when moving from the released llvm-gcc-4.2-2.7 to llvm-gcc-4.2-2.8
Platform: uname -a == SunOS 5.10 Generic_142901-12 i86pc i386 i86pc
Toolchain: gcc 4.5.1 binutils 2.20.1
Configure invocation: ../llvm-gcc-4.2-2.8.source/configure --prefix=/proj/spear0/dtmc_x86/llvm-2.8-gcc --program-prefix=llvm- --enable-llvm=/proj/spear0/dtmc_x86/llvm --enable-languages=c,c++ --enable-checking --with-gnu-as --with-as=/proj/spear0/binutils-2.20.1/bin/as --with-gnu-ld --with-ld=/proj/spear0/binutils-2.20.1/bin/ld
The specific error occurs when building libgcc2.c. I'm building using 'gmake' (no -j flag).
Re-running gmake reproduces the error, and provides the following background about gcc build progress:
The bug also occurs when using gcc 4.4.1 on Solaris/x86. And even though the exact error is "internal compiler error", which would imply a gcc bug, the fact that both compilers can handle llvm-gcc-2.7-4.2 but not llvm-gcc-2.8-4.2 suggests that this has more to do with changes to llvm-gcc between the 2.7 and 2.8 releases.
Any advice would be greatly appreciated!