public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/107461] [12/13 Regression] ambiguity error for friend with templated constexpr argument Date: Sat, 04 Feb 2023 10:39:40 +0000 [thread overview] Message-ID: <bug-107461-4-dPo6XDUXAf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107461-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107461 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 |P1 Summary|[12 Regression] ambiguity |[12/13 Regression] |error for friend with |ambiguity error for friend |templated constexpr |with templated constexpr |argument |argument
next prev parent reply other threads:[~2023-02-04 10:39 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-30 8:17 [Bug c++/107461] New: GCC rejects program with ambiguity error jlame646 at gmail dot com 2022-10-30 19:13 ` [Bug c++/107461] " pinskia at gcc dot gnu.org 2022-11-08 14:19 ` [Bug c++/107461] [12/13 Regression] ambiguity error for friend with templated constexpr argument ppalka at gcc dot gnu.org 2023-01-13 11:37 ` rguenth at gcc dot gnu.org 2023-02-03 14:41 ` cvs-commit at gcc dot gnu.org 2023-02-03 15:07 ` [Bug c++/107461] [12 " cvs-commit at gcc dot gnu.org 2023-02-03 15:08 ` ppalka at gcc dot gnu.org 2023-02-04 7:26 ` raj.khem at gmail dot com 2023-02-04 10:37 ` jakub at gcc dot gnu.org 2023-02-04 10:39 ` jakub at gcc dot gnu.org 2023-02-04 10:39 ` jakub at gcc dot gnu.org [this message] 2023-02-04 17:02 ` [Bug c++/107461] [12/13 " ppalka at gcc dot gnu.org 2023-02-04 17:04 ` ppalka at gcc dot gnu.org 2023-02-04 17:14 ` jakub at gcc dot gnu.org 2023-02-06 2:35 ` cvs-commit at gcc dot gnu.org 2023-02-06 3:01 ` ppalka at gcc dot gnu.org 2023-02-06 16:33 ` [Bug c++/107461] [12 " cvs-commit at gcc dot gnu.org 2023-02-06 16:36 ` ppalka at gcc dot gnu.org 2023-03-03 14:12 ` ppalka 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-107461-4-dPo6XDUXAf@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).