public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc r11-2637] libstdc++: Fix compatibility support in unique_ptr pretty printer Date: Mon, 10 Aug 2020 17:48:15 +0000 (GMT) [thread overview] Message-ID: <20200810174815.6FF8A385702F@sourceware.org> (raw) https://gcc.gnu.org/g:ed11f7e84bcae89f486f5023e566726a7faa7dd4 commit r11-2637-ged11f7e84bcae89f486f5023e566726a7faa7dd4 Author: Jonathan Wakely <jwakely@redhat.com> Date: Mon Aug 10 18:44:06 2020 +0100 libstdc++: Fix compatibility support in unique_ptr pretty printer The support for the old std::unique_ptr implementation was failing, because it tried to work on a typedef instead of the underlying type. The test supposed to verify the support worked wasn't using a typedef, so didn't notice the problem. libstdc++-v3/ChangeLog: * python/libstdcxx/v6/printers.py (UniquePointerPrinter.__init__): Use gdb.Type.strip_typedefs(). * testsuite/libstdc++-prettyprinters/compat.cc: Use a typedef in the emulated old type. Diff: --- libstdc++-v3/python/libstdcxx/v6/printers.py | 6 +++--- libstdc++-v3/testsuite/libstdc++-prettyprinters/compat.cc | 4 +++- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/libstdc++-v3/python/libstdcxx/v6/printers.py b/libstdc++-v3/python/libstdcxx/v6/printers.py index 0bf307b8e5f..c0f061f79c1 100644 --- a/libstdc++-v3/python/libstdcxx/v6/printers.py +++ b/libstdc++-v3/python/libstdcxx/v6/printers.py @@ -245,7 +245,7 @@ class UniquePointerPrinter: def __init__ (self, typename, val): self.val = val - impl_type = val.type.fields()[0].type.tag + impl_type = val.type.fields()[0].type.strip_typedefs() # Check for new implementations first: if is_specialization_of(impl_type, '__uniq_ptr_data') \ or is_specialization_of(impl_type, '__uniq_ptr_impl'): @@ -253,7 +253,7 @@ class UniquePointerPrinter: elif is_specialization_of(impl_type, 'tuple'): tuple_member = val['_M_t'] else: - raise ValueError("Unsupported implementation for unique_ptr: %s" % impl_type) + raise ValueError("Unsupported implementation for unique_ptr: %s" % str(impl_type)) tuple_impl_type = tuple_member.type.fields()[0].type # _Tuple_impl tuple_head_type = tuple_impl_type.fields()[1].type # _Head_base head_field = tuple_head_type.fields()[0] @@ -262,7 +262,7 @@ class UniquePointerPrinter: elif head_field.is_base_class: self.pointer = tuple_member.cast(head_field.type) else: - raise ValueError("Unsupported implementation for tuple in unique_ptr: %s" % impl_type) + raise ValueError("Unsupported implementation for tuple in unique_ptr: %s" % str(impl_type)) def children (self): return SmartPtrIterator(self.pointer) diff --git a/libstdc++-v3/testsuite/libstdc++-prettyprinters/compat.cc b/libstdc++-v3/testsuite/libstdc++-prettyprinters/compat.cc index f1c3b599634..c681becf8b9 100644 --- a/libstdc++-v3/testsuite/libstdc++-prettyprinters/compat.cc +++ b/libstdc++-v3/testsuite/libstdc++-prettyprinters/compat.cc @@ -53,7 +53,9 @@ namespace std { unique_ptr(T* p) { _M_t._M_head_impl = p; } - tuple<T*, D> _M_t; + using __tuple_type = tuple<T*, D>; + + __tuple_type _M_t; }; // Old representation of std::optional, before GCC 9
reply other threads:[~2020-08-10 17:48 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200810174815.6FF8A385702F@sourceware.org \ --to=redi@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ --cc=libstdc++-cvs@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: linkBe 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).