Date: Sun, 30 Aug 1998 17:21:50 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: "Thomas J. Hruska" <thruska AT tir DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: Display question...
In-Reply-To: <3.0.5.16.19980827202740.2cfff282@mail.tir.com>
Message-ID: <Pine.SUN.3.91.980830172131.20257Z-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Thu, 27 Aug 1998, Thomas J. Hruska wrote:

> DJGPP has poor error/warning alerts compared to Borland's

You need to use -Wall -O, and then you'll see that GCC blows Turbo C
out of the water as far as diagnostics is concerned.

> How badly is the performance cut since I only want to let the user know
> that the program is working and to please wait?  Since most of the activity
> of the program is hard drive related (and some blocks can take 5-10 seconds
> to process in a 16-bit environment), I figured 32-bit was the best way to
> go to speed things up a bit.

You will need to post more information to get meaningful replies.
Specifically:

	- how much time (percentwise) does the program read/write
          files, relative to the total run time?
	- how large are the files it reads/writes?
	- does it seek into files or only reads/writes sequentially?

In most programs the overhead is negligible, unless the program does
nothing else but read/write the file.

> How long does it take to switch to and from real mode?

Hundreds of CPU cycles.