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] pretty-printing of a const set<foo> fails Date: Thu, 03 Sep 2015 00:24:00 -0000 [thread overview] Message-ID: <bug-67440-4-YMkIBYzPOb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67440-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67440 --- Comment #1 from Doug Evans <dje at google dot com> --- Created attachment 36288 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36288&action=edit patch + testcase This could use another set of eyes.
next prev parent reply other threads:[~2015-09-03 0:24 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-09-03 0:18 [Bug libstdc++/67440] New: " dje at google dot com 2015-09-03 0:24 ` dje at google dot com [this message] 2015-09-03 10:05 ` [Bug libstdc++/67440] " 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-YMkIBYzPOb@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: 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).