public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/107164] No pedantic warning for declaration just referring to a previously-declared enum type Date: Wed, 05 Oct 2022 22:05:22 +0000 [thread overview] Message-ID: <bug-107164-4-WQ8E2DLM3w@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107164-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107164 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- clang says it is a GCC extension: <source>:2:6: warning: redeclaration of already-defined enum 'E' is a GNU extension [-Wgnu-redeclared-enum] enum E; ^ <source>:1:6: note: previous definition is here enum E {a,b,c}; ^ GCC does have a forward declaration extension for enum types so it makes sense to allow this as an extension too. That is: ``` enum E; enum E {a,b,c}; ``` (which GCC does have a pedantic diagnostic about).
next prev parent reply other threads:[~2022-10-05 22:05 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-05 21:57 [Bug c/107164] New: " stephenheumann at gmail dot com 2022-10-05 22:05 ` pinskia at gcc dot gnu.org [this message] 2022-10-18 23:26 ` [Bug c/107164] " cvs-commit at gcc dot gnu.org 2022-10-18 23:27 ` 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-107164-4-WQ8E2DLM3w@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).