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 target/115373] [15 Regression] RISCV slp-cond-2-big-array.c slp-cond-2.c scan-tree-dump fails since r15-859-geaaa4b88038 Date: Fri, 07 Jun 2024 06:04:46 +0000 [thread overview] Message-ID: <bug-115373-4-Vs41AtvxpB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115373-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115373 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |15.0 CC| |rguenth at gcc dot gnu.org Target| |riscv Keywords| |testsuite-fail --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- This also wasn't seen in precommit CI. I can confirm it on trunk and the issue is that we prefer load-lanes for f3 instead of SLP. This issue will go away when we do load-lanes from SLP, so it's intermittent (but I can't promise any timeline). I wonder if the FAIL also occurs on aarch64. There's vect_load_lanes to eventually "fix" the FAIL by adjusting the testcase expectation.
next prev parent reply other threads:[~2024-06-07 6:04 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-06 18:31 [Bug target/115373] New: " patrick at rivosinc dot com 2024-06-06 18:31 ` [Bug target/115373] " patrick at rivosinc dot com 2024-06-07 6:04 ` rguenth at gcc dot gnu.org [this message] 2024-06-07 6:13 ` rguenth at gcc dot gnu.org 2024-06-27 1:23 ` thiago.bauermann at linaro dot 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-115373-4-Vs41AtvxpB@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).