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 tree-optimization/104655] [12 Regression] array subscript 0 is outside array bounds of Date: Wed, 23 Feb 2022 17:55:59 +0000 [thread overview] Message-ID: <bug-104655-4-4UuDWcOHO7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104655-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104655 Martin Sebor <msebor at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE CC| |msebor at gcc dot gnu.org Status|WAITING |RESOLVED --- Comment #8 from Martin Sebor <msebor at gcc dot gnu.org> --- The warning in the test case in comment #6 is intentional: it triggers because the hardcoded address (0xfee00000) doesn't refer to a known object, same as in the test case in bug 99578 comment 0. The bug is still open because there's a lack of consensus as to whether or how GCC should be enhanced to accept such code without a warning. -Warray-bounds and -Wstringop-overflow/-overread depend on optimizations some of which tend to expose new instances of warnings as optimizers improve from one release to another. *** This bug has been marked as a duplicate of bug 99578 ***
prev parent reply other threads:[~2022-02-23 17:55 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-23 8:12 [Bug tree-optimization/104655] New: " pmenzel+gcc at molgen dot mpg.de 2022-02-23 8:17 ` [Bug tree-optimization/104655] " pinskia at gcc dot gnu.org 2022-02-23 10:39 ` pinskia at gcc dot gnu.org 2022-02-23 10:42 ` rguenth at gcc dot gnu.org 2022-02-23 10:49 ` pmenzel+gcc at molgen dot mpg.de 2022-02-23 10:53 ` jakub at gcc dot gnu.org 2022-02-23 11:14 ` pmenzel+gcc at molgen dot mpg.de 2022-02-23 12:04 ` pinskia at gcc dot gnu.org 2022-02-23 12:10 ` pmenzel+gcc at molgen dot mpg.de 2022-02-23 17:55 ` msebor at gcc dot gnu.org [this message]
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-104655-4-4UuDWcOHO7@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).