public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "P at draigBrady dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/111526] New: inconsistent handling of declaration after label Date: Thu, 21 Sep 2023 18:02:35 +0000 [thread overview] Message-ID: <bug-111526-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111526 Bug ID: 111526 Summary: inconsistent handling of declaration after label Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: P at draigBrady dot com Target Milestone: --- Created attachment 55963 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55963&action=edit coreutils fix for non gcc >= 11 Ever since https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=8b7a9a24 declarations after labels are allowed by default, and only disabled with -pedantic etc. I.e. the following simple code compiles on gcc >= 11, but will fail when tried to be compiled with gcc <= 10, or clang for e.g. This is exacerbated by the fact there is no compiler option to avoid the issue on gcc <= 10 or clang, as that code is explicitly disallowed by C11 and earlier. int f(int x) { switch (x) { case 1: int i=f(x); } return 0; } There is also a more subtle related issue (which I haven't fully reduced but can easily reproduce), where the warning will NOT fire even with -Wpedantic on gcc 13 at least. If one compiles GNU coreutils with the attached commit reverted, and with -Wpedantic on newer gcc, it will _NOT_ issue a warning.
next reply other threads:[~2023-09-21 18:02 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-21 18:02 P at draigBrady dot com [this message] 2023-09-21 18:10 ` [Bug c/111526] " pinskia at gcc dot gnu.org 2023-09-21 18:13 ` pinskia at gcc dot gnu.org 2023-09-21 18:26 ` P at draigBrady dot com 2023-09-21 18:28 ` P at draigBrady dot com 2023-09-21 18:43 ` pinskia at gcc dot gnu.org 2023-09-21 18:43 ` pinskia at gcc dot gnu.org 2023-09-21 18:45 ` pinskia 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-111526-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).