Xref: news2.mv.net comp.os.msdos.djgpp:2362
From: ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Compilation Timing
Date: 2 Apr 1996 02:06:58 GMT
Organization: The National Capital FreeNet
Lines: 26
Sender: ao950 AT freenet6 DOT carleton DOT ca (Paul Derbyshire)
Message-ID: <4jq242$fj8@freenet-news.carleton.ca>
References: <4jovn6$2k2 AT news DOT csus DOT edu>
Reply-To: ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire)
NNTP-Posting-Host: freenet6.carleton.ca
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp


GEORGE ARUGAY MONTEMAYOR (gmontem AT sfsu DOT edu) writes:
> --
> Hi,
> 
> Does djgpp have a switch that will tell me how long it took to compile 
> source code?  That way I can fiddle with my cache settings/RAM disk 
> settings until I can find the 'best' optimial configuration for djgpp.

Don't know of any, but if it turns out there isn't there's a workaround:
compile it from Windows, watching the clock in the screen corner; or, make
a short C program that does something like:

int main (int argc, char *argv[]) {
   [read system time]
   [shell gcc with the same arguments]
   [read system time, subtract earlier time]
   [convert it into readable text and print it]
}


--
    .*.  "Clouds are not spheres, mountains are not cones, coastlines are not
 -()  <  circles, and bark is not smooth, nor does lightning travel in a
    `*'  straight line."    ,------------------------------------------------
         -- B. Mandelbrot  |  Paul Derbyshire (PGD) ao950 AT freenet DOT carleton DOT ca