public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: "François Dumont" <frs.dumont@gmail.com>
Cc: "libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH][_GLIBCXX_INLINE_VERSION] Fix std::span pretty printer
Date: Thu, 26 May 2022 00:34:10 +0100	[thread overview]
Message-ID: <CACb0b4kK=onHYT+BYg6k=G04_EqiG=6HouXGbGJmzeeWzCX7WA@mail.gmail.com> (raw)
In-Reply-To: <c471c1e2-fc87-d313-4d01-85b10b9f75d7@gmail.com>

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
>
>      libstdc++: [_GLIBCXX_INLINE_VERSION] Fix std::span pretty printer
>
>      libstdc++-v3/ChangeLog:
>
>              * python/libstdcxx/v6/printers.py (StdSpanPrinter.__init__):
>              Strip typename from version namespace.
>
> Tested under Linux x86_64 _GLIBCXX_INLINE_VERSION mode.
>
> Ok to commit ?

OK, thanks.


  reply	other threads:[~2022-05-25 23:34 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 [this message]
2022-05-25 23:38   ` Jonathan Wakely
2022-05-26  9:21     ` Jonathan Wakely
2022-05-26  9:40       ` François Dumont
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='CACb0b4kK=onHYT+BYg6k=G04_EqiG=6HouXGbGJmzeeWzCX7WA@mail.gmail.com' \
    --to=jwakely@redhat.com \
    --cc=frs.dumont@gmail.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).