public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/99880] [10/11 Regression] ICE in maybe_set_vectorized_backedge_value, at tree-vect-loop.c:9161 since r10-3711-g69f8c1aef5cdcc54 Date: Tue, 06 Apr 2021 11:11:42 +0000 [thread overview] Message-ID: <bug-99880-4-5Ipr1Q6YKc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99880-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99880 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- So we're having a PHI latch value vectorized because it's used by the outer loop (vect_used_in_outer_by_reduction), but the vect_nested_cycle def PHI in the inner loop isn't relevant since it's vect_unused_in_scope: <bb 5> [local count: 11811160]: # g_36 = PHI <g_21(11), -8(15)> # c_lsm.16_20 = PHI <_12(11), c_lsm.16_29(15)> # ivtmp_18 = PHI <ivtmp_1(11), 1717986920(15)> g_21 = g_36 + 5; vect_cst__28 = { 0, 0, 0, 0 }; <bb 6> [local count: 118111600]: # h_14 = PHI <10(5), h_24(12)> # c_lsm.16_22 = PHI <c_lsm.16_20(5), _10(12)> # ivtmp_30 = PHI <10(5), ivtmp_31(12)> h_24 = h_14 + -1; _7 = d.6_6 <= c_lsm.16_22; _8 = (int) _7; vect__10.19_33 = vect_cst__28; _10 = 0; ivtmp_31 = ivtmp_30 - 1; if (ivtmp_31 != 0) goto <bb 12>; [90.00%] else goto <bb 9>; [10.00%] <bb 12> [local count: 106300440]: goto <bb 6>; [100.00%] <bb 9> [local count: 11811160]: # _27 = PHI <_10(6)> _12 = _27 - e.10_11; it's the c_lsm.16_22 PHI and the _10 backedge def (note how we failed to constant propagate the 10 ...). The fix is simple and hopefully it doesn't break other stuff.
next prev parent reply other threads:[~2021-04-06 11:11 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-02 2:47 [Bug c/99880] New: ICE in maybe_set_vectorized_backedge_value, at tree-vect-loop.c:9161 haoxintu at gmail dot com 2021-04-02 11:13 ` [Bug tree-optimization/99880] [10/11 Regression] ICE in maybe_set_vectorized_backedge_value, at tree-vect-loop.c:9161 since r10-3711-g69f8c1aef5cdcc54 marxin at gcc dot gnu.org 2021-04-06 7:42 ` rguenth at gcc dot gnu.org 2021-04-06 11:11 ` rguenth at gcc dot gnu.org [this message] 2021-04-06 12:20 ` cvs-commit at gcc dot gnu.org 2021-04-06 12:21 ` [Bug tree-optimization/99880] [10 " rguenth at gcc dot gnu.org 2021-04-08 12:02 ` rguenth at gcc dot gnu.org 2021-04-26 11:46 ` cvs-commit at gcc dot gnu.org 2021-04-26 11:46 ` 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-99880-4-5Ipr1Q6YKc@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: linkBe 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).