testsuite, fortran: make kfail gfortran specific
authorNils-Christian Kempke <nils-christian.kempke@intel.com>
Tue, 31 May 2022 16:10:18 +0000 (18:10 +0200)
committerIjaz, Abdul B <abdul.b.ijaz@intel.com>
Thu, 7 Sep 2023 22:35:18 +0000 (00:35 +0200)
The modified test in function-calls.exp actually passes with ifort and
ifx.  The particular fail seems to be specific to gfortran.  When the
test was introduced it was only tested with gfortran (actually the
whole patch was written with gfortran and the GNU Fortran argument
passing convention in mind).

Approved-by: Tom Tromey <tom@tromey.com>
gdb/testsuite/gdb.fortran/function-calls.exp

index f9a1efc241f3db5f9cddfe38e614fff03906e6d6..646fbb06435188d5175bc98057d663cf2076b776 100644 (file)
@@ -101,7 +101,9 @@ gdb_test "p sum_some(1,2)" " = 3"
 
 # Paragraph 10: optional value arguments. There is insufficient DWARF
 # information to reliably make this case work.
-setup_kfail "gdb/24305" *-*-*
+if { [test_compiler_info {gfortran-*} f90] } {
+    setup_kfail "gdb/24305" *-*-*
+}
 gdb_test "p one_arg_value(10)" " = 10"
 
 # DW_AT_artificial formal parameters must be passed manually. This