public inbox for
help / color / mirror / Atom feed
From: "Franथईois Dumont" <>
Subject: [gcc r13-2766] libstdc++: Remove useless gdb printer registrations
Date: Thu, 22 Sep 2022 04:24:00 +0000 (GMT)	[thread overview]
Message-ID: <> (raw)

commit r13-2766-g42630dc056ddf2dbe012aa7cc8eee09c5b960102
Author: François Dumont <>
Date:   Wed Sep 21 18:59:43 2022 +0200

    libstdc++: Remove useless gdb printer registrations
            * python/libstdcxx/v6/ Remove ptinter registration for non-existing
            types std::__debug::unique_ptr, std::__debug::stack, std::__debug::queue,

 libstdc++-v3/python/libstdcxx/v6/ | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/libstdc++-v3/python/libstdcxx/v6/ b/libstdc++-v3/python/libstdcxx/v6/
index bd4289c1c62..5a3dcbd13f9 100644
--- a/libstdc++-v3/python/libstdcxx/v6/
+++ b/libstdc++-v3/python/libstdcxx/v6/
@@ -2246,12 +2246,7 @@ def build_libstdcxx_dictionary ():
     libstdcxx_printer.add('std::__debug::map', StdMapPrinter)
     libstdcxx_printer.add('std::__debug::multimap', StdMapPrinter)
     libstdcxx_printer.add('std::__debug::multiset', StdSetPrinter)
-    libstdcxx_printer.add('std::__debug::priority_queue',
-                          StdStackOrQueuePrinter)
-    libstdcxx_printer.add('std::__debug::queue', StdStackOrQueuePrinter)
     libstdcxx_printer.add('std::__debug::set', StdSetPrinter)
-    libstdcxx_printer.add('std::__debug::stack', StdStackOrQueuePrinter)
-    libstdcxx_printer.add('std::__debug::unique_ptr', UniquePointerPrinter)
     libstdcxx_printer.add('std::__debug::vector', StdVectorPrinter)
     # These are the TR1 and C++11 printers.

                 reply	other threads:[~2022-09-22  4:24 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).