public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/98503] [11 regression] -Warray-bounds false positive with global variables at -O2 since r11-3306-g3f9a497d1b0dd9da Date: Tue, 05 Jan 2021 17:31:24 +0000 [thread overview] Message-ID: <bug-98503-4-RHJ6flmLZb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98503-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98503 --- Comment #10 from Martin Sebor <msebor at gcc dot gnu.org> --- The main purpose of the "partly outside" warning is to detect reads/writes that cross the trailing array boundary. Those typically come up when a "typeless" buffer (either char array or one allocated by a function like malloc) is used to store a sequence of heterogeneous elements. Besides these bugs the warning also detects other kinds of invalid accesses that span the boundary, like in comment #0. The access there in invalid for a different reason than the usual -Warray-bounds, so issuing a warning that's controlled by a different option would be appropriate (-Wstrict-aliasing seems like a good fit). It's something we have discussed doing but it's not at the top my to do list. Making it conditional on -fstrict-aliasing might be worth considering as well.
next prev parent reply other threads:[~2021-01-05 17:31 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-03 7:53 [Bug c/98503] New: [11 regression] -Warray-bounds false positive with global variables at -O2 w at 1wt dot eu 2021-01-03 7:56 ` [Bug c/98503] " w at 1wt dot eu 2021-01-04 12:33 ` [Bug c/98503] [11 regression] -Warray-bounds false positive with global variables at -O2 since r11-3306-g3f9a497d1b0dd9da marxin at gcc dot gnu.org 2021-01-04 16:06 ` msebor at gcc dot gnu.org 2021-01-04 16:17 ` w at 1wt dot eu 2021-01-04 16:19 ` w at 1wt dot eu 2021-01-04 17:41 ` msebor at gcc dot gnu.org 2021-01-04 22:43 ` w at 1wt dot eu 2021-01-05 11:16 ` rguenth at gcc dot gnu.org 2021-01-05 11:34 ` w at 1wt dot eu 2021-01-05 17:31 ` msebor at gcc dot gnu.org [this message] 2021-01-28 23:06 ` [Bug middle-end/98503] " msebor at gcc dot gnu.org 2021-04-27 11:40 ` [Bug middle-end/98503] [11/12 " jakub at gcc dot gnu.org 2021-05-05 16:52 ` msebor at gcc dot gnu.org 2021-05-05 17:16 ` w at 1wt dot eu 2021-07-28 7:05 ` rguenth at gcc dot gnu.org 2021-11-17 22:34 ` msebor at gcc dot gnu.org 2022-03-08 0:03 ` msebor at gcc dot gnu.org 2022-03-23 8:31 ` rguenth at gcc dot gnu.org 2022-03-23 9:32 ` w at 1wt dot eu
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-98503-4-RHJ6flmLZb@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).