delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1996/07/16/06:43:53

Date: Tue, 16 Jul 1996 13:39:28 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Arash <ei39594 AT ios DOT chalmers DOT se>
Cc: djgpp AT delorie DOT com
Subject: Re: c:\Compiling............ Zzzzz..... :)
In-Reply-To: <4sdqm0$of6@nyheter.chalmers.se>
Message-Id: <Pine.SUN.3.91.960716132934.16752F-100000@is>
Mime-Version: 1.0

On 15 Jul 1996, Arash wrote:

> This is a fairly stuid question, but is there anyway to speed up the 
> compiler?? I'm stuck with this old 486 which makes compile time longer 
> than my lunch time :(

Did you check the compilation speed against the standards described in 
the DJGPP FAQ list?  If not, please download the file v2/faq201b.zip from 
the same place you get DJGPP and read section 7.1 there; maybe your 
system is set up in a sub-optimal way.

If you already did that and DJGPP compiles at the rates described in the
FAQ, then it must be quite a package that compiles for such a long time. 
I also work with an ``old'' 486, and most of the packages (even as large
as Emacs) don't leave me enough time to even make and drink a cup of
coffee... 

> BTW, I have DJGPP V2 but i'm using TurboC when writing small dos appz, 
> guess why?

One of the reasons TurboC is so fast is the low quality of the code it 
produces (did you ever looked at the machine code of the programs you 
run?)  Borland C makes a much better job, and for a price: it only 
compiles twice as fast as DJGPP (TurboC compiles tenfold as fast).  If 
you want much faster compilation, compile with -O0 (no optimizations at 
all) with DJGPP too.

- Raw text -


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