public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/94675] [9/10 regression] -Warray-bounds false positive with -O2 since r9-1948 Date: Tue, 21 Apr 2020 19:14:38 +0000 [thread overview] Message-ID: <bug-94675-4-xeokyMr6Fn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94675-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94675 --- Comment #12 from Jeffrey A. Law <law at redhat dot com> --- SO it's not terrible to get the key block cleaned up. but that's not sufficient to resolve this issue. We all missed an important tidbit. VRP is complaining about this: ps.D.2041.s = &MEM <byte> [(void *)&c + 7B]; Note the object we reference in the &MEM expression, "c". "c" is a byte: typedef unsigned char byte; byte c; One could argue the problem is FRE. Prior to fre3 we had: ;; basic block 9, loop depth 0 ;; pred: 7 _34 = ps.D.2041.s; _35 = _34 + 7; ps.D.2041.s = _35; fre3 turns that into: ps.D.2041.s = &MEM <byte> [(void *)&c + 7B]; And we're going to lose. One could also argue that the warning has to be tolerant of these actions from FRE. The question would be how to do that without totally compromising the warning.
next prev parent reply other threads:[~2020-04-21 19:14 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-20 19:42 [Bug tree-optimization/94675] New: [9 regression] -Warray-bounds false positive with -O2 chantry.xavier at gmail dot com 2020-04-20 22:16 ` [Bug tree-optimization/94675] " msebor at gcc dot gnu.org 2020-04-21 6:51 ` chantry.xavier at gmail dot com 2020-04-21 7:04 ` marxin at gcc dot gnu.org 2020-04-21 7:46 ` rguenth at gcc dot gnu.org 2020-04-21 7:58 ` [Bug tree-optimization/94675] [9/10 " rguenth at gcc dot gnu.org 2020-04-21 7:59 ` jakub at gcc dot gnu.org 2020-04-21 8:06 ` [Bug tree-optimization/94675] [9/10 regression] -Warray-bounds false positive with -O2 since r9-1948 jakub at gcc dot gnu.org 2020-04-21 14:03 ` law at redhat dot com 2020-04-21 14:18 ` rguenther at suse dot de 2020-04-21 14:43 ` law at redhat dot com 2020-04-21 14:57 ` rguenther at suse dot de 2020-04-21 14:58 ` msebor at gcc dot gnu.org 2020-04-21 19:14 ` law at redhat dot com [this message] 2020-04-21 19:16 ` law at redhat dot com 2020-04-21 20:10 ` law at redhat dot com 2020-04-21 21:00 ` msebor at gcc dot gnu.org 2020-04-22 6:34 ` rguenther at suse dot de 2020-04-24 7:48 ` chantry.xavier at gmail dot com 2020-04-24 15:16 ` msebor at gcc dot gnu.org 2020-04-30 13:12 ` chantry.xavier at gmail dot com 2021-06-01 8:17 ` [Bug tree-optimization/94675] [9/10/11/12 " rguenth at gcc dot gnu.org 2021-09-06 11:25 ` pinskia at gcc dot gnu.org 2022-03-16 11:09 ` chantry.xavier at gmail dot com 2022-03-16 13:24 ` rguenth at gcc dot gnu.org 2022-05-27 9:42 ` [Bug tree-optimization/94675] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:40 ` jakub at gcc dot gnu.org 2023-05-14 21:25 ` [Bug tree-optimization/94675] [10/11/12/13/14 " pinskia at gcc dot gnu.org 2023-07-07 10:37 ` [Bug tree-optimization/94675] [11/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-94675-4-xeokyMr6Fn@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).