diff options
| author | Jakub Jelinek <jakub@redhat.com> | 2024-06-14 19:57:59 +0200 |
|---|---|---|
| committer | Jakub Jelinek <jakub@redhat.com> | 2024-06-14 19:57:59 +0200 |
| commit | 1bb2535c7cb279e6aab731e79080d8486dd50cce (patch) | |
| tree | 942e19be1d2f78918ea38145972737da79c0f93f /gcc/tree-dump.h | |
| parent | 2830b0b8655f0d1a62b416af8ade31f5b96f0ffb (diff) | |
| download | gcc-1bb2535c7cb279e6aab731e79080d8486dd50cce.zip gcc-1bb2535c7cb279e6aab731e79080d8486dd50cce.tar.gz gcc-1bb2535c7cb279e6aab731e79080d8486dd50cce.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.
Diffstat (limited to 'gcc/tree-dump.h')
0 files changed, 0 insertions, 0 deletions