public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/109233] [12/13 Regression] warning: array subscript 5 is above array bounds of ‘struct tg3_napi[5]’ since r12-2591 Date: Wed, 22 Mar 2023 14:13:51 +0000 [thread overview] Message-ID: <bug-109233-4-SIpMxRawuG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109233-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109233 --- Comment #7 from Martin Liška <marxin at gcc dot gnu.org> --- Note, the linux kernel disables the -Werror of the warning for GCC 11 and 12: https://github.com/torvalds/linux/blob/a1effab7a3a35a837dd9d2b974a1bc4939df1ad5/init/Kconfig#L893-L904 while they still hope it can be enabled for GCC 13.
next prev parent reply other threads:[~2023-03-22 14:13 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-21 13:58 [Bug c/109233] New: warning: array subscript 5 is above array bounds of ‘struct tg3_napi[5]’ ubizjak at gmail dot com 2023-03-21 14:01 ` [Bug c/109233] " ubizjak at gmail dot com 2023-03-21 14:05 ` ubizjak at gmail dot com 2023-03-22 10:27 ` ubizjak at gmail dot com 2023-03-22 10:38 ` [Bug c/109233] warning: array subscript 5 is above array bounds of ‘struct tg3_napi[5]’ since r12-2591 jakub at gcc dot gnu.org 2023-03-22 10:40 ` [Bug c/109233] [12/13 Regression] " jakub at gcc dot gnu.org 2023-03-22 10:43 ` ubizjak at gmail dot com 2023-03-22 12:10 ` ubizjak at gmail dot com 2023-03-22 14:13 ` marxin at gcc dot gnu.org [this message] 2023-03-22 14:37 ` jakub at gcc dot gnu.org 2023-03-22 14:39 ` jakub at gcc dot gnu.org 2023-03-22 15:02 ` aldyh at gcc dot gnu.org 2023-03-22 17:16 ` amacleod at redhat dot com 2023-03-23 10:00 ` rguenth at gcc dot gnu.org 2023-03-27 6:13 ` ubizjak at gmail dot com 2023-05-08 12:26 ` [Bug c/109233] [12/13/14 " rguenth 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-109233-4-SIpMxRawuG@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).