Hi,
the gimplefe40 and gimplefe41.c tests expect vector capabilities
(vect_float etc.) yet are not in the vect subdirectory. This causes
both to be called unconditionally without prior target-specific vector
setup normally performed by vect/vect.exp.
There is a target-specific option for powerpc
/* { dg-additional-options "-maltivec" { target { powerpc*-*-* &&
powerpc_altivec_ok } } } */
which enables Altivec on supported targets but I'd rather not create
another special case for s390. I suppose the better solution is to move
these tests to the vect subdirectory.
Is this OK?
Regards
Robin
--
gcc/testsuite/ChangeLog:
* gcc.dg/gimplefe-40.c: Moved to...
* gcc.dg/vect/gimplefe-40.c: ...here.
* gcc.dg/gimplefe-41.c: Moved to...
* gcc.dg/vect/gimplefe-41.c: ...here.
commit 1acd4d01c41aeea78ec3c188beb25b245dda4c8b
Author: Robin Dapp <rd...@linux.ibm.com>
Date: Wed Mar 17 09:08:42 2021 +0100
[PATCH] testsuite: Move gimplefe-4[0|1] tests.
The gimplefe-40.c and gimplefe-41.c test cases require vect_* effective
targets even though they reside in gcc.dg. By default e.g.
DEFAULT_VECTCFLAGS which is used to add target-specific machine or build
flags is only applied in the ./vect subdirectory. Move these tests
there.
diff --git a/gcc/testsuite/gcc.dg/gimplefe-40.c b/gcc/testsuite/gcc.dg/vect/gimplefe-40.c
similarity index 100%
rename from gcc/testsuite/gcc.dg/gimplefe-40.c
rename to gcc/testsuite/gcc.dg/vect/gimplefe-40.c
diff --git a/gcc/testsuite/gcc.dg/gimplefe-41.c b/gcc/testsuite/gcc.dg/vect/gimplefe-41.c
similarity index 100%
rename from gcc/testsuite/gcc.dg/gimplefe-41.c
rename to gcc/testsuite/gcc.dg/vect/gimplefe-41.c
