From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] Fix .gdb_index with Ada
Date: Thu, 13 Oct 2022 23:44:20 +0200 [thread overview]
Message-ID: <243a535f-e79a-c52c-f5f8-1b03d332b564@suse.de> (raw)
In-Reply-To: <871qrbpico.fsf@tromey.com>
On 10/13/22 22:40, Tom Tromey wrote:
> Tom> [ ... patch ... ]
> Tom> fixes the FAIL, so is this one of the "rare and not worth supporting"
> Tom> cases you're referring to?
>
>> I thought that was necessary to avoid redundancy in the index, but I see
>> now it isn't, or at least not in that way. I'm looking again at why the
>> new indices are larger in general.
>
> I looked into this more.
>
> Older versions of gdb don't add C++ symbols to the index, so when I
> diff'd the indexes I saw a lot of "_Z" additions. Locally I've changed
> this code to skip linkage names for C++ only.
>
Ah, does that then fix the c-linkage-name.exp regression?
Thanks,
- Tom
> I compared the symbols from old and new indexes. In every case (except
> the one below) I checked, the new gdb seemed more correct. In
> particular it added inlined functions to the index, and it used the
> correct name for "enum class" enumerator constants.
>
> I did find out that the new index included entries for the linkage names
> of classes. This isn't generally useful, and they have weird names like
> "6mumble", so I also have a patch to drop these entries from the cooked
> index entirely.
>
> Tom
next prev parent reply other threads:[~2022-10-13 21:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 20:20 Tom Tromey
2022-09-22 20:20 ` [PATCH 1/2] Improve Ada support in .gdb_index Tom Tromey
2022-09-22 20:20 ` [PATCH 2/2] Change .gdb_index de-duplication implementation Tom Tromey
2022-09-28 2:00 ` [PATCH 0/2] Fix .gdb_index with Ada Tom de Vries
2022-10-11 19:59 ` Tom Tromey
2022-10-13 20:40 ` Tom Tromey
2022-10-13 21:44 ` Tom de Vries [this message]
2022-10-14 13:24 ` Tom Tromey
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=243a535f-e79a-c52c-f5f8-1b03d332b564@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=tromey@adacore.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).