espressif/binutils-gdb
1
0
Fork 0
mirror of https://github.com/espressif/binutils-gdb.git synced 2025-06-26 05:47:26 +08:00
Code Issues Packages Projects Releases Wiki Activity

Move target check into allow_altivec_tests

Browse Source 
Pedro pointed out that only PPC can possibly have altivec, so we can
move the target check into allow_altivec_tests.
This commit is contained in:
Tom Tromey
2023-01-24 12:50:20 -07:00
parent 52c0551e9a
commit d8f5b7d1d1
4 changed files with 6 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
gdb/testsuite/gdb.arch/altivec-abi.exp
View File

@ -22,7 +22,6 @@
#
require allow_altivec_tests
require {istarget "powerpc*"}
standard_testfile

1
gdb/testsuite/gdb.arch/altivec-regs.exp
View File

@ -22,7 +22,6 @@
#
require allow_altivec_tests
require {istarget "powerpc*"}
standard_testfile

2
gdb/testsuite/gdb.arch/powerpc-vector-regs.exp
View File

@ -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

5
gdb/testsuite/lib/gdb.exp
View File

@ -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"