This is the mail archive of the gcc-patches@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: The speed of the compiler, was: Re: Combine four insns


On Aug 9, 2010, at 8:26 AM, Diego Novillo wrote:
> Additionally, the very worst offender in terms of compile time is -g. The size of debugging information is such, that I/O and communication times increase significantly.

Well, if one uses a technology to engineer out the possibility of creating/moving/copying/assembling that information...  Apple found it beneficial to leave it behind in the .o files and has the debugger go look in the .o files...  more can be done.

For example, the front-end could tap into a live database directly and avoid much of the cost.  Instead of writing out the same information 100 times for 100 translation units, the first one writes, then next just punt to the first.  Of course, you'd have to be willing to sign up for the downside of this sort of scheme.  Another possibility would be to create the data very lazily (little of the debug information ever created is ever used)...


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