public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "uecker at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/112571] New: ICE with nested redefinition of enum Date: Thu, 16 Nov 2023 18:42:27 +0000 [thread overview] Message-ID: <bug-112571-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112571 Bug ID: 112571 Summary: ICE with nested redefinition of enum Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: uecker at gcc dot gnu.org Target Milestone: --- The following code ICEs on trunk but not on 13.2 with -std=c2x typedef __SIZE_TYPE__ size_t; enum h : typeof (enum h { D }) { D }; https://godbolt.org/z/cd1o75M3W
next reply other threads:[~2023-11-16 18:42 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-16 18:42 uecker at gcc dot gnu.org [this message] 2023-11-16 18:45 ` [Bug c/112571] " uecker at gcc dot gnu.org 2023-11-19 20:04 ` [Bug c/112571] [13/14 Regression] " pinskia at gcc dot gnu.org 2024-01-31 21:40 ` cvs-commit at gcc dot gnu.org 2024-01-31 21:44 ` jsm28 at gcc dot gnu.org 2024-03-23 21:44 ` [Bug c/112571] [13 " pinskia at gcc dot gnu.org 2024-03-25 22:51 ` cvs-commit at gcc dot gnu.org 2024-03-25 22:54 ` jsm28 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-112571-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: 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).