aboutsummaryrefslogtreecommitdiff
path: root/gdb/shnbsd-tdep.c
diff options
context:
space:
mode:
authorAndreas Arnez <arnez@linux.vnet.ibm.com>2015-08-24 15:37:40 +0200
committerAndreas Krebbel <krebbel@linux.vnet.ibm.com>2015-08-24 15:37:40 +0200
commit77c365df78441f7b968ec0f62c7ed9f5de36dc60 (patch)
tree8fcef58189c76d18d85756fcac27034c4c4c4a41 /gdb/shnbsd-tdep.c
parentcfe101c6a8227b6b97ed2da85895db7d6083bfa6 (diff)
downloadgdb-77c365df78441f7b968ec0f62c7ed9f5de36dc60.zip
gdb-77c365df78441f7b968ec0f62c7ed9f5de36dc60.tar.gz
gdb-77c365df78441f7b968ec0f62c7ed9f5de36dc60.tar.bz2
gnu_vector.exp: Avoid some more known FAILs
This avoids two more types of FAILs with the gnu_vector test case. First, for POWER targets newer GCCs emit an ABI note when invoked with "-mcpu=native". Then the test case fell back to non-native compile, producing code for a non-vector ABI. But that is not supported by GDB. Thus the compiler note is now suppressed with "-Wno-psabi". Second, on s390 the test case produced FAILs after falling back to a non-vector ABI when using "finish" or "return" in a vector-valued function. This was due to a long-standing known bug (Bug 8549). This case is now detected, and KFAILs are emitted instead. gdb/testsuite/ChangeLog: * gdb.base/gnu_vector.exp: Try compilation with "-mcpu=native -Wno-psabi" if "-mcpu=native" fails. For the tests with "finish" and "return" use KFAIL when GDB can not read/write the vector return value.
Diffstat (limited to 'gdb/shnbsd-tdep.c')
0 files changed, 0 insertions, 0 deletions