GCC-3.4.2 PCH failures (segmentation faults)

ilja ilja.siera at ukonline.co.uk
Fri Nov 5 15:54:23 PST 2004


Hi,

I'm getting a lot of pch failures in my GCC-3.4.2 testsuite.
I'll spare the whole list, this is a grab out of it:

>FAIL: gcc.dg/pch/common-1.c -O0 -g (test for excess errors)
>FAIL: gcc.dg/pch/common-1.c  -O0  (test for excess errors)
>FAIL: gcc.dg/pch/common-1.c  -O1  (test for excess errors)
>FAIL: gcc.dg/pch/common-1.c  -O2  (test for excess errors)
>FAIL: gcc.dg/pch/common-1.c  -O3 -fomit-frame-pointer  (test for excess
errors)
>FAIL: gcc.dg/pch/common-1.c  -O3 -g  (test for excess errors)
>FAIL: gcc.dg/pch/common-1.c  -Os  (test for excess errors)
>FAIL: gcc.dg/pch/cpp-1.c -O0 -g (test for excess errors)
>FAIL: gcc.dg/pch/cpp-1.c  -O0  (test for excess errors)
>FAIL: gcc.dg/pch/cpp-1.c  -O1  (test for excess errors)
>FAIL: gcc.dg/pch/cpp-1.c  -O2  (test for excess errors)
>FAIL: gcc.dg/pch/cpp-1.c  -O3 -fomit-frame-pointer  (test for excess
errors)
>FAIL: gcc.dg/pch/cpp-1.c  -O3 -g  (test for excess errors)
>FAIL: gcc.dg/pch/cpp-1.c  -Os  (test for excess errors)
>FAIL: gcc.dg/pch/cpp-2.c -O0 -g (test for excess errors)
>FAIL: gcc.dg/pch/cpp-2.c  -O0  (test for excess errors)
>FAIL: gcc.dg/pch/cpp-2.c  -O1  (test for excess errors)
>FAIL: gcc.dg/pch/cpp-2.c  -O2  (test for excess errors)
>FAIL: gcc.dg/pch/cpp-2.c  -O3 -fomit-frame-pointer  (test for excess
errors)

in the detailed log this is the typical message:

>FAIL: gcc.dg/pch/inline-3.c  -O3 -g  (test for excess errors)
>Excess errors:
/source/blfs/build/gcc-3.4.2/gcc/testsuite/gcc.dg/pch/inline-3.c:2: internal
compiler >error: Segmentation fault
>UNTESTED: gcc.dg/pch/inline-3.c  -O3 -g  assembly comparison
>Executing on host:
/source/blfs/build/gcc-build/gcc/xgcc -B/source/blfs/build/gcc-build/gcc/
./inline-3.h   -Os    -o inline-3.h.gch    (timeout = 300)

(all failures come up the same)

I'm building my BLFS on top of lfs-6.0 build with GCC-3.4.2. There were no
errors in the testsuite while building gcc-3.4.2 for lfs-6.0.
Since it didn't occur during the lfs build I suspect the kernel. Could that
be true or should i look somewhere else.
Hope somebody can shed some light,

Regards,

ilja







More information about the blfs-support mailing list