public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/102844] [9/10/11/12 Regression] gcc-9.x miscompiles unsigned char expression in switch
Date: Tue, 19 Oct 2021 18:11:05 +0000 [thread overview]
Message-ID: <bug-102844-4-bTMTHy37oW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102844-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102844
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Before:
<bb 13> [local count: 25265782]:
<L4>:
nd.7_11 = _46;
_12 = _46 + -128;
_13 = (unsigned char) _12;
dic = _13;
goto <bb 15>; [100.00%]
<bb 14> [local count: 25265782]:
<L5>:
dic = 0;
<bb 15> [local count: 114848370]:
# nd_52 = PHI <nd_6(14), 149(12), nd_6(13), 33(8)>
return nd_52;
<bb 16> [local count: 25270028]:
_46 = (signed char) nd_6;
if (_46 < 0)
goto <bb 13>; [33.33%]
else
goto <bb 14>; [66.67%]
Hmmm:
<bb 16> [local count: 25270028]:
nd_36 = ASSERT_EXPR <nd_47, nd_47 <= 130>;
_46 = (signed char) nd_36;
if (_46 < 0)
goto <bb 21>; [33.33%]
else
goto <bb 20>; [66.67%]
<bb 21> [local count: 8423438]:
_17 = ASSERT_EXPR <_46, _46 < 0>;
nd_39 = ASSERT_EXPR <nd_36, nd_36 + 128 <= 127>;
<bb 13> [local count: 25265782]:
<L4>:
nd.7_11 = _34(D);
_12 = _33(D) + -128;
_13 = (unsigned char) _12;
dic = _13;
goto <bb 15>; [100.00%]
<bb 20> [local count: 16846590]:
nd_45 = ASSERT_EXPR <nd_36, nd_36 + 128 > 127>;
Hmm, no phi node at bb 13 for _46 ....
next prev parent reply other threads:[~2021-10-19 18:11 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 17:45 [Bug c/102844] New: " breiten at lexmark dot com
2021-10-19 17:58 ` [Bug tree-optimization/102844] [9/10/11/12 Regression] " pinskia at gcc dot gnu.org
2021-10-19 18:11 ` pinskia at gcc dot gnu.org [this message]
2021-10-19 18:13 ` pinskia at gcc dot gnu.org
2021-10-19 18:23 ` [Bug tree-optimization/102844] [9/10/11/12 Regression] vrp inserting assert causes miscompiling when doing update_ssa pinskia at gcc dot gnu.org
2021-10-20 7:10 ` rguenth at gcc dot gnu.org
2021-10-20 7:44 ` rguenth at gcc dot gnu.org
2021-10-20 7:49 ` rguenth at gcc dot gnu.org
2021-10-20 8:08 ` marxin at gcc dot gnu.org
2021-10-20 8:28 ` rguenth at gcc dot gnu.org
2021-10-20 8:33 ` marxin at gcc dot gnu.org
2021-10-20 8:59 ` rguenth at gcc dot gnu.org
2021-10-20 9:00 ` rguenth at gcc dot gnu.org
2021-10-20 9:03 ` rguenth at gcc dot gnu.org
2021-10-20 9:08 ` rguenth at gcc dot gnu.org
2021-10-20 9:19 ` rguenth at gcc dot gnu.org
2021-10-20 9:21 ` aldyh at gcc dot gnu.org
2021-10-20 9:30 ` rguenther at suse dot de
2021-10-20 9:47 ` aldyh at gcc dot gnu.org
2021-10-20 9:50 ` rguenth at gcc dot gnu.org
2021-10-20 9:50 ` rguenth at gcc dot gnu.org
2021-10-20 10:56 ` marxin at gcc dot gnu.org
2021-10-20 12:49 ` [Bug tree-optimization/102844] [9/10/11/12 Regression] DOM jump threading not copying block that became non-empty amacleod at redhat dot com
2021-10-20 16:13 ` law at gcc dot gnu.org
2021-10-21 6:02 ` rguenth at gcc dot gnu.org
2022-05-20 8:24 ` [Bug tree-optimization/102844] [9/10/11/12/13 " rguenth at gcc dot gnu.org
2022-05-20 12:01 ` aldyh at gcc dot gnu.org
2022-05-20 15:11 ` law at gcc dot gnu.org
2022-05-20 15:33 ` aldyh at gcc dot gnu.org
2022-05-27 9:46 ` [Bug tree-optimization/102844] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:46 ` jakub at gcc dot gnu.org
2023-01-19 13:26 ` rguenth at gcc dot gnu.org
2023-07-07 10:41 ` [Bug tree-optimization/102844] [11/12/13/14 " rguenth at gcc dot gnu.org
2023-09-19 11:24 ` rguenth at gcc dot gnu.org
2023-09-19 11:25 ` [Bug tree-optimization/102844] [11/12/13 " 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-102844-4-bTMTHy37oW@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).