public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "daniel.lundin.mail at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/114266] New: No -pedantic diagnostic for zero-sized array in compound literals Date: Thu, 07 Mar 2024 10:50:44 +0000 [thread overview] Message-ID: <bug-114266-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114266 Bug ID: 114266 Summary: No -pedantic diagnostic for zero-sized array in compound literals Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: daniel.lundin.mail at gmail dot com Target Milestone: --- (int[]){}; produces no diagnostics with -std=c23 -pedantic. Empty initalizer lists are OK under -std=c23 and -std=gnu so that's not the problem. gcc correctly gives a diagnostic for that in -std=c17 -pedantic mode. Zero-sized arrays should however give a diagnostic in -std=cxx -pedantic mode. Prior to C23 this was not really a problem as we would get a diagnostic for the empty initializer list. But now this non-conforming C compiles cleanly even with -pedantic set. A diagnostic similar to the one given in clang would be good: warning: zero size arrays are an extension [-Wzero-length-array] As I understand it, gcc did have -Wzero-length-array in the past but removed it? See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94428. The options -Wstrict-flex-arrays -fstrict-flex-arrays seem to have no effect (and my example isn't a flexible array member but a compound literal).
next reply other threads:[~2024-03-07 10:50 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-07 10:50 daniel.lundin.mail at gmail dot com [this message] 2024-03-07 10:52 ` [Bug c/114266] " daniel.lundin.mail at gmail dot com 2024-03-07 16:43 ` jsm28 at gcc dot gnu.org 2024-03-08 7:25 ` daniel.lundin.mail at gmail dot com
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-114266-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).