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/103690] [12 Regression] ICE: in build2, at tree.c:4985 with -g -O2 -fno-tree-dce -fno-tree-dse -fno-tree-fre --param=max-jump-thread-duplication-stmts=94
Date: Mon, 13 Dec 2021 23:02:08 +0000 [thread overview]
Message-ID: <bug-103690-4-IN0qetySu8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103690-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103690
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
Last reconfirmed| |2021-12-13
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(gdb) p debug_gimple_stmt(stmt)
_67 = _14 + _66;
Before pre had:
intD.9 * __trans_tmp_1D.2946;
....
# RANGE [1, 9223372036854775807] NONZERO 9223372036854775804
_66 = (long unsigned intD.16) _17;
# PT = nonlocal escaped
# ALIGN = 4, MISALIGN = 0
_67 = __trans_tmp_1_14 + _66;
But after:
# RANGE [1, 9223372036854775807] NONZERO 9223372036854775804
_66 = (long unsigned intD.16) _17;
# PT = nonlocal escaped
# ALIGN = 4, MISALIGN = 0
_67 = _14 + _66;
We already removed the definition of _14 too:
Removing dead stmt __trans_tmp_1_14 = _24 + 4;
So it is the order of the removal which is causing issues.
next prev parent reply other threads:[~2021-12-13 23:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 19:26 [Bug tree-optimization/103690] New: [12 Regression] ICE: in build2, at tree.c:4985 with " zsojka at seznam dot cz
2021-12-13 22:30 ` [Bug tree-optimization/103690] [12 Regression] ICE: in build2, at tree.c:4985 with -g " pinskia at gcc dot gnu.org
2021-12-13 22:51 ` pinskia at gcc dot gnu.org
2021-12-13 23:02 ` pinskia at gcc dot gnu.org [this message]
2021-12-14 10:03 ` [Bug tree-optimization/103690] [12 Regression] ICE: in build2, at tree.c:4985 with -g -O2 -fno-tree-dce -fno-tree-dse -fno-tree-fre --param=max-jump-thread-duplication-stmts=94 since r12-2591-g2e96b5f14e402569 marxin at gcc dot gnu.org
2021-12-15 20:05 ` acoplan at gcc dot gnu.org
2021-12-16 17:17 ` aldyh at gcc dot gnu.org
2022-01-04 10:21 ` rguenth at gcc dot gnu.org
2022-01-04 12:17 ` cvs-commit at gcc dot gnu.org
2022-01-04 12:17 ` 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-103690-4-IN0qetySu8@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).