]> git.ipfire.org Git - thirdparty/binutils-gdb.git/commitdiff
gdb/testsuite: don't avoid DWARF assembler tests with Clang
authorAndrew Burgess <aburgess@redhat.com>
Fri, 11 Nov 2022 15:21:56 +0000 (15:21 +0000)
committerAndrew Burgess <aburgess@redhat.com>
Fri, 18 Nov 2022 11:21:36 +0000 (11:21 +0000)
Two tests make the claim that the DWARF assembler requires gcc,
however, this isn't true.  I think at one point, when the DWARF
assembler was first added, we did use some techniques that were not
portable (see the comments in lib/dwarf.exp on function_range for
details), however, I think most DWARF assembler tests will now work
fine with Clang.

The two tests that I modify in this commit both work fine with Clang,
at least, I've tested with Clang 9.0.1 and 15.0.2, and don't see any
problems, so I'm removing the early return logic that stops these
tests from running with Clang.

Reviewed-By: Lancelot SIX <lancelot.six@amd.com>
gdb/testsuite/gdb.base/until-trailing-insns.exp
gdb/testsuite/gdb.cp/incomplete-type-overload.exp

index 6396b6650c1ce0a413f38b2f922051ef173a3ab7..56f6cf038e2f29214a2cf5a98299bb01d4a55e8c 100644 (file)
@@ -84,12 +84,6 @@ if {![dwarf2_support]} {
     return 0
 }
 
-# The DWARF assembler requires the gcc compiler.
-if {![is_c_compiler_gcc]} {
-    unsupported "gcc is required for this test"
-    return 0
-}
-
 standard_testfile .c .S
 
 if { [prepare_for_testing "failed to prepare" ${testfile} ${srcfile}] } {
index 96ed25dd5d14bb75659bced87be6bef4795dae32..024014d68ba6cbfad0db55cbce13abc96c9d62bd 100644 (file)
@@ -31,11 +31,6 @@ if [prepare_for_testing "failed to prepare" $testfile $srcfile {debug c++}] {
     return
 }
 
-if {[test_compiler_info clang-*-*]} {
-    untested "gcc is required for dwarf assembler tests"
-    return
-}
-
 if ![runto_main] {
     return
 }