public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "luoxhu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/103029] [12 regression] gcc.dg/vect/pr82436.c ICEs on r12-4818
Date: Tue, 02 Nov 2021 03:46:49 +0000 [thread overview]
Message-ID: <bug-103029-4-fuW3PdVSqM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103029-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103029
luoxhu at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |luoxhu at gcc dot gnu.org,
| |rguenther at suse dot de
--- Comment #2 from luoxhu at gcc dot gnu.org ---
Confirmed.
P7's extra option -mno-allow-movmisalign makes this ICE happens. If add this
option on P9 also ICEs. Reason is the phi arguments order changes if switch the
sequence of loopify and lv_adjust_loop_entry_edge.
the constant input argument from bb 18 is in phi index 1 now makes the followed
vectorize code fail to handle?
if (_42 != 0)
goto <bb 18>; [80.00%]
else
goto <bb 19>; [20.00%]
<bb 18> [local count: 67276368]:
<bb 9> [local count: 611603351]:
# i_76 = PHI <i_57(10), 1(18)> // here
# y_lsm.6_74 = PHI <_61(10), 0.0(18)> // here
# w_lsm.7_73 = PHI <_58(10), 0.0(18)> // here
i.0_72 = (unsigned int) i_76;
_70 = (long unsigned int) i.0_72;
_69 = _70 * 80;
x_68 = r_22(D) + _69;
fpred_67 = x_68->f_pred;
fexp_66 = x_68->f_exp;
tem_65 = fpred_67 - fexp_66;
_64 = x_68->f_sigma;
_63 = tem_65 / _64;
_62 = ABS_EXPR <_63>;
_61 = _62 + y_lsm.6_74;
_60 = tem_65 / fexp_66;
_59 = ABS_EXPR <_60>;
_58 = _59 + w_lsm.7_73;
i_57 = i_76 + 1;
if (n_19(D) > i_57)
goto <bb 10>; [89.00%]
else
goto <bb 14>; [11.00%]
<bb 10> [local count: 544326983]:
goto <bb 9>; [100.00%]
It was:
if (_42 != 0)
goto <bb 18>; [80.00%]
else
goto <bb 19>; [20.00%]
<bb 18> [local count: 67276368]:
<bb 9> [local count: 611603351]:
# i_76 = PHI <1(18), i_57(10)>
# y_lsm.6_74 = PHI <0.0(18), _61(10)>
# w_lsm.7_73 = PHI <0.0(18), _58(10)>
i.0_72 = (unsigned int) i_76;
_70 = (long unsigned int) i.0_72;
_69 = _70 * 80;
x_68 = r_22(D) + _69;
fpred_67 = x_68->f_pred;
fexp_66 = x_68->f_exp;
tem_65 = fpred_67 - fexp_66;
_64 = x_68->f_sigma;
_63 = tem_65 / _64;
_62 = ABS_EXPR <_63>;
_61 = _62 + y_lsm.6_74;
_60 = tem_65 / fexp_66;
_59 = ABS_EXPR <_60>;
_58 = _59 + w_lsm.7_73;
i_57 = i_76 + 1;
if (n_19(D) > i_57)
goto <bb 10>; [89.00%]
else
goto <bb 20>; [11.00%]
<bb 10> [local count: 544326983]:
goto <bb 9>; [100.00%]
The comments in function gimple_lv_adjust_loop_header_phi says
/* Browse all 'second' basic block phi nodes and add phi args to
edge 'e' for 'first' head. PHI args are always in correct order. */
Any function to fix the phi order?
next prev parent reply other threads:[~2021-11-02 3:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 18:43 [Bug tree-optimization/103029] New: " seurer at gcc dot gnu.org
2021-11-01 18:46 ` [Bug tree-optimization/103029] " seurer at gcc dot gnu.org
2021-11-02 3:46 ` luoxhu at gcc dot gnu.org [this message]
2021-11-02 6:04 ` luoxhu at gcc dot gnu.org
2021-11-02 7:45 ` rguenth at gcc dot gnu.org
2021-11-02 15:56 ` rguenth at gcc dot gnu.org
2021-11-02 17:49 ` cvs-commit at gcc dot gnu.org
2021-11-02 17:50 ` rguenth at gcc dot gnu.org
2021-11-03 1:22 ` luoxhu 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-103029-4-fuW3PdVSqM@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).