From:	tomw AT tsys DOT demon DOT co DOT uk (Tom Wheeley)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: gcc compiles so slow?
Date:	Fri, 20 Dec 96 01:54:49 GMT
Organization:	Adventures and Diving
Lines:	31
Distribution:	world
Message-ID:	<851046889snz@tsys.demon.co.uk>
References:	<58s98p$460 AT galileo DOT polito DOT it> <32B22D13 DOT 5E7D AT cs DOT com> <sZeFECAAvHuyEwUo AT chocolat DOT foobar DOT co DOT uk>
Reply-To:	tw104 AT york DOT ac DOT uk
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

On Wednesday, in article
     <sZeFECAAvHuyEwUo AT chocolat DOT foobar DOT co DOT uk>
     Paul AT foobar DOT co DOT uk DOT chocolat "Paul Shirley" wrote:

> >The overhead is a "fixed cost," though; it is constant.  It becomes
> >insignificant when your project is big enough.
> 
> It becomes insignificant IFF you compile increasingly large files OR you
> have sufficient caching capacity to avoid the 2nd and later loads of the
> compiler.

Not if you have say a 1 billion line source file.  Then the compile time
dwarfs the laoding-cpp/cc1/as/ld time.  That's also when borland or
whatever runs out of segments<g> and won't compile at all :^)

> If you have sufficient ram its completely possible that the compiler
> will only load once per session (guess who has lots of ram ;)

I think that must happen to me, because when djgpp gets started on the
Makefile in my project, it absolutely canes it through all but the first
source files and the linker stage.

(That's 16Mb RAM in a Win(eugh)95 dos box)

:sb)   please send mail to <tw104 AT york DOT ac DOT uk>   http://www.york.ac.uk/~tw104/
--
#include <stdio.h>                  /* The .splitbung super .sig system! */
#include <string.h>
main(){FILE*f;int c[1];char s[99];puts("sig:");fgets(s,99,stdin);if(!*c=strchr(s
,'\n'))s[c=0;f=fopen(s,"r");while((c=getc(f))!=EOF)putchar(c);f&&fclose(f)

- Raw text -