This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/8108] Problem in the code generator for C and the linker is extremelly slow
- From: "stephan dot tobies at nokia dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 30 Mar 2004 14:17:34 -0000
- Subject: [Bug c/8108] Problem in the code generator for C and the linker is extremelly slow
- References: <20021001081602.8108.manuel.serrano@sophia.inria.fr>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From stephan dot tobies at nokia dot com 2004-03-30 14:17 -------
Subject: Re: Problem in the code generator for C and the linker
is extremelly slow
ext Manuel Serrano wrote:
> [snip]
>
>>There is a version of the binutils in the making (2.15) which will solve
>>the problem from the point of view of ld. They have a much improved
>>string merging algorithm that reduces link times for me from ~3000s to
>>~40s. This is still worse than the original ~7s (for gcc-2.95.x
>>generated objects) but it is 2 orders of magnitudes down.
>>
>>
>I would by, at once, a 2x slowdown ;-)
>
>
I have profiled this some more. Most of the time spent now during
linking is no longer in the string merging, but instead in the general
merging process. I have basically no clue of how object files are
structured and how linking takes places, but it would seem to me that ld
has done most of what they can do to solve the problem of the increased
link time.
I cannot judge if the slow down in the linker is now still due to the
way that debug information is represented, of if this is general
problem/feature of how the later gcc's structure the object files. Maybe
somebody from the gcc maintainers will take on this problem - I would
offer my help to nail down the problem.
BR
Stephan
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8108