public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/115139] [14 Regression] Enum inside variadic template class can't define one of self with usage another value from this enum Date: Fri, 17 May 2024 14:49:31 +0000 [thread overview] Message-ID: <bug-115139-4-MQeOupXrW2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115139-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115139 Patrick Palka <ppalka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |14.2 Assignee|unassigned at gcc dot gnu.org |ppalka at gcc dot gnu.org Ever confirmed|0 |1 Last reconfirmed| |2024-05-17 Status|UNCONFIRMED |ASSIGNED Keywords| |ice-on-valid-code Summary|Enum inside variadic |[14 Regression] Enum inside |template class can't define |variadic template class |one of self with usage |can't define one of self |another value from this |with usage another value |enum |from this enum CC| |ppalka at gcc dot gnu.org --- Comment #1 from Patrick Palka <ppalka at gcc dot gnu.org> --- Confirmed, started with r14-4796-g3e3d73ed5e85e7. Interestingly r15-123-gf04dc89a991ddc made us accept this testcase on trunk, so this is a 14 regression only.
next prev parent reply other threads:[~2024-05-17 14:49 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-17 14:27 [Bug c++/115139] New: " pavel at karpychev dot name 2024-05-17 14:49 ` ppalka at gcc dot gnu.org [this message] 2024-05-21 19:54 ` [Bug c++/115139] [14 Regression] " cvs-commit at gcc dot gnu.org 2024-05-21 20:16 ` cvs-commit at gcc dot gnu.org 2024-05-21 20:16 ` ppalka at gcc dot gnu.org 2024-05-22 11:48 ` pavel at karpychev dot name
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-115139-4-MQeOupXrW2@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).