public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/100994] [12 Regression] wrong code with "-O1 -finline-small-functions -fipa-cp"
Date: Wed, 09 Jun 2021 18:31:05 +0000 [thread overview]
Message-ID: <bug-100994-4-q68msrOrfr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100994-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100994
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The difference after IPA between r12-433 and r12-434 is:
--- pr100994.c.092t.fixup_cfg3_ 2021-06-09 14:26:08.000000000 -0400
+++ pr100994.c.092t.fixup_cfg3 2021-06-09 14:26:28.000000000 -0400
@@ -3,7 +3,6 @@
int main ()
{
- const struct a l;
const <unnamed-unsigned:9> l$c;
int g.0_4;
int f.3_5;
@@ -14,8 +13,7 @@ int main ()
int e.5_10;
<bb 2> [local count: 1073741824]:
- l = d;
- l$c_3 = l.c;
+ l$c_3 = 0;
<bb 3> [local count: 9761289362]:
g.0_4 = g;
@@ -37,8 +35,8 @@ int main ()
goto <bb 6>; [50.00%]
<bb 6> [local count: 4343773769]:
- l.c = l$c_3;
- _6 = BIT_FIELD_REF <l, 8, 0>;
+ d.c = l$c_3;
+ _6 = 0;
_7 = _6 & 15;
if (_7 != 0)
goto <bb 8>; [50.00%]
Note, d is a TREE_STATIC const variable where both members are 0,
so I guess l$c_3 = 0; is ok, but the l.c = l$c_3 to d.c = l$c_3; change is not,
that is what segfaults there.
next prev parent reply other threads:[~2021-06-09 18:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 14:29 [Bug ipa/100994] New: " suochenyao at 163 dot com
2021-06-09 18:24 ` [Bug ipa/100994] [12 Regression] " jakub at gcc dot gnu.org
2021-06-09 18:31 ` jakub at gcc dot gnu.org [this message]
2021-06-09 18:39 ` jakub at gcc dot gnu.org
2021-06-09 19:02 ` jakub at gcc dot gnu.org
2021-06-09 19:07 ` jakub at gcc dot gnu.org
2021-06-09 19:41 ` msebor at gcc dot gnu.org
2021-06-09 21:28 ` ebotcazou at gcc dot gnu.org
2021-06-09 21:30 ` ebotcazou at gcc dot gnu.org
2021-06-09 21:32 ` pinskia 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-100994-4-q68msrOrfr@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).