Date: Thu, 9 Sep 1999 09:19:01 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Andy <wowbagger AT diamond DOT co DOT uk>
cc: djgpp AT delorie DOT com
Subject: Re: Need help building Allegro!?!
In-Reply-To: <7r6cdu$a0e$1@nclient9-gui.server.ntli.net>
Message-ID: <Pine.SUN.3.91.990909091847.6646H-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 8 Sep 1999, Andy wrote:

> Um, Well I clocked my cpu back to what it should be (400Mhz) , and allegro
> complied with no errors. Even though windows was not to fussy with my
> overclocked processor it looks like djgpp did not like it at all.

GCC is a very memory-intensive compiler, it moves large buffers around
a lot.  It also uses lots of memory.  So it is very sensitive to small
problems with memory accesses, and it uses addresses that Windows
might never touch.  Overclocking might create random problems with
memory chips and/or caches that cannot keep up with the processor, and
if that happens, GCC will surely crash.

Note that section 6.6 of the FAQ mentions such problems.