public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "David M. Lee" <dmlee@Crossroads.com>
To: "H. J. Lu" <hjl@lucon.org>
Cc: <binutils@sourceware.org>
Subject: RE: Excessive link time with 2.16.1
Date: Mon, 19 Jun 2006 20:26:00 -0000	[thread overview]
Message-ID: <43F5E8AE07F17C47BC16F7A159E9E700950683@mailnode1.commstor.crossroads.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2126 bytes --]

I tried binutils 2.17.50.0.2.  The link time was over 10 minutes.

I finally got it to run with the profiler.  Looks like the bulk of the
time is spent in qsort, called from bfd_elf_match_symbols_in_sections.

I've attached the output from gprof.

dave
<><


-----Original Message-----
From: H. J. Lu [mailto:hjl@lucon.org] 
Sent: Thursday, June 15, 2006 12:01 AM
To: David M. Lee
Cc: binutils@sourceware.org
Subject: Re: Excessive link time with 2.16.1


On Wed, Jun 14, 2006 at 10:06:15PM -0500, David M. Lee wrote:
> 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.
> 

The Linux binutils 2.17.50.0.2 includes that patch.


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.

[-- Attachment #2: gmon.txt.gz --]
[-- Type: application/x-gzip, Size: 56088 bytes --]

             reply	other threads:[~2006-06-19 20:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19 20:26 David M. Lee [this message]
2006-06-19 20:27 ` H. J. Lu
  -- strict thread matches above, loose matches on Subject: below --
2006-06-15  5:01 David M. Lee
2006-06-15  7:53 ` H. J. Lu
2006-06-13 18:58 David M. Lee
2006-06-13 19:01 ` H. J. Lu
2006-06-13 16:20 David M. Lee
2006-06-13 17:58 ` H. J. Lu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43F5E8AE07F17C47BC16F7A159E9E700950683@mailnode1.commstor.crossroads.com \
    --to=dmlee@crossroads.com \
    --cc=binutils@sourceware.org \
    --cc=hjl@lucon.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).