delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1994/03/24/10:35:49

Date: Thu, 24 Mar 94 09:53:37 -0500
From: dj AT ctron DOT com (DJ Delorie)
To: eliz AT is DOT elta DOT co DOT il
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu
Subject: Re: DJGPP Speed

>   Is 200 lines per second reasonable for DJGCC 1.11?  I tested it on my

My system (486DX2/66, optimized for go32) can build all of gcc in 30
minutes or less (faster than pizza delivery).  You can figure out
rates from there.  Dhrystones for gcc in djgpp on my machine run
around 50K, about the same as a Sparc IPX or Sparc II, but that
doesn't include disk I/O.

Run "go32" and make sure you have at least 1-2M of *available* memory
(building gcc with -O2 requires around 4.5M of available memory).
Give yourself about 1.5M for TMP (not go32tmp) and give the rest to
smartdrv (or other cache), but at least a few meg (if you've been
counting, you're up to 8M at this point, maybe more) - enough to hold
all the binaries gcc uses (go32, gcc, cpp, cc1, as, ld).  That's about
as optimal as it gets, as far as big wins go.

Oh - I'm using a fast SCSI II disk and AHA-2742T EISA controller that
can *sustain* 4.5Mb/s into the system, which helps a lot.

DJ


- Raw text -


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