public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dje at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/67440] New: pretty-printing of a const set<foo> fails
Date: Thu, 03 Sep 2015 00:18:00 -0000	[thread overview]
Message-ID: <bug-67440-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67440

            Bug ID: 67440
           Summary: pretty-printing of a const set<foo> fails
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dje at google dot com
  Target Milestone: ---

Type lookup in the pretty-printer of const set<foo> fails, set<foo> should be
used instead.

With the attached changes to the testcase, before the attached patch, one sees:

Python Exception <type 'exceptions.ValueError'> Cannot find type const
std::__debug::set<int, std::less<int>, std::allocator<int> >::_Rep_type:

Index: testsuite/libstdc++-prettyprinters/simple.cc
===================================================================
--- testsuite/libstdc++-prettyprinters/simple.cc        (revision 227421)
+++ testsuite/libstdc++-prettyprinters/simple.cc        (working copy)
@@ -73,6 +73,9 @@
   std::map<std::string, int>::iterator mpiter = mp.begin();
 // { dg-final { note-test mpiter {{first = "zardoz", second = 23}} } }

+  const std::set<int> const_intset = {2, 3};
+// { dg-final { note-test const_intset {std::set with 2 elements = {[0] = 2,
[1] = 3}} } }
+
   std::set<std::string> sp;
   sp.insert("clownfish");
   sp.insert("barrel");


             reply	other threads:[~2015-09-03  0:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-03  0:18 dje at google dot com [this message]
2015-09-03  0:24 ` [Bug libstdc++/67440] " dje at google dot com
2015-09-03 10:05 ` redi at gcc dot gnu.org

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=bug-67440-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).