Date: Sun, 28 Jun 1998 15:31:50 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: "Charles M. Dude" <dude AT hal DOT io DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: Compiled programs LAG terribly
In-Reply-To: <3593FDD5.D62342E6@hal.io.com>
Message-ID: <Pine.SUN.3.91.980628152846.9146G-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Fri, 26 Jun 1998, Charles M. Dude wrote:

> Ive just had a talk to the author. The program allocates 32MB on startup,
> regardeless of the size of the input files. So, one can understand that,
> on a 32Meg machine, DPMI starts to swap.

How does it allocate the memory?  If it uses malloc (as opposed to 
calloc), then in general the program doesn't neeed to begin paging right 
away, since you haven't accessed that memory.

> Do you think this is the reason for it? Does that really cause two minutes
> of silence before anything happens? As I mentioned, on the same machine
> running linux, the program comes up immediately.

Please post what go32-v2 prints when invoked with no arguments, in the 
same configuration where you run the DJGPP-compiled program.  It could be 
that you don't give enough physical memory to the program.