This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: Experiencing unreproducible internal compiler errors <<whinge>>
- To: Zack Weinberg <zack at wolery dot cumb dot org>
- Subject: Re: Experiencing unreproducible internal compiler errors <<whinge>>
- From: Toon Moene <toon at moene dot indiv dot nluug dot nl>
- Date: Thu, 16 Mar 2000 21:17:42 +0100
- CC: Matt Lowry <mclowry at cs dot adelaide dot edu dot au>, gcc-bugs at gcc dot gnu dot org
- Organization: Moene Computational Physics, Maartensdijk, The Netherlands
- References: <Pine.SV4.3.93.1000316115453.18668A-100000@rosemary> <20000315175455.G27910@wolery.cumb.org>
Zack Weinberg wrote:
> On Thu, Mar 16, 2000 at 12:23:38PM +1030, Matt Lowry wrote:
> > I have encountered internal compiler errors with gcc 2.95.2, but they are
> > unreproducible in that with all cases the problem did not reappear when
> > make was immediatley reinvoked.
> 99 times out of 100, this is a hardware problem, such as an
> excessively overclocked CPU or a faulty memory board. Please see
> http://www.bitwizard.nl/sig11/
However, in the past we've also seen this behaviour with experimental OS
kernels (like the odd-numbered Linux ones).
Remember that a buggy device driver is a great way to change memory you
think is private to your process in inpredictable ways.
--
Toon Moene (toon@moene.indiv.nluug.nl)
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
Phone: +31 346 214290; Fax: +31 346 214286
GNU Fortran: http://gcc.gnu.org/onlinedocs/g77_news.html