delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1997/06/05/13:08:50

Date: Thu, 5 Jun 1997 20:04:11 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Gyorgy Abonyi <loop AT hu DOT bonus DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: Speed of DJGPP?
In-Reply-To: <199706051442.QAA28972@zeus.hu.bonus.com>
Message-ID: <Pine.SUN.3.91.970605195808.7238C-100000@is>
MIME-Version: 1.0

On Thu, 5 Jun 1997, Gyorgy Abonyi wrote:

> On my system (p133, 16Mbyte ram,
> Win95), DJGPP usually spends equal time in CPP and AS than in CC1,

I find this hard to believe, unless your system has awfully non-optimal
configuration.  A typical compile, even on small modules should dwell in
CC1 much longer than in CPP and AS.  I suggest you check your
configuration (especially how much free DPMI memory does Windows let you
use) as per section 3.9 of the FAQ. 

> BCC and Watcom usually don't use external C pre-processor, and assembler
> module, so they don't need to pass a lot of an information via file I/O (I
> know thay creates temp files, but not as much as gcc...).

With a large cache and TMPDIT that points to a RAM drive, most of the I/O
to temporary files actually boils down to memory moves, and those are
lightning fast on a Pentium. 

> And if You can access a U..ix version of gcc, than You can check that the
> -pipe option speeds up really the compilation.

Did you actually check this?  I did, and on many workstations there is no 
visible difference.  The reason, again, is that Unix has a well-tuned 
disk cache.

- Raw text -


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