From: "François Dumont" <frs.dumont@gmail.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: "libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>
Subject: Re: [PATCH][_GLIBCXX_INLINE_VERSION] Fix std::span pretty printer
Date: Thu, 26 May 2022 11:40:20 +0200 [thread overview]
Message-ID: <0fb0ade2-7d75-08fa-d65f-7d71a591681b@gmail.com> (raw)
In-Reply-To: <CACb0b4nicGZ5RwtZdgiX3_vFoZO_nFTOK+o1NHNGLPJV=oKWoA@mail.gmail.com>
On 26/05/22 11:21, Jonathan Wakely wrote:
> On Thu, 26 May 2022 at 00:38, Jonathan Wakely <jwakely@redhat.com> wrote:
>> On Thu, 26 May 2022 at 00:34, Jonathan Wakely <jwakely@redhat.com> wrote:
>>> On Wed, 25 May 2022 at 21:29, François Dumont via Libstdc++
>>> <libstdc++@gcc.gnu.org> wrote:
>>>> Hi
>>>>
>>>> Here is a patch to fix std::span pretty printer in versioned
>>>> namespace mode.
>>>>
>>>> Note that there is still a problem with std::atomic after this patch.
>>>>
>>>> got: $13 = std::atomic<std::__8::shared_ptr<int>> (empty) = {get() = 0x0}
>>>> FAIL: libstdc++-prettyprinters/cxx20.cc print spe
>> Does this fix it?
>>
>> --- a/libstdc++-v3/python/libstdcxx/v6/printers.py
>> +++ b/libstdc++-v3/python/libstdcxx/v6/printers.py
>> @@ -1734,6 +1734,7 @@ class StdAtomicPrinter:
>> impl = val['_M_impl']
>> self.shptr_printer = SharedPointerPrinter(typename, impl)
>> self.children = self._shptr_children
>> + self.typename = self.typename.replace(self.value_type.tag, typ)
>>
>> def _shptr_children(self):
>> return SmartPtrIterator(self.shptr_printer.pointer)
>>
>>
>> I'll test it with a versioned-namespace build tomorrow.
> No, that didn't work, but the attached patch does. Pushed to trunk.
Great, I just pushed mine too.
Thanks
next prev parent reply other threads:[~2022-05-26 9:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 20:26 François Dumont
2022-05-25 23:34 ` Jonathan Wakely
2022-05-25 23:38 ` Jonathan Wakely
2022-05-26 9:21 ` Jonathan Wakely
2022-05-26 9:40 ` François Dumont [this message]
2022-05-26 14:49 ` Jonathan Wakely
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=0fb0ade2-7d75-08fa-d65f-7d71a591681b@gmail.com \
--to=frs.dumont@gmail.com \
--cc=jwakely@redhat.com \
--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).