Mail Archives: djgpp/1996/07/16/08:34:11
Date: | Tue, 16 Jul 1996 08:25:50 -0400
|
Message-Id: | <199607161225.IAA19062@delorie.com>
|
From: | DJ Delorie <dj>
|
To: | ei39594 AT ios DOT chalmers DOT se
|
CC: | djgpp AT delorie DOT com
|
In-reply-to: | <4sdqm0$of6@nyheter.chalmers.se> (message from Arash on 15 Jul
|
| 1996 16:12:48 GMT)
|
Subject: | Re: c:\Compiling............ Zzzzz..... :)
|
> 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 :(
As a benchmark, I could compile all of gcc on my 486/66 in 16M ram in
about half an hour. If it takes you longer than that (scale for clock
speeds), your system isn't configured right.
Please read the section of the FAQ about tuning your system.
> I don't know anything about compilers, but i think if someone rewrited
> the scanner/parser-part and hard-coded all that stuff things should go a
> lot faster, but that's just to hard...
Do you realize that gcc is about 30 Mb of source code? Do you realize
that there are thousands of people already working on gcc, including
how to make it faster in general?
> I think everyone agrees when i say that to much "UNIXism" has made DJGPP
> slow :)
Hey! We've been improving the speed for about ten years now. Compile
speed is about par with Borland if your system is configured right.
I'd also like to know which unixisms you'd like to throw away, and why
you feel that they'd improve the compilation speed.
- Raw text -