Date: Wed, 13 Oct 1999 11:43:55 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Johan Venter <jventer AT writeme DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: allegro gone missing?
In-Reply-To: <lAFM3.3249$_4.5461@newsfeeds.bigpond.com>
Message-ID: <Pine.SUN.3.91.991013114326.16702H-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 Tue, 12 Oct 1999, Johan Venter wrote:

> For some reason I find that compiling in DOS under CWSDPMI is takes
> about twice as long as compiling in Windows under its DPMI
> server. When compiling under CWSDPMI, the compilation does more disk
> thrashing than usual (noticeably more).

Do you have disk cache installed in the DOS configuration?  If not,
there's your reason.

If you do install the cache, and if your system setup is consistent
with the advice in section 3.9 of the FAQ, it probably means that GCC
runs out of free memory and pages to disk.  This can happen with large
programs, or with memory-starved machines (you didn't post info about
either, so I'm entitled to wild guesses, right?).  Sections 7.1 and
7.2 of the FAQ might help.

If you cannot figure out the reason, post here the vital details.
Something is clearly wrong or suboptimal, because Windows can never be
faster than a well-tuned DOS machine when compiling with DJGPP
(assuming the same hardware).