public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Alexander Lindsay <alexlindsay239@gmail.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: Noted slowness in profile loading with binutils 2.37
Date: Fri, 11 Feb 2022 10:17:17 -0800	[thread overview]
Message-ID: <CANFcJrEPzxHscaQRefWw3aXMUs9kQx4_mq5bLyqHscHwiARvow@mail.gmail.com> (raw)
In-Reply-To: <CANFcJrFSNBFf=-mtssSYOXCmTyx1ivuZWAa3hFtYGrMOTS98iA@mail.gmail.com>

So it looks like you were spot-on

On Fri, Feb 11, 2022 at 10:16 AM Alexander Lindsay <alexlindsay239@gmail.com>
wrote:

> Hi Nick,
>
> This was the result of my bisect:
>
> ca8f6bc629cb27792ce449e7253c74a3f6f75fda is the first bad commit
> Date:   Tue Mar 2 16:08:23 2021 +0000
>
>     Fix the BFD library's parsing of DIEs where specification attributes
> can refer to variables that are defined later on.
>
>             PR 27484
>             * dwarf2.c (scan_unit_for_symbols): Scan twice, once to
> accumulate
>             function and variable tags and a second time to resolve their
>             attributes.
>
>  bfd/ChangeLog |   7 ++++
>  bfd/dwarf2.c  | 133
> ++++++++++++++++++++++++++++++++++++++++++++++------------
>  2 files changed, 114 insertions(+), 26 deletions(-)
>
> On Thu, Feb 10, 2022 at 3:00 AM Nick Clifton <nickc@redhat.com> wrote:
>
>> Hi Alexander,
>>
>> > - binutils version 2.36.1: 6.5 seconds
>> > - binutils version 2.37: Still not loaded at 6 minutes
>> >
>> > I think the relevant binutil tool here is addr2line. Does anyone have a
>> > quick idea for what may have caused the slow-down?
>>
>> It will be a change in the BFD library.  More specifically it
>> is likely to be a change to bfd/dwarf2.c.  Have a look at the
>> ChangeLog in the bfd/ directory for the 2.37 release for more
>> hints.
>>
>> I suspect, but do not know for sure, that it could be the patch
>> for PR 27484 ....
>>
>> Cheers
>>    Nick
>>
>>
>>

  reply	other threads:[~2022-02-11 18:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08 17:44 Alexander Lindsay
2022-02-08 17:57 ` H.J. Lu
2022-02-08 18:45   ` Alexander Lindsay
2022-02-09  1:09 ` Alan Modra
2022-02-10 11:00 ` Nick Clifton
2022-02-11 18:16   ` Alexander Lindsay
2022-02-11 18:17     ` Alexander Lindsay [this message]
2022-02-14 14:18       ` Nick Clifton

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=CANFcJrEPzxHscaQRefWw3aXMUs9kQx4_mq5bLyqHscHwiARvow@mail.gmail.com \
    --to=alexlindsay239@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=nickc@redhat.com \
    /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).