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)
commit6911239bbaa7b4365d3d0ff7b6cb296cfe43480c
treefa725903db20973fc68d429315318f2052d6c83f
parentc963bda81e255dbac7c1acd31121d282a4910308
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>
gdb/testsuite/gdb.base/until-trailing-insns.exp
gdb/testsuite/gdb.cp/incomplete-type-overload.exp