From: Cary Coutant <ccoutant@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Doug Evans <dje@google.com>,
gdb-patches <gdb-patches@sourceware.org>,
Tom Tromey <tromey@redhat.com>,
Sterling Augustine <saugustine@google.com>,
Jakub Jelinek <jakub@redhat.com>
Subject: Re: [RFA] Work around binutils/15021
Date: Wed, 12 Jun 2013 19:50:00 -0000 [thread overview]
Message-ID: <CAHACq4oGwpHSr2eaN7GojfPZmWN2wgPWsg_TyPckEv2GOhQHLw@mail.gmail.com> (raw)
In-Reply-To: <20130612181619.GA13006@host2.jankratochvil.net>
>> The gold "bug" is that, when using pubnames(/pubtypes) to generate the
>> index, gold doesn't have sufficient info to generate as "accurate" a
>> .gdb_index ("accurate" as in: the CU will have a DW_AT_GNU_pubtypes
>> attribute when it would be better if the TU had that attribute).
>> If those sections are missing then gold falls back to reading all the
>> debug info and using that to generate the index, and when it does that
>> it can generate a better index, and I'm guessing that's what you're
>> seeing.
>
> I get the same .gdb_index content from gold even when I use -gpubnames.
Gold ignores the pubnames sections unless there's a DW_AT_GNU_pubtypes
attribute with a reference class form. If it's just a flag (as trunk
GCC generates), that's not sufficient. (I intend to fix gold to work
with this, but haven't done it yet.) On top of that, GCC doesn't put
that attribute in the TUs at all, so gold will always parse the debug
info in each TU. I think GCC needs to be fixed to emit that attribute
in each TU.
-cary
prev parent reply other threads:[~2013-06-12 18:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 23:21 Doug Evans
2013-01-17 17:53 ` Tom Tromey
2013-01-17 18:42 ` Doug Evans
2013-01-17 21:04 ` [RFA, doc RFA] " Doug Evans
2013-01-18 7:17 ` Eli Zaretskii
2013-01-18 14:32 ` Tom Tromey
2013-01-24 14:59 ` Regressions with dwz [Re: [RFA] Work around binutils/15021] Jan Kratochvil
[not found] ` <CADPb22SoND17XeXBL2N+-DXf+yKuWe4PJEXR86qT06-q_LA+7g@mail.gmail.com>
2013-01-24 17:16 ` Jan Kratochvil
2013-01-24 19:08 ` Jan Kratochvil
2013-01-30 20:41 ` Tom Tromey
2013-06-09 17:09 ` [RFA] Work around binutils/15021 Jan Kratochvil
2013-06-12 9:49 ` Doug Evans
2013-06-12 18:29 ` Jan Kratochvil
2013-06-12 19:50 ` Cary Coutant [this message]
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=CAHACq4oGwpHSr2eaN7GojfPZmWN2wgPWsg_TyPckEv2GOhQHLw@mail.gmail.com \
--to=ccoutant@google.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=jakub@redhat.com \
--cc=jan.kratochvil@redhat.com \
--cc=saugustine@google.com \
--cc=tromey@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