public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
* [gcc(refs/vendors/riscv/heads/gcc-13-with-riscv-opts)] RISC-V Regression: Fix FAIL of bb-slp-68.c for RVV
@ 2023-10-16 18:38 Jeff Law
0 siblings, 0 replies; only message in thread
From: Jeff Law @ 2023-10-16 18:38 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:4b0f502e0df34b23aef259d320ef220bca1a819a
commit 4b0f502e0df34b23aef259d320ef220bca1a819a
Author: Juzhe-Zhong <juzhe.zhong@rivai.ai>
Date: Fri Oct 13 14:01:26 2023 +0800
RISC-V Regression: Fix FAIL of bb-slp-68.c for RVV
Like comment said, this test failed on 64 bytes vector.
Both RVV and GCN has 64 bytes vector.
So it's more reasonable to use vect512.
gcc/testsuite/ChangeLog:
* gcc.dg/vect/bb-slp-68.c: Use vect512.
(cherry picked from commit 8544efd6d4aea46656c37b0e002503616f09edfc)
Diff:
---
gcc/testsuite/gcc.dg/vect/bb-slp-68.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/testsuite/gcc.dg/vect/bb-slp-68.c b/gcc/testsuite/gcc.dg/vect/bb-slp-68.c
index e7573a14933e..2dd3d8ee90c6 100644
--- a/gcc/testsuite/gcc.dg/vect/bb-slp-68.c
+++ b/gcc/testsuite/gcc.dg/vect/bb-slp-68.c
@@ -20,4 +20,4 @@ void foo ()
/* We want to have the store group split into 4, 2, 4 when using 32byte vectors.
Unfortunately it does not work when 64-byte vectors are available. */
-/* { dg-final { scan-tree-dump-not "from scalars" "slp2" { xfail amdgcn-*-* } } } */
+/* { dg-final { scan-tree-dump-not "from scalars" "slp2" { xfail vect512 } } } */
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2023-10-16 18:38 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-10-16 18:38 [gcc(refs/vendors/riscv/heads/gcc-13-with-riscv-opts)] RISC-V Regression: Fix FAIL of bb-slp-68.c for RVV Jeff Law
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).