From 07b6c044833e9ae2a723400435b32612bd9cee2a Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Thu, 3 Jul 2014 17:23:43 +0200 Subject: [PATCH] Explain gfortran-dg-runtest usage in libgomp Fortran testing. libgomp/ * testsuite/libgomp.fortran/fortran.exp: Explain gfortran-dg-runtest usage. From-SVN: r212266 --- libgomp/ChangeLog | 5 +++++ libgomp/testsuite/libgomp.fortran/fortran.exp | 4 +++- 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/libgomp/ChangeLog b/libgomp/ChangeLog index 6745b3e75e8..aaaaca8a00d 100644 --- a/libgomp/ChangeLog +++ b/libgomp/ChangeLog @@ -1,3 +1,8 @@ +2014-07-03 Thomas Schwinge + + * testsuite/libgomp.fortran/fortran.exp: Explain + gfortran-dg-runtest usage. + 2014-06-25 Jakub Jelinek * testsuite/libgomp.fortran/simd5.f90: New test. diff --git a/libgomp/testsuite/libgomp.fortran/fortran.exp b/libgomp/testsuite/libgomp.fortran/fortran.exp index e0bffe390b7..41e1714ad8b 100644 --- a/libgomp/testsuite/libgomp.fortran/fortran.exp +++ b/libgomp/testsuite/libgomp.fortran/fortran.exp @@ -59,7 +59,9 @@ if { $lang_test_file_found } { append ld_library_path [gcc-set-multilib-library-path $GCC_UNDER_TEST] set_ld_library_path_env_vars - # Main loop. + # For Fortran we're doing torture testing, as Fortran has far more tests + # with arrays etc. that testing just -O0 or -O2 is insufficient, that is + # typically not the case for C/C++. gfortran-dg-runtest $tests "" }