Date: Wed, 31 May 2000 20:56:40 +0600 (LKT)
From: Kalum Somaratna aka Grendel <kalum AT lintux DOT cx>
X-Sender: kalum AT roadrunner DOT grendel DOT net
To: djgpp AT delorie DOT com
Subject: Re: Internal compiler error
In-Reply-To: <Pine.SUN.3.91.1000531145519.11385B@is>
Message-ID: <Pine.LNX.4.21.0005312045460.1241-100000@roadrunner.grendel.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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
Precedence: bulk

On Wed, 31 May 2000, Eli Zaretskii wrote:

 
> 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. 

Indeed. FWIW whenever I by new memory chips, I allways run GCC on a large
build to see wether the memory is ok...IMHO GCC is a *very* good way to
test your PC's stability...

Grendel

Hi, I'm a signature virus. plz set me as your signature and help me spread
:)