This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Strange bootstrap failure in
- To: gcc-bugs at gcc dot gnu dot org
- Subject: Strange bootstrap failure in
- From: David Ronis <ronis at montroll dot chem dot mcgill dot ca>
- Date: Tue, 21 Mar 2000 12:36:52 -0500
- Reply-to: ronis at onsager dot chem dot mcgill dot ca
I tried an optimized bootstrap build of gcc version 2.96 20000321
(experimental) on an i686-linux(2.2.14)-gnu(2.1.3) box with
BOOT_CFLAGS
-O3 -march=pentiumpro -funroll-loops -fomit-frame-pointer
-fstrict-aliasing -fforce-mem -fforce-addr -ffast-math -malign-double
The last few lines of the log read (with lines broken by me):
stage1/xgcc -Bstage1/ -B/usr/local/i686-pc-linux-gnu/bin/ -c -DIN_GCC
-W -Wall -Wtraditional -O2 -O3 -march=pentiumpro -funroll-loops
-fomit-frame-pointer -fstrict-aliasing -fforce-mem -fforce-addr
-ffast-math -malign-double -DHAVE_CONFIG_H -I. -I../../egcs/gcc
-I../../egcs/gcc/config -I../../egcs/gcc/../include
../../egcs/gcc/gccspec.c
stage1/xgcc -Bstage1/ -B/usr/local/i686-pc-linux-gnu/bin/ -DIN_GCC -W
-Wall -Wtraditional -O2 -O3 -march=pentiumpro -funroll-loops
-fomit-frame-pointer -fstrict-aliasing -fforce-mem -fforce-addr
-ffast-math -malign-double -DHAVE_CONFIG_H -o xgcc gcc.o gccspec.o
intl.o prefix.o version.o obstack.o ../libiberty/libiberty.a
echo "int xxy_us_dummy;" >tmp-dum.c
./xgcc -B/usr/local/i686-pc-linux-gnu/bin/ -B.
-I/usr/local/i686-pc-linux-gnu/include -S tmp-dum.c
make[2]: *** [s-under] Segmentation fault
make[2]: Leaving directory `/home/ronis/Project/notar/objdir/gcc'
make[1]: *** [bootstrap] Error 2
make[1]: Leaving directory `/home/ronis/Project/notar/objdir/gcc'
make: *** [bootstrap] Error 2
The problem is that ./xgcc SIGSEGV's (when run with no arguments or
with -v) and thus I've not been able to run with -save-temps. This
problem was also present in the preceding snapshot (and was reported).
David
P.S., there are several nasty bugs that crop up with high levels of
optimization (notably in g++) and are already present in 2.95.2 and
lead to massive g++ testfailures. [I've reported the ones I've come
across, albeit without any ideas how to fix them].