gdb/testsuite: don't avoid DWARF assembler tests with Clang
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>
This commit is contained in:
parent
c963bda81e
commit
6911239bba
2 changed files with 0 additions and 11 deletions
|
@ -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}] } {
|
||||
|
|
|
@ -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
|
||||
}
|
||||
|
|
Loading…
Add table
Reference in a new issue