]> git.ipfire.org Git - thirdparty/binutils-gdb.git/commitdiff
gdb/testsuite: extend XFAIL to gdb.fortran/entry-point.exp to clang too
authorGuinevere Larsen <blarsen@redhat.com>
Tue, 30 Jul 2024 17:36:45 +0000 (14:36 -0300)
committerGuinevere Larsen <blarsen@redhat.com>
Fri, 2 Aug 2024 12:06:26 +0000 (09:06 -0300)
The test gdb.fortran/entry-point.exp already has an XFAIL when trying to
set a breakpoint in mod::mod_foo because gcc puts that subprogram in the
wrong scope in the debug information. Clang's debug information looks
the same as gcc's, so the test to setup the xfail has been extended to
also include clang.

Approved-By: Andrew Burgess <aburgess@redhat.com>
gdb/testsuite/gdb.fortran/entry-point.exp

index 4e4706dd1baffb86eb1107ce403cf0204665a967..51550adcfb26bcfec8e6b9d281c0c0700e94e60f 100644 (file)
@@ -72,12 +72,12 @@ set entry_point_name "mod::mod_foo"
 
 # GCC moves subroutines with entry points out of the module scope into the
 # compile unit scope.
-if {[test_compiler_info {gcc-*}]} {
+if {[test_compiler_info {gcc-*}] || [test_compiler_info {clang-*}]} {
     setup_xfail "gcc/105272" "*-*-*"
 }
 gdb_breakpoint $entry_point_name
 
-if {[test_compiler_info {gcc-*}]} {
+if {[test_compiler_info {gcc-*}] || [test_compiler_info {clang-*}]} {
     setup_xfail "gcc/105272" "*-*-*"
 }
 gdb_continue_to_breakpoint "continue to breakpoint: $entry_point_name" \