delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2003/08/03/17:45:04

From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: slow operation
Date: 3 Aug 2003 21:34:01 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 50
Message-ID: <bgjv49$ash$1@nets3.rz.RWTH-Aachen.DE>
References: <3f2cff90$1 AT news DOT bezeqint DOT net>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 1059946441 11153 137.226.32.75 (3 Aug 2003 21:34:01 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 3 Aug 2003 21:34:01 GMT
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Klayhamn <psycho AT isdn DOT net DOT il> wrote:

> and i'm running this on a P166mhz with 128MB ram...
> Just as comparison -- with TurboC 3.0 it takes virtually NO TIME at all
> (compiles before i blink) -

Unfortunately, TurboC isn't really playing the same game.  For
starters, this program is C++, not C.  That makes a *big* difference.

NOTE: Borland also has a C++ compiler, but none that bears version
number 3.0 and would be able to digest ANSI Standard C++ sources.

> and i am able to use intense software without much trouble (like ARACHNE web
> browser for DOS for example)

Compilation of C++ sources is a lot more "intense" than you seem to be
aware of.  It's long been known that about the best test to check for
general stability of a new machine is to compile large-ish programs
with GCC on it.

> so is it just DJGPP being "more sophisticated" or simply going through a
> lenghtier process --

Both of those.

> or is it the fact i'm only compiling/linking/making from within the RHIDE
> ide?

That certainly isn't making things any easier.

> or is it the Pentium 166mhz (although i doubt it)...?

To a rather significant extent, it is.

> What do you guys think, and is it some known issue that can be fixed?

Hard to tell.  This could easily be a problem largely caused by
insufficient tuning of your DOS configuration.  In particular, of your
disk cache settings.  If the compilation time doesn't decrease by quite
a lot if you repeat the compilation from the command line at least 
twice in a row:

	gpp -o Hello Hello.cpp
	gpp -o Hello Hello.cpp

your disk cache is in need of a tweak.

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019