Hello all,
I've got the ICE on the gcc.c-torture/compile/20000718.c test:
powerpc-linux-gnuspe-gcc -c -O3 -funroll-loops 20000718.c
20000718.c: In function 'baz':
20000718.c:14: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
Compilation passed OK with -mfloat-gprs=single, and fails with
-mfloat-gprs=double (compiler default).
Is this a known failure? Any fixes?
compiler details:
Target: powerpc-linux-gnuspe
Configured with: ../gcc-4.3-20080228/configure
--target=powerpc-linux-gnuspe
--prefix=/opt/crosstool/gcc-4.3-20080228-glibc-20070515T2025/powerpc-linux-gnuspe
--disable-hosted-libstdcxx
--with-headers=/opt/crosstool/gcc-4.3-20080228-glibc-20070515T2025/powerpc-linux-gnuspe/powerpc-linux-gnuspe/include
--with-local-prefix=/opt/crosstool/gcc-4.3-20080228-glibc-20070515T2025/powerpc-linux-gnuspe/powerpc-linux-gnuspe
--disable-nls --enable-threads=posix --enable-symvers=gnu
--enable-__cxa_atexit --enable-languages=c,c++,java --enable-shared
--enable-c99 --enable-long-long --without-x --with-mpfr=/usr/local
--with-cpu=8540 --enable-cxx-flags=-mcpu=8540 --enable-e500_double
I analyzed test results for the gnuspe target; latest I found is
for 4.3.0 20080124
(http://gcc.gnu.org/ml/gcc-testresults/2008-01/msg01187.html).
The 20000718.c test passed, as I see, but I wonder how was the compiler
configured? The test target name was "reg_e500v1_ssh", so I guess the
compiler configuration was without e500 long double support (i.e.
without -mfloat-gprs=double).
Have anyone ran the gcc testuite with e500 long double enabled?
Thanks for any help.
Regards,
Sergei
