public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/108986] [11/12/13 Regression] Incorrect warning for [static] array parameter Date: Thu, 02 Mar 2023 15:42:23 +0000 [thread overview] Message-ID: <bug-108986-4-EknZJWAeeL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108986-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108986 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 |P2 Target Milestone|--- |12.3 Summary|Incorrect warning for |[11/12/13 Regression] |[static] array parameter |Incorrect warning for | |[static] array parameter CC| |jakub at gcc dot gnu.org --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- One warning with the bogus [static 28] appeared with -O2 -Wall in r12-6606-g9d6a0f388eb048f8d87f With -O0 -Wall we started warning once with correct [static 7] in r11-3305-gbaad4c48a85a354d2bf1 and the bogus [static 28] first appeared in r11-3540-g873f8c1e6df94a9dcbfbe69 and two warnings starting with r12-6606.
next prev parent reply other threads:[~2023-03-02 15:42 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-01 18:35 [Bug c/108986] New: " Keith.S.Thompson at gmail dot com 2023-03-01 18:41 ` [Bug c/108986] " Keith.S.Thompson at gmail dot com 2023-03-02 10:11 ` rguenth at gcc dot gnu.org 2023-03-02 15:42 ` jakub at gcc dot gnu.org [this message] 2023-03-02 18:09 ` [Bug c/108986] [11/12/13 Regression] " jakub at gcc dot gnu.org 2023-03-03 15:12 ` cvs-commit at gcc dot gnu.org 2023-03-03 15:19 ` [Bug c/108986] [11/12 " jakub at gcc dot gnu.org 2023-03-19 5:30 ` cvs-commit at gcc dot gnu.org 2023-03-20 10:28 ` [Bug c/108986] [11 " jakub at gcc dot gnu.org 2023-05-08 12:26 ` rguenth at gcc dot gnu.org 2023-08-04 14:06 ` muecker at gwdg dot de
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-108986-4-EknZJWAeeL@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).