Mail Archives: djgpp/2003/08/03/17:45:04
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 -