Re: bootstrap/7300: ../../gcc-3.1/gcc/libgcc2.c:1004: internal error: Segmentation fault

[Dara Hazeghi <dhazeghi@yahoo.com>]

The following reply was made to PR bootstrap/7300; it has been noted by GNATS.

From: Dara Hazeghi <dhazeghi@yahoo.com>
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: bootstrap/7300: ../../gcc-3.1/gcc/libgcc2.c:1004: internal error: Segmentation fault
Date: Wed, 21 May 2003 01:33:44 -0700 (PDT)

 --- "David G. Miller" <dave@davenjudy.org> wrote:
 > Date: Sat, 10 May 2003 20:20:53 -0600
 > From: "David G. Miller" <dave@davenjudy.org>
 > To: Dara Hazeghi <dhazeghi@yahoo.com>
 > Subject: Re: bootstrap/7300:
 > ../../gcc-3.1/gcc/libgcc2.c:1004: internal error:
 >  Segmentation fault
 > 
 > Dara Hazeghi wrote:
 > 
 > >
 >
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-
 > 
 > > trail&database=gcc&pr=7300
 > >
 > > Hello,
 > >
 > > could the submitter of this bug report please
 > verify that this 
 > > problem  exists with a current version of gcc (ie
 > 3.2.3), or submit 
 > > the  preprocessed source causing the crash as the
 > ICE message 
 > > suggests.  There have been a number of reports of
 > successful builds of 
 > > gcc 3.2.x  on i586-linux, so I suspect the problem
 > should not be too 
 > > difficult to  determine the cause of. Thanks,
 > >
 > > Dara
 > 
 > Dara -
 >    I tried reproducing the problem and in some ways
 > did but I'm fairly 
 > convinced part of the problem is my hardware.  I got
 > several "*Error*: 
 > suffix or operands invalid for `*movd*'" problems
 > that went away as soon 
 > as I tried to compile the source code that
 > supposedly caused the problem 
 > separately.  At some point, these got replaced by
 > seg faults that again 
 > went away as soon as I attempted to separately
 > compile the source code 
 > for which the error was reported.  I eventually
 > resorted to wrapping the 
 > "make bootstrap" in a while loop with a "sleep 60"
 > whenever the make 
 > exited.  This system has shown heat related
 > instability in the past and 
 > this looks like the same thing.
 > 
 >    The buld eventually completed and I've used the
 > resulting copy of gcc 
 > to build several programs which then executed
 > flawlessly.  I would chalk 
 > this one up to uncovering a hardware problem on the
 > build system.
 > 
 >    Let me know if you have any questions or if there
 > is anything you 
 > would like to see built on this system.
 > 
 > Regards,
 > Dave
 > 
 
 __________________________________
 Do you Yahoo!?
 The New Yahoo! Search - Faster. Easier. Bingo.
 http://search.yahoo.com