public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason.vas.dias at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/109316] New: incorrect "warning: declaration does not declare anything" for anonymous enums in structs, for -std=(gnu|c)-17 Date: Tue, 28 Mar 2023 13:30:01 +0000 [thread overview] Message-ID: <bug-109316-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109316 Bug ID: 109316 Summary: incorrect "warning: declaration does not declare anything" for anonymous enums in structs, for -std=(gnu|c)-17 Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: jason.vas.dias at gmail dot com Target Milestone: --- Just a niggle: I don't think this code should produce a warning, but under GCC 12, with -std=gnu17 or -std=c17, or without any '-std=' setting in C language mode, it does: 'struct S { int a; enum { S_O_a = 0 }; }'; /tmp/b.c:1:37: warning: declaration does not declare anything 1 | struct S { int a; enum { S_O_a = 0 }; }; | Yes, I know the enumeration declaration does not add anything to the struct declaration, (intentionally!), but in fact GCC HAS inserted DWARF debuginfo for the enumerator 'S_O_a' in the debug_info section , which can be used by code in which case the constant is interpolated into the output machine code, so something HAS been declared here ...
reply other threads:[~2023-03-28 13:30 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-109316-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).