From: David Jenkins <me AT jenkinsdavid DOT demon DOT co DOT uk>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Allegro WIP (make.exe crash)
Date: Wed, 24 Sep 1997 02:24:58 +0100
Organization: None
Distribution: world
Message-ID: <jXXK2FAqvGK0Ew9a@jenkinsdavid.demon.co.uk>
References: <eoToTAAPiwJ0Ewho AT jenkinsdavid DOT demon DOT co DOT uk>
 <19970923064201 DOT CAA03046 AT ladder01 DOT news DOT aol DOT com>
NNTP-Posting-Host: jenkinsdavid.demon.co.uk
MIME-Version: 1.0
Lines: 34
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

In article <19970923064201 DOT CAA03046 AT ladder01 DOT news DOT aol DOT com>, Dyad255
<dyad255 AT aol DOT com> writes
>Yes, the WIP colblend.c does now contain HUGE macro expansions (of expansions).
>
>>I just got PGCC and rebuilt Allegro WIP, this time to fix them I
>>followed somebody elses advice.
>>Start a Dos session in Win95,
>>Alt + TAB back to Win95 select the Dos boxes properties
>>Under the memory tab select DPMI and TYPE in 65535.
>>Make then ran without errors.
>
>Hm! I just got PGCC and rebuilt Allegro WIP too, but 65535 didn't work for
>me...
>Neither did stubedit or any other '95 tricks... I only had 16mb RAM on
>that machine, but VM has never failed me....
>
>I had to go into bare naked DOS mode with CWSDPMI version 3. After 1
>minute of swapping, the thing compiled on the p133.  8)
>
I did get errors with the 65535 in Win95s DPMI setting, even after
trying other things. The only workaround I could find was to rebuild
AllegroWIP using -O3 instead of -O6 :(
The colblend.c kept freezing the build process using -O6, using -O3 it
took a while to compile it too.

What kind of speed increase would -O6 give over -O3 anyway?? I read in
one of the Docs that Allegro uses a lot of asm stuff allready. So I
didn't see the point in struggling to get it compiling with -O6.


-- 
http://www.jenkinsdavid.demon.co.uk for C programmers.
David Jenkins