diff options
| author | Jakub Jelinek <jakub@redhat.com> | 2024-06-14 19:57:59 +0200 |
|---|---|---|
| committer | Jakub Jelinek <jakub@redhat.com> | 2024-06-20 13:04:56 +0200 |
| commit | b4e4997b1f2e21598947f8339db5eb7cc0230476 (patch) | |
| tree | 27fc3ceea62880b14d409a6369a0d094a4f0b0cd | |
| parent | 166c9f99a2376b2255021de52a563e1268584c12 (diff) | |
| download | gcc-b4e4997b1f2e21598947f8339db5eb7cc0230476.zip gcc-b4e4997b1f2e21598947f8339db5eb7cc0230476.tar.gz gcc-b4e4997b1f2e21598947f8339db5eb7cc0230476.tar.bz2 | |
testsuite: Add -Wno-psabi to vshuf-mem.C test
The newly added test FAILs on i686-linux.
On x86_64-linux
make check-g++ RUNTESTFLAGS='--target_board=unix\{-m64,-m32/-msse2,-m32/-mno-sse/-mno-mmx\} dg-torture.exp=vshuf-mem.C'
shows that as well.
The problem is that without SSE2/MMX the vector is passed differently
than normally and so GCC warns about that.
-Wno-psabi is the usual way to shut it up.
Also wonder about the
// { dg-additional-options "-march=z14" { target s390*-*-* } }
line, doesn't that mean the test will FAIL on all pre-z14 HW?
Shouldn't it use some z14_runtime or similar effective target, or
check in main (in that case copied over to g++.target/s390) whether
z14 instructions can be actually used at runtime?
2024-06-14 Jakub Jelinek <jakub@redhat.com>
* g++.dg/torture/vshuf-mem.C: Add -Wno-psabi to dg-options.
(cherry picked from commit 1bb2535c7cb279e6aab731e79080d8486dd50cce)
| -rw-r--r-- | gcc/testsuite/g++.dg/torture/vshuf-mem.C | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gcc/testsuite/g++.dg/torture/vshuf-mem.C b/gcc/testsuite/g++.dg/torture/vshuf-mem.C index 5f1ebf6..6d892f8 100644 --- a/gcc/testsuite/g++.dg/torture/vshuf-mem.C +++ b/gcc/testsuite/g++.dg/torture/vshuf-mem.C @@ -1,4 +1,4 @@ -// { dg-options "-std=c++11" } +// { dg-options "-std=c++11 -Wno-psabi" } // { dg-do run } // { dg-additional-options "-march=z14" { target s390*-*-* } } |