[PATCH v2 4/4] testsuite, fortran: make kfail gfortran specific

[Nils-Christian Kempke <nils-christian.kempke@intel.com>]

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).
---
 gdb/testsuite/gdb.fortran/function-calls.exp | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/gdb/testsuite/gdb.fortran/function-calls.exp b/gdb/testsuite/gdb.fortran/function-calls.exp
index bc0192be064..533283b9ef8 100644
--- a/gdb/testsuite/gdb.fortran/function-calls.exp
+++ b/gdb/testsuite/gdb.fortran/function-calls.exp
@@ -102,7 +102,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
-- 
2.25.1

Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva  
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928