public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/67048] [9/10/11/12 Regression] GCC rejects well-formed program using empty anonymous enum specifier in a variable declaration Date: Fri, 29 Apr 2022 19:09:25 +0000 [thread overview] Message-ID: <bug-67048-4-gPVH4uhHiq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67048-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67048 Marek Polacek <mpolacek at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[9/10/11/12/13 Regression] |[9/10/11/12 Regression] GCC |GCC rejects well-formed |rejects well-formed program |program using empty |using empty anonymous enum |anonymous enum specifier in |specifier in a variable |a variable declaration |declaration --- Comment #5 from Marek Polacek <mpolacek at gcc dot gnu.org> --- Fixed for GCC 13 so far.
next prev parent reply other threads:[~2022-04-29 19:09 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-07-29 3:15 [Bug c++/67048] New: " anders.granlund.0 at gmail dot com 2015-07-29 9:24 ` [Bug c++/67048] " redi at gcc dot gnu.org 2021-08-04 22:07 ` [Bug c++/67048] [9/10/11/12 Regression] " pinskia at gcc dot gnu.org 2022-01-17 15:18 ` rguenth at gcc dot gnu.org 2022-01-31 15:27 ` marxin at gcc dot gnu.org 2022-04-28 20:14 ` [Bug c++/67048] [9/10/11/12/13 " mpolacek at gcc dot gnu.org 2022-04-29 19:08 ` cvs-commit at gcc dot gnu.org 2022-04-29 19:09 ` mpolacek at gcc dot gnu.org [this message] 2022-05-27 9:35 ` [Bug c++/67048] [10/11/12 " rguenth at gcc dot gnu.org 2022-06-28 10:31 ` jakub at gcc dot gnu.org 2022-08-12 8:11 ` cvs-commit at gcc dot gnu.org 2023-03-07 17:42 ` [Bug c++/67048] [10/11 " mpolacek 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-67048-4-gPVH4uhHiq@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).