Hi,
This adds a require-effective-target zvl256b check to pr123626.c.
As the test compiles with _zvl256b and is a run test we need
to check the target actually supports 256b vectors.
This time with proper check... As the CI is not functional, I'll just
go ahead and commit it as obvious.
Regards
Robin
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/base/pr123626.c: Add target check.
---
gcc/testsuite/gcc.target/riscv/rvv/base/pr123626.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/gcc/testsuite/gcc.target/riscv/rvv/base/pr123626.c
b/gcc/testsuite/gcc.target/riscv/rvv/base/pr123626.c
index ddf9b065d91..5d4ab9a1238 100644
--- a/gcc/testsuite/gcc.target/riscv/rvv/base/pr123626.c
+++ b/gcc/testsuite/gcc.target/riscv/rvv/base/pr123626.c
@@ -1,6 +1,8 @@
/* { dg-do run } */
/* { dg-options "-march=rv64gcv_zvl256b -mabi=lp64d -O3 -fsigned-char
-fno-strict-aliasing -fwrapv -std=gnu99" { target rv64 } } */
/* { dg-options "-march=rv32gcv_zvl256b -mabi=ilp32 -O3 -fsigned-char
-fno-strict-aliasing -fwrapv -std=gnu99" { target rv32 } } */
+/* { dg-require-effective-target rvv_zvl256b } */
+
short a;
long long b;
char c[3][3][17];
--
2.52.0
