From: Jonathan Wakely <jwakely@redhat.com>
To: "Hoyer, David" <David.Hoyer@netapp.com>
Cc: libstdc++ <libstdc++@gcc.gnu.org>, gcc-patches@gcc.gnu.org
Subject: Re: printers.py issue
Date: Thu, 11 Mar 2021 17:56:28 +0000 [thread overview]
Message-ID: <20210311175628.GF3008@redhat.com> (raw)
In-Reply-To: <DM5PR06MB280975DD7FF0C2E9130A797E92919@DM5PR06MB2809.namprd06.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 513 bytes --]
On 10/03/21 16:57 +0000, Hoyer, David wrote:
>I wanted to finally follow up on these issues I reported.
>
>On issue 1, the patch you provided did fix the problem
Thanks for confirming. It's committed to the master branch now (as
attached to this mail). I also plan to backport it to the active
release branches later.
>On issue 2, I changed our python script to convert it to a string and it now works!
Great. I think it's correct that those constructor methods expect
strings for the 'typename' parameter.
[-- Attachment #2: patch.txt --]
[-- Type: text/x-patch, Size: 1576 bytes --]
commit 9dacc828bf8b087ddfaf797ed7238da45609082c
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Thu Mar 11 16:48:32 2021
libstdc++: Fix find_type helper to work consistently
The find_type helper function sometimes results in "class X::name" and
lookup for that fails. For more details see "Problem 1" in
https://gcc.gnu.org/pipermail/libstdc++/2021-March/052132.html and the
example at https://sourceware.org/bugzilla/show_bug.cgi?id=27510#c2
This patch replaces typ.unqualified() with typ.tag, which is never
qualified, and will never include the 'class' or 'struct' keywords.
Using the .tag attribute should be safe here because we know we are
looking at a class type and we've already used strip_typedefs().
libstdc++-v3/ChangeLog:
* python/libstdcxx/v6/printers.py (find_type): Use tag attribute
instead of unqualified() method.
diff --git a/libstdc++-v3/python/libstdcxx/v6/printers.py b/libstdc++-v3/python/libstdcxx/v6/printers.py
index 00db6cb4e82..550e0ecdd22 100644
--- a/libstdc++-v3/python/libstdcxx/v6/printers.py
+++ b/libstdc++-v3/python/libstdcxx/v6/printers.py
@@ -85,8 +85,8 @@ except ImportError:
def find_type(orig, name):
typ = orig.strip_typedefs()
while True:
- # Strip cv-qualifiers. PR 67440.
- search = '%s::%s' % (typ.unqualified(), name)
+ # Use Type.tag to ignore cv-qualifiers. PR 67440.
+ search = '%s::%s' % (typ.tag, name)
try:
return gdb.lookup_type(search)
except RuntimeError:
next prev parent reply other threads:[~2021-03-11 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DM5PR06MB28097C4E645110031875A391929D9@DM5PR06MB2809.namprd06.prod.outlook.com>
2021-02-26 22:27 ` Jonathan Wakely
2021-02-26 22:31 ` Hoyer, David
2021-03-04 4:35 ` Hoyer, David
2021-03-04 11:47 ` Jonathan Wakely
2021-03-04 14:19 ` Hoyer, David
2021-03-04 14:57 ` Jonathan Wakely
2021-03-10 16:57 ` Hoyer, David
2021-03-11 17:56 ` Jonathan Wakely [this message]
2021-03-11 18:33 ` Hoyer, David
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=20210311175628.GF3008@redhat.com \
--to=jwakely@redhat.com \
--cc=David.Hoyer@netapp.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.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).