https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117721
--- Comment #3 from Peter Bergner <bergner at gcc dot gnu.org> ---
(In reply to Michael Meissner from comment #0)
> gcc.dg/vect/pr112325.c
This is compiling some explict vector code, so I wouldn't expect this to run on
power4, but it does. I would have thought the dg-require-effective-target
vect_int and vect_shift would have disabled it on non-vector enabled ppc
targets, but the target tests allow all powerpc*-*-* targets. I think we want
something like the following:
--- a/gcc/testsuite/lib/target-supports.exp
+++ b/gcc/testsuite/lib/target-supports.exp
@@ -4279,7 +4279,8 @@ proc check_effective_target_vect_int { } {
return [check_cached_effective_target_indexed vect_int {
expr {
[istarget i?86-*-*] || [istarget x86_64-*-*]
- || [istarget powerpc*-*-*]
+ || ([istarget powerpc*-*-*]
+ && [check_effective_target_powerpc_altivec])
|| [istarget amdgcn-*-*]
|| [istarget sparc*-*-*]
|| [istarget alpha*-*-*]
@@ -7678,7 +7679,8 @@ proc check_effective_target_sparc_vis { } {
proc check_effective_target_vect_shift { } {
return [check_cached_effective_target_indexed vect_shift {
- expr {[istarget powerpc*-*-*]
+ expr {([istarget powerpc*-*-*]
+ && [check_effective_target_powerpc_altivec])
|| [istarget ia64-*-*]
|| [istarget i?86-*-*] || [istarget x86_64-*-*]
|| [istarget aarch64*-*-*]
There look to be more effective target tests we need a similar fix for.
