This is the mail archive of the binutils@sourceware.org mailing list for the binutils 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: Excessive link time with 2.16.1


Interesting.

Here are the link times for the example mentioned in PR2342 and my application for various binutils.  The patch helped a lot, but it's not the only problem.

       | 2.15.94.0.2.2 |  2.16.1 | 2.16.1 +PR2342 patch
-------+---------------+---------+---------------------
slowld |    4m 17s     |  4m 16s |       15s
myapp  |       11s     | 13m 03s |    1m 07s

So the patch definitely fixes the problem the 'slowld' example had, and addresses most of the problem with myapp.

I'll try and run with a profiler to see if I can figure out where all the time is being spent.

BTW: in order to apply http://sourceware.org/ml/binutils/2006-04/msg00329.html, I had to apply http://sourceware.org/cgi-bin/cvsweb.cgi/src/bfd/elflink.c.diff?r1=1.143&r2=1.144&cvsroot=src first.

dave
<><


-----Original Message-----
From: H. J. Lu [mailto:hjl@lucon.org] 
Sent: Tuesday, June 13, 2006 1:58 PM
To: David M. Lee
Cc: binutils@sourceware.org
Subject: Re: Excessive link time with 2.16.1


On Tue, Jun 13, 2006 at 01:09:57PM -0500, David M. Lee wrote:
> Unfortunately, no.
> 

I was wondering if it was the same as

http://sources.redhat.com/bugzilla/show_bug.cgi?id=2342#c9


H.J.



CONFIDENTIAL: This email, including its contents and attachments, if any, are confidential. If the reader of this e-mail is not an intended recipient, you have received this e-mail in error and any review, dissemination, distribution or copying is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by return e-mail at [emailaddress@crossroads.com] and permanently delete the copy you received. Copyright and other intellectual property rights in its contents are the sole property of Crossroads Systems, Inc. Email transmission cannot be guaranteed to be secure or error-free. The sender therefore does not accept liability for any errors or omissions in the contents of the message which arise as a result of email  transmission.  Although we routinely screen for viruses, addressees should check this email and any attachments for viruses. We make no representation or warranty as to the absence of viruses in this email or any attachments.


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