https://gcc.gnu.org/g:1bb2535c7cb279e6aab731e79080d8486dd50cce

commit r15-1344-g1bb2535c7cb279e6aab731e79080d8486dd50cce
Author: Jakub Jelinek <ja...@redhat.com>
Date:   Fri Jun 14 19:57:59 2024 +0200

    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  <ja...@redhat.com>
    
            * g++.dg/torture/vshuf-mem.C: Add -Wno-psabi to dg-options.

Diff:
---
 gcc/testsuite/g++.dg/torture/vshuf-mem.C | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/g++.dg/torture/vshuf-mem.C 
b/gcc/testsuite/g++.dg/torture/vshuf-mem.C
index 5f1ebf65665c..6d892f876be5 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*-*-* } }

Reply via email to