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 testsuite/100073] [11 regression] test case gcc.dg/pr86058.c fails after r11-8161
Date: Wed, 14 Apr 2021 16:15:21 +0000 [thread overview]
Message-ID: <bug-100073-4-Kks3iAeFWZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100073-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100073
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2021-04-14
Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot gnu.org
Status|UNCONFIRMED |ASSIGNED
Ever confirmed|0 |1
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
Looks like powerpc64 doesn't warn for the code, and apparently neither does
aarch64 with -mabi=ilp32, due to what seems like a limitation in the uninit
pass which sees this IL:
<bb 3> [local count: 105119324]:
doloop.6_16 = (unsigned int) indx_9(D);
ivtmp.9_22 = (unsigned long) &MEM <int[10]> [(void *)&arr + -4B]; <<<
&arr[-1]
_27 = out_11(D) + 18446744073709551612;
ivtmp.11_26 = (unsigned long) _27;
<bb 4> [local count: 955630225]:
# doloop.6_20 = PHI <doloop.6_17(6), doloop.6_16(3)>
# ivtmp.9_7 = PHI <ivtmp.9_6(6), ivtmp.9_22(3)> <<< ivtmp.9_22(3)
points to arr[-1]
# ivtmp.11_24 = PHI <ivtmp.11_25(6), ivtmp.11_26(3)>
ivtmp.9_6 = ivtmp.9_7 + 4; <<< &arr[0]
_28 = (void *) ivtmp.9_6;
_1 = MEM[(int *)_28]; <<< uninitialized
read, no warning
next prev parent reply other threads:[~2021-04-14 16:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 23:49 [Bug testsuite/100073] New: [11 regression] test case gcc.dg/pr86058.c fails after r11- seurer at gcc dot gnu.org
2021-04-14 6:54 ` [Bug testsuite/100073] [11 regression] test case gcc.dg/pr86058.c fails after r11-8161 rguenth at gcc dot gnu.org
2021-04-14 16:15 ` msebor at gcc dot gnu.org [this message]
2021-04-14 16:45 ` cvs-commit at gcc dot gnu.org
2021-04-14 16:48 ` [Bug tree-optimization/100073] missing warning on an uninitialized array read in a loop msebor at gcc dot gnu.org
2021-04-14 16:50 ` msebor at gcc dot gnu.org
2021-04-15 12:09 ` cvs-commit at gcc dot gnu.org
2021-04-27 11:40 ` jakub at gcc dot gnu.org
2021-07-28 7:06 ` rguenth at gcc dot gnu.org
2022-04-21 7:49 ` rguenth at gcc dot gnu.org
2023-05-29 10:04 ` jakub 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-100073-4-Kks3iAeFWZ@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: link
Be 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).