Explain gfortran-dg-runtest usage in libgomp Fortran testing.

	libgomp/
	* testsuite/libgomp.fortran/fortran.exp: Explain
	gfortran-dg-runtest usage.

From-SVN: r212266

diff --git a/libgomp/ChangeLog b/libgomp/ChangeLog
index 6745b3e75e8680039903a6b7304e6cb12e275c18..aaaaca8a00d823140daa53f6daaa07d0f42aaa8c 100644 (file)
--- a/libgomp/ChangeLog
+++ b/libgomp/ChangeLog
@@ -1,3 +1,8 @@
+2014-07-03  Thomas Schwinge  <thomas@codesourcery.com>
+
+       * testsuite/libgomp.fortran/fortran.exp: Explain
+       gfortran-dg-runtest usage.
+
 2014-06-25  Jakub Jelinek  <jakub@redhat.com>
 
        * testsuite/libgomp.fortran/simd5.f90: New test.

diff --git a/libgomp/testsuite/libgomp.fortran/fortran.exp b/libgomp/testsuite/libgomp.fortran/fortran.exp
index e0bffe390b7a6e7ea78c8ff6bdb24a2d5689335d..41e1714ad8b3d00e67c53d5dd53074f42d71432f 100644 (file)
--- 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 ""
 }