[v2,9/9] Move target check into allow_altivec_tests
Commit Message
Pedro pointed out that only PPC can possibly have altivec, so we can
move the target check into allow_altivec_tests.
---
gdb/testsuite/gdb.arch/altivec-abi.exp | 1 -
gdb/testsuite/gdb.arch/altivec-regs.exp | 1 -
gdb/testsuite/gdb.arch/powerpc-vector-regs.exp | 2 +-
gdb/testsuite/lib/gdb.exp | 5 +++++
4 files changed, 6 insertions(+), 3 deletions(-)
@@ -22,7 +22,6 @@
#
require allow_altivec_tests
-require {istarget "powerpc*"}
standard_testfile
@@ -22,7 +22,6 @@
#
require allow_altivec_tests
-require {istarget "powerpc*"}
standard_testfile
@@ -20,7 +20,7 @@
# 0 to 31 in each of the 16 bytes of each corresponding register, and
# we then check if gdb sees these same values.
-require allow_altivec_tests {[istarget "powerpc*"}
+require allow_altivec_tests
standard_testfile
@@ -3471,6 +3471,11 @@ gdb_caching_proc allow_altivec_tests {
return 0
}
+ if {![istarget powerpc*]} {
+ verbose "$me: PPC target required, returning 0" 2
+ return 0
+ }
+
# Make sure we have a compiler that understands altivec.
if [test_compiler_info gcc*] {
set compile_flags "additional_flags=-maltivec"