From: Tom Tromey <tom@tromey.com>
To: Gary Benson via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix gdb.python/py-format-string.exp with Clang
Date: Thu, 22 Oct 2020 12:53:51 -0600 [thread overview]
Message-ID: <87k0vi148w.fsf@tromey.com> (raw)
In-Reply-To: <1602691187-19392-1-git-send-email-gbenson@redhat.com> (Gary Benson via Gdb-patches's message of "Wed, 14 Oct 2020 16:59:47 +0100")
>>>>> "Gary" == Gary Benson via Gdb-patches <gdb-patches@sourceware.org> writes:
Gary> Hi all,
Gary> GDB includes the virtual table pointer when formatting polymorphic
Gary> C++ objects for printing, but GCC and Clang name these differently:
Gary> GCC emits a DW_AT_name of "_vptr.Base" when describing the virtual
Gary> table pointer of a type derived from type "Base", whereas Clang
Gary> will emit "_vptr$Base" in this situation. This patch fixes a
Gary> testcase which failed because of this.
Gary> Checked on Fedora 32 x86_64, with GCC and Clang. Ok to commit?
This is ok. Thank you.
Tom
next prev parent reply other threads:[~2020-10-22 18:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 15:59 Gary Benson
2020-10-22 18:53 ` Tom Tromey [this message]
2020-10-27 17:04 ` Gary Benson
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=87k0vi148w.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
/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).