Date:	Thu, 14 Jul 1994 11:59:44 -0700
From:	Philip Freidin <philip AT xilinx DOT com>
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	Re: 1.12 ?
Cc:	philip AT xilinx DOT com

DJ writes:
> I'm planning on getting 1.12 ready for release this weekend, which
> means reading though all my back mail looking for bug reports and
> patches to work on.  If anyone knows of a bug that is bad enough to
> hold off a 1.12 release until such bug is fixed, please post them (try
> to avoid repeats).  Diffs would be appreciated also.  Also, if you
> want something added to the standard djgpp package let me know - just
> make sure it's in the contrib format and available to me via FTP or
> uuencode.


Unfortunately I have not been a big user of 1.11, but had used 1.08
or maybe 1.09 a bit. In "net tradition" I'll ask anyway, whether this
following problem has been seen by others, and has it been reported
as either a bug or something to be fixed.

I have a small application, that needs a big array:

unsigned int array[16778000];    /* allocate 64MB (some in RAM, some on disk) */

this is declared ouside of any procedures, so is statically allocated.

in 1.08/1.09 this program compiled and linked fine, and the process
only took a minute or two (the actual program is about 200 lines).

With 1.11, the link phase runs for about 45 minutes, beating on the
disk, and eventually runs out of space with a message like:
	VM EXHAUSTED

GO32TMP=N:\    and this drive has 104MB free space

Looks to me like the ld is trying to build this array at link time,
and then gets into trouble. This used to work fine in 1.08/9

	Thanks in advance
			Philip

- Raw text -