FreeBSD 6.1 buildworld segfault on gcc

[Mischa Peters]

Hi Alex,

>> Not sure if this is the right list, there are so many... but here  
>> it  goes. :)
> Always a good place to start.

Pfew ;)

>> I am trying to run buildworld on FreeBSD 6.1. Using RELENG_6_1.
>> It segfaults on GCC with the following message:
>>
>> cc -O2 -fno-strict-aliasing -pipe -DIN_GCC -DHAVE_CONFIG_H - 
>> DPREFIX= \"/usr/obj/usr/src/tmp/usr\" -I/usr/obj/usr/src/tmp/usr/ 
>> src/gnu/ usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/ 
>> cc_int/../ cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../ 
>> contrib/gcc -I/ usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/ 
>> gcc/config - DHAVE_CONFIG_H -DTARGET_NAME=\"i386-undermydesk- 
>> freebsd\" -DIN_GCC  - I/usr/obj/usr/src/tmp/legacy/usr/include -c / 
>> usr/src/gnu/usr.bin/cc/ cc_int/../../../../contrib/gcc/local-alloc.c
>> cc -O2 -fno-strict-aliasing -pipe -DIN_GCC -DHAVE_CONFIG_H - 
>> DPREFIX= \"/usr/obj/usr/src/tmp/usr\" -I/usr/obj/usr/src/tmp/usr/ 
>> src/gnu/ usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/ 
>> cc_int/../ cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../ 
>> contrib/gcc -I/ usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/ 
>> gcc/config - DHAVE_CONFIG_H -DTARGET_NAME=\"i386-undermydesk- 
>> freebsd\" -DIN_GCC  - I/usr/obj/usr/src/tmp/legacy/usr/include -c / 
>> usr/src/gnu/usr.bin/cc/ cc_int/../../../../contrib/gcc/loop.c
>> /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/loop.c: In   
>> function `strength_reduce':
>> /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/loop.c: 
>> 5420:  internal compiler error: Segmentation fault: 11
>> Please submit a full bug report,
>> with preprocessed source if appropriate.
>> See <URL:http://gcc.gnu.org/bugs.html> for instructions.
>> *** Error code 1
>
> Does it always segfault in the same place?  If not then faulty  
> memory is your number one suspect.  For that try memtest86+ (google  
> for it and burn a CD), or just try pulling memory sticks and seeing  
> if the problem goes away (but beware static).

It's always in the same place, with the same message. :(

Mischa