This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Suggestions for improving gcc 3.2 compilation speed?


On Friday, March 7, 2003, at 11:28 AM, Zack Weinberg wrote:
That's clever.  Do you think you could make this happen automatically
when more than one input file is given on cc1(plus)'s command line?  I
believe the Java front end does something like that already.

There are lots of possibilities. Zero-compile, compiler notes into the .o file the compile line, doesn't do any work, the driver, when doing a link, noticed these zero-compile .o files, and then invokes the compiler with all the relevant details. This preserves the current model and style of building.


Force the GUI development frontend to synth up such files (the ones with #pragma translationunit).

Insist that the compiler be given multiple .cc files on a single command line, if they want the speed up.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]