🚀 go-pugleaf

A couple of weeks ago I reported that gcc-2.2.2 uses unreasonably
large amounts of memory when compiling large array initializers.
After building gcc-2.3.1 I found that this behavior still exists.

I have been able to verify the existence of this problem on a
DECstation under Ultrix 4.2 (blech) and SPARC under SunOS 4.2.
I originally found the problem when trying to compile the xclient
"xphoon" which includes a 757x757 bitmap of the moon as an
array initializer, but have verified that it occurs in general.
In the case of xphoon the initializer consists of ~70,000 8bit
values but the compiler runs out of virtual memory (despite a
70MB swap partition) even on less than half that.  The DEC MIPS
compiler does not use any unusual amount of memory to compile
this declaration (i.e. less than a couple of MB).

Since it is fairly common practice to compile bitmaps into
programs as array initializers, and the ANSI standard does not
have any restrictions on initializer usage, this would seem to
be a fairly serious bug.

--
Jurgen Botz                  |   Internet: JBotz@mtholyoke.edu
Academic Systems Consultant  |     Bitnet: JBotz@mhc.bitnet
Mount Holyoke College        |      Voice: (US) 413-538-2375 (daytime)
South Hadley, MA, USA        | Snail Mail: J. Botz, 01075-0629