X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-bounces using -f
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Huge differences in compilation time between gcc/gpp
Date: Wed, 10 Apr 2002 13:13:12 CDT
Organization: Rice University, Houston TX
Lines: 8
Message-ID: <3cb480b8.sandmann@clio.rice.edu>
References: <MPG DOT 171e94b2eddf849f989686 AT news DOT icm DOT edu DOT pl> <a91t3m$hb$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <MPG DOT 171e9828cbff1a8e989687 AT news DOT icm DOT edu DOT pl>
NNTP-Posting-Host: clio.rice.edu
X-Trace: joe.rice.edu 1018462460 9484 128.42.105.3 (10 Apr 2002 18:14:20 GMT)
X-Complaints-To: abuse AT rice DOT edu
NNTP-Posting-Date: 10 Apr 2002 18:14:20 GMT
X-NewsEditor: ED-1.5.9
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

> Is P166 too old for C++, then ? (with MSVC++ I can compile C++ in few 
> seconds)  

It's more likely an issue of memory than CPU speed.  C++ compiles with 
GCC 3.x seem to take a minimum of 16MB of free memory.  Try to make sure
go32-v2 shows this much free (not page or swap).

GCC 2.x uses less for C++ compiles.