Date: Wed, 24 Sep 1997 11:34:31 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Shawn Hargreaves <Shawn AT talula DOT demon DOT co DOT uk>
cc: djgpp AT delorie DOT com
Subject: Re: Allegro WIP (make.exe crash)
In-Reply-To: <2E4OlpA9sBK0EwvF@talula.demon.co.uk>
Message-ID: <Pine.SUN.3.91.970924113405.18049B-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Tue, 23 Sep 1997, Shawn Hargreaves wrote:

> It's very worrying that so many people seem to have trouble compiling
> this file! It is very large (a macro that expands into 256 versions of a
> color blending routine, one for each alpha value, and is used three
> times for the different color depths), but it isn't _so_ big that I
> would expect it to cause problems, and the individual functions are all
> quite small.

GCC is known to gobble ludicrous amounts of memory when optimizing
some innocent-looking programs, especially if you say -O3 or -O2.

> I have a nasty feeling that I might have to split this
> across several files, unless you can find a reliable way to make it
> build...

You just need to have enough VM (and possibly to stubedit cc1 for a
larger stack size), that's all.  But splitting that file seems to be a
good idea anyway.  IMHO, no file should require more than 16MBytes to
compile, because some people don't bother to set their systems to more
than that.

> Do you know which phase of the compile is causing the crash?

From the reports I saw, it's cc1.