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/115652] [15 Regression] GCN: FAIL: gcc.dg/vect/pr70138-{1,2}.c (internal compiler error: verify_ssa failed) Date: Wed, 26 Jun 2024 17:25:39 +0000 [thread overview] Message-ID: <bug-115652-4-ffmy3PRmtD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115652-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115652 --- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> --- (In reply to Jeffrey A. Law from comment #4) > That patch seems to be causing ssa verification failures (should be visible > with riscv64-elf cross): > > make check-gcc RUNTESTFLAGS=rvv.exp=vsetvl_bug-2.c > > Running > /home/jlaw/jenkins/workspace/riscv64-elf/gcc/gcc/testsuite/gcc.target/riscv/ > rvv/rvv.exp ... > FAIL: gcc.target/riscv/rvv/vsetvl/vsetvl_bug-2.c -O0 (internal compiler > error: verify_ssa failed) > FAIL: gcc.target/riscv/rvv/vsetvl/vsetvl_bug-2.c -O0 (test for excess > errors) > FAIL: gcc.target/riscv/rvv/vsetvl/vsetvl_bug-2.c -O1 (internal compiler > error: verify_ssa failed) > FAIL: gcc.target/riscv/rvv/vsetvl/vsetvl_bug-2.c -O1 (test for excess > errors) > FAIL: gcc.target/riscv/rvv/vsetvl/vsetvl_bug-2.c -O2 (internal compiler > error: verify_ssa failed) > FAIL: gcc.target/riscv/rvv/vsetvl/vsetvl_bug-2.c -O2 (test for excess > errors) > FAIL: gcc.target/riscv/rvv/vsetvl/vsetvl_bug-2.c -O3 -fomit-frame-pointer > -funroll-loops -fpeel-loops -ftracer -finline-functions (internal compiler > error: verify_ssa failed) > FAIL: gcc.target/riscv/rvv/vsetvl/vsetvl_bug-2.c -O3 -fomit-frame-pointer > -funroll-loops -fpeel-loops -ftracer -finline-functions (test for excess > errors) > FAIL: gcc.target/riscv/rvv/vsetvl/vsetvl_bug-2.c -O3 -g (internal > compiler error: verify_ssa failed) > FAIL: gcc.target/riscv/rvv/vsetvl/vsetvl_bug-2.c -O3 -g (test for excess > errors) > FAIL: gcc.target/riscv/rvv/vsetvl/vsetvl_bug-2.c -Os (internal compiler > error: verify_ssa failed) > FAIL: gcc.target/riscv/rvv/vsetvl/vsetvl_bug-2.c -Os (test for excess > errors) > > There's a handful of other failures since yesterday, but I suspect they're > all the same root cause. I can reproduce the above, we get vect__85.21_1 = .COND_LEN_XOR ({ -1, ... }, vect_l_437__lsm.13_110.20_2, vect__87.19_22, vect_l_437__lsm.13_110.20_2, loop_len_54, 0); vect__87.19_22 = (vector([32,32]) int) vect__90.18_9; I'm testing a fix: diff --git a/gcc/tree-vect-slp.cc b/gcc/tree-vect-slp.cc index 896ea6dc14c..ce214dd652e 100644 --- a/gcc/tree-vect-slp.cc +++ b/gcc/tree-vect-slp.cc @@ -9752,7 +9752,8 @@ vect_schedule_slp_node (vec_info *vinfo, { gimple_stmt_iterator si2 = gsi_after_labels (LOOP_VINFO_LOOP (loop_vinfo)->header); - if (vect_stmt_dominates_stmt_p (last_stmt, *si2)) + if (last_stmt != *si2 + && vect_stmt_dominates_stmt_p (last_stmt, *si2)) si = si2; } }
next prev parent reply other threads:[~2024-06-26 17:25 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-25 20:28 [Bug target/115652] New: " tschwinge at gcc dot gnu.org 2024-06-25 22:00 ` [Bug tree-optimization/115652] " pinskia at gcc dot gnu.org 2024-06-26 7:05 ` rguenth at gcc dot gnu.org 2024-06-26 12:05 ` cvs-commit at gcc dot gnu.org 2024-06-26 12:06 ` rguenth at gcc dot gnu.org 2024-06-26 15:59 ` law at gcc dot gnu.org 2024-06-26 17:25 ` rguenth at gcc dot gnu.org [this message] 2024-06-27 5:53 ` cvs-commit at gcc dot gnu.org 2024-06-27 5:54 ` rguenth at gcc dot gnu.org 2024-06-28 8:06 ` tschwinge at gcc dot gnu.org 2024-06-28 12:50 ` cvs-commit at gcc dot gnu.org 2024-06-28 12:50 ` 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-115652-4-ffmy3PRmtD@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).