From: Tom Tromey <tromey@adacore.com>
To: Tom de Vries <tdevries@suse.de>
Cc: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] Fix .gdb_index with Ada
Date: Fri, 14 Oct 2022 07:24:08 -0600 [thread overview]
Message-ID: <87r0zao7wn.fsf@tromey.com> (raw)
In-Reply-To: <243a535f-e79a-c52c-f5f8-1b03d332b564@suse.de> (Tom de Vries's message of "Thu, 13 Oct 2022 23:44:20 +0200")
>> 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.
>>
Tom> Ah, does that then fix the c-linkage-name.exp regression?
Yeah. I'm testing the updated series now, I hope to send it today.
Tom
prev parent reply other threads:[~2022-10-14 13:24 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
2022-10-14 13:24 ` Tom Tromey [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=87r0zao7wn.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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).