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/106192] [11/12/13 Regression] ICE in vect_loop_versioning, at tree-vect-loop-manip.cc:3522 Date: Tue, 05 Jul 2022 08:10:55 +0000 [thread overview] Message-ID: <bug-106192-4-vflroMa0Vm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106192-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106192 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org, | |matz at gcc dot gnu.org, | |rguenth at gcc dot gnu.org Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Keywords| |needs-bisection Known to work| |10.3.0 Priority|P3 |P2 Known to fail| |11.3.0, 12.1.0, 13.0 Last reconfirmed| |2022-07-05 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed. LOOP_REQUIRES_VERSIONING_FOR_SIMD_IF_COND is _15 and we have the loop header <bb 4> [local count: 696725737]: # i.2_29 = PHI <1(3), i.2_22(11)> # ivtmp_24 = PHI <100(3), ivtmp_16(11)> .GOMP_SIMD_LANE (simduid.6_17(D), 0, _12); _13 = i.2_29 + -1; _18 = (integer(kind=8)) _13; _19 = a[_18]; _20 = _19 + 1; a[_18] = _20; i.2_22 = i.2_29 + 1; _3 = j.0_28 + 1; _15 = _3 <= 59; .GOMP_SIMD_LANE (simduid.6_17(D), 0, _15); _8 = _19 + 2; a[_18] = _8; ivtmp_16 = ivtmp_24 - 1; if (ivtmp_16 != 0) goto <bb 11>; [87.50%] else goto <bb 12>; [12.50%] so the bb != loop->header part of the assert already fires. The condition is loop invariant but it wasn't hoisted for some reason. Or rather it looks like we unrolled the loop once which we might not do to .GOMP_SIMD_LANE bbs IIRC. unroll-and-jam does this.
next prev parent reply other threads:[~2022-07-05 8:10 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-04 19:43 [Bug fortran/106192] New: " gscfq@t-online.de 2022-07-04 22:31 ` [Bug tree-optimization/106192] " pinskia at gcc dot gnu.org 2022-07-05 8:10 ` rguenth at gcc dot gnu.org [this message] 2022-07-05 12:53 ` matz at gcc dot gnu.org 2022-07-05 12:54 ` matz at gcc dot gnu.org 2022-07-07 12:46 ` [Bug tree-optimization/106192] [11/12/13 Regression] ICE in vect_loop_versioning, at tree-vect-loop-manip.cc:3522 since r11-1650-g1dfa89b0355520ca marxin at gcc dot gnu.org 2023-05-29 10:07 ` [Bug tree-optimization/106192] [11/12/13/14 " jakub 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-106192-4-vflroMa0Vm@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).