public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/96303] [10/11 Regression] Ambiguous overload for operator!= for std::__debug::bitset compiled with -std=c++20 and -pedantic. Date: Thu, 23 Jul 2020 19:18:57 +0000 [thread overview] Message-ID: <bug-96303-4-qrtWcSoUxe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96303-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96303 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org Last reconfirmed| |2020-07-23 Status|UNCONFIRMED |ASSIGNED Known to work| |9.3.0 Known to fail| |10.2.0, 11.0 Summary|Ambiguous overload for |[10/11 Regression] |operator!= for |Ambiguous overload for |std::__debug::bitset |operator!= for |compiled with -std=c++20 |std::__debug::bitset |and -pedantic. |compiled with -std=c++20 | |and -pedantic. Target Milestone|--- |10.3 Keywords| |rejects-valid --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> --- Yes I didn't realise the debug bitset defines its own rel ops. I wonder if it really needs them at all.
next prev parent reply other threads:[~2020-07-23 19:18 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-23 19:01 [Bug libstdc++/96303] New: " matt.lawson at precisionplanting dot com 2020-07-23 19:18 ` redi at gcc dot gnu.org [this message] 2020-08-07 19:29 ` [Bug libstdc++/96303] [10/11 Regression] " cvs-commit at gcc dot gnu.org 2020-08-07 19:46 ` cvs-commit at gcc dot gnu.org 2020-08-07 19:46 ` redi at gcc dot gnu.org 2020-08-27 12:37 ` 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-96303-4-qrtWcSoUxe@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).