From c6a0e02d08b8a30c76bc3f2fea7e772714f748e6 Mon Sep 17 00:00:00 2001 From: Guinevere Larsen Date: Tue, 30 Jul 2024 14:36:45 -0300 Subject: gdb/testsuite: extend XFAIL to gdb.fortran/entry-point.exp to clang too 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 --- gdb/testsuite/gdb.fortran/entry-point.exp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gdb/testsuite/gdb.fortran/entry-point.exp b/gdb/testsuite/gdb.fortran/entry-point.exp index 4e4706d..51550ad 100644 --- a/gdb/testsuite/gdb.fortran/entry-point.exp +++ b/gdb/testsuite/gdb.fortran/entry-point.exp @@ -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" \ -- cgit v1.1