Date:	Wed, 31 May 2000 15:01:25 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	"J.W. Dare" <jwdare AT novia DOT net>
cc:	djgpp AT delorie DOT com
Subject:	Re: Internal compiler error
In-Reply-To:	<oaf9jsctifoumgvet1oeflofobgb8k2iil@4ax.com>
Message-ID:	<Pine.SUN.3.91.1000531145519.11385B@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On 31 May 2000, J.W. Dare wrote:

> While using djgpp for my first semester C++ programming class
> assignments, approximatly half of the time the compiler quits with
> error messages similar to the two below.  A second attempt will
> usually compile the code.
[snip]
> I'm running djgpp from a DOS window in Win 95, OSR2, on an older 100
> Mhz pentium.  Does anyone know what could be causing these problems?
> 
> D:\UNO\asgn07>gxx -g p03_41.cpp -o fib02.cpp
> In file included from p03_41.cpp:10:
> c:/develop/djgpp/lang/cxx/iostream.h: In method `class istream &
> istream::opera
> or >>(unsigned char *)':
> c:/develop/djgpp/lang/cxx/iostream.h:201: Internal compiler error.

Internal compiler errors or crashes that are not repeatable are usually a 
tell-tell sign of a hardware problem.

GCC is a memory hog: it uses lots of memory, moves large buffers to and
fro, and runs the CPU at full throttle for prolonged periods of time. 
Thus, it frequently reveals hardware problems, such as faulty memory
chips, over-zealously overclocked CPUs, and incorrect settings of memory
wait states or CPU caches. 

This is explained in the DJGPP FAQ list, sections 6.4 and 6.6.

I suggest to review your BIOS settings, and try to change memory/cache 
settings to slower but safer ones.  If that doesn't help, it's possible 
that some of your memory chips are not keeping up with the CPU.  Time to 
upgrade?

- Raw text -