public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: "Steinar H. Gunderson" <sesse@google.com>, binutils@sourceware.org
Cc: sesse@chromium.org
Subject: Re: [PATCH] Add a trie to map quickly from address range to compilation unit.
Date: Wed, 23 Mar 2022 14:14:31 +0000	[thread overview]
Message-ID: <63191455-2374-5db9-f55e-ddf794c7d88e@redhat.com> (raw)
In-Reply-To: <20220321094030.1256430-1-sesse@google.com>

Hi Steinar,

> Add a radix-256 trie over the address space to quickly map address to
> compilation unit spaces; for content_shell, which is 1.6 GB when some
> (but not full) debug information turned is on, we go from 6 ms to
> 0.006 ms (6 µs) for each lookup from address to compilation unit, a 1000x
> speedup. There is still a slow part left in mapping to symbol name,
> but this at least gets us halfway there.

This patch appears to introduce some new failures into the various testsuites.
For example with a toolchain targeted at x86_64-pc-linux-gnu I see:

   GAS REGRESSION: DWARF2 debugging information 2
   GAS REGRESSION: DWARF2 debugging information 2 with SHF_COMPRESS
   GAS REGRESSION: 64bit DWARF2 debugging information 2
   GAS REGRESSION: 64bit DWARF2 debugging information 2 with SHF_COMPRESS
   LD REGRESSION:  Dump pr21978.so
   BIN REGRESSION: build-id-debuglink (grepping for source file name is disassembly output)

These all appear to be due to lack of line number information.  For example
the gas tests are failing because they are expecting to see a line like this:

   ./dw2-compress-2.c:6

But instead they are being given:

   ./dw2-compress-2.c:?

There are similar explanations for the other failures too.

Please could you look into this ?

Cheers
   Nick


  reply	other threads:[~2022-03-23 14:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21  9:40 Steinar H. Gunderson
2022-03-23 14:14 ` Nick Clifton [this message]
2022-03-23 15:53   ` Steinar H. Gunderson
2022-03-23 22:24   ` Steinar H. Gunderson
2022-03-24  5:22     ` Alan Modra
2022-03-24  8:01       ` Steinar H. Gunderson
2022-03-24 23:30         ` Alan Modra
2022-03-25  0:01           ` Steinar H. Gunderson
2022-03-28 10:19           ` Jan Beulich
2022-03-28 23:47             ` Alan Modra
2022-03-29  6:07               ` Jan Beulich
2022-03-31  6:21                 ` Steinar H. Gunderson
2022-04-03 11:39                   ` Alan Modra
2022-04-04  7:29                     ` Steinar H. Gunderson

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=63191455-2374-5db9-f55e-ddf794c7d88e@redhat.com \
    --to=nickc@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=sesse@chromium.org \
    --cc=sesse@google.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).