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]

speedup collect2 (by not using it)


These patches speed up compiles by around 2.8% on Finder_FE by not trying to using collect2 when it isn't necessary. This is about 62ms per compile. If collect2 is in use for collecting (USE_COLLECT2 is defined), then these changes don't have any effect, otherwise, if -frepo is given, collect2 is used, otherwise, we use ld as normal.

So, the question is, does collect2 ever do anything interesting when USE_COLLECT2 isn't defined and -frepo isn't given? Problem areas might be IBM (COLLECT_EXPORT_LIST). If aix is a problem, we can always do collect2 when COLLECT_EXPORT_LIST is defined.

Another question would be, do we trust gcc.c to be able to find ld as well as collect2.c can find ld? :-( Answer should be yes, but in practice, there could be bugs.

So, does this sound reasonable?

Attachment: collect2-fsf-2.diffs
Description: Binary data


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