delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1994/09/06/17:02:35

Date: Tue, 6 Sep 1994 16:02:48 -0400 (EDT)
From: Kimberley Burchett <OKRA AT max DOT tiac DOT net>
Subject: Re: GCC question - why so slow ?
To: Markus Hahn <Markus DOT Hahn AT studbox DOT uni-stuttgart DOT de>
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu


On Tue, 6 Sep 1994, Markus Hahn wrote:

> Short question : why is the new version 2.60 of GCC so S-L-O-W ????

  Are you using gcc or djgpp?  Anyway, try setting the /temp directory to 
a ramdrive.  Be sure that the /bin directory is in the beginning of the 
path.  I've got a copy of go32.exe in my source directory so it gets 
found faster when I compile things.  Other than that, I can't think of 
much to speed it up.
  I've got a 486sx25 w/4MB memory and I compile most stuff in about 15 or
20 seconds.  My record is 12 seconds.  My other record is 3.5 minutes 
(but that was a fluke - when I rebooted and compiled the same thing, it 
went a lot faster).

> My standard compilation batch is
> 
>                          gcc %1.c -o %1 -gcc -lpc

  Hm... might want to add -lm to that for when you want to use math... 
also you might like -O3 to get optimizations.  And you're not running the 
result through coff2exe.  I added "strip -s a.out" to my batch to get 
smaller programs.  I also put "c:\dos\smartdrv /c" at the end to flush 
the write cache.
							Kim

- Raw text -


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