re PR libfortran/59513 (Fortran runtime error: Sequential READ or WRITE not allowed...

2015-03-22 Jerry DeLisle  <jvdelisle@gcc.gnu.org>

	PR libgfortran/59513
	* gfortran.texi (Read/Write after EOF marker): New information.

From-SVN: r221575

diff --git a/gcc/fortran/ChangeLog b/gcc/fortran/ChangeLog
index 3fc259c2cae40cf491a9a00599e6f8991e1ba978..c8c030844fd77a2652b42ec5e8defdd56cdaa7e1 100644 (file)
--- a/gcc/fortran/ChangeLog
+++ b/gcc/fortran/ChangeLog
@@ -1,3 +1,8 @@
+2015-03-22 Jerry DeLisle  <jvdelisle@gcc.gnu.org>
+
+       PR libgfortran/59513
+       * gfortran.texi (Read/Write after EOF marker): New information.
+
 2015-03-21  H.J. Lu  <hongjiu.lu@intel.com>
 
        * gfortran.texi (_gfortran_caf_sync_memory): Put @{xxx} in one

diff --git a/gcc/fortran/gfortran.texi b/gcc/fortran/gfortran.texi
index c980fe3d00890c43859dc919236e4152f73d4152..9eca6c7a75607e96b8fb8c62dfc39584fadacfde 100644 (file)
--- a/gcc/fortran/gfortran.texi
+++ b/gcc/fortran/gfortran.texi
@@ -1404,6 +1404,7 @@ without warning.
 * OpenMP::
 * OpenACC::
 * Argument list functions::
+* Read/Write after EOF marker::
 @end menu
 
 @node Old-style kind specifications
@@ -2049,6 +2050,18 @@ For details refer to the g77 manual
 Also, @code{c_by_val.f} and its partner @code{c_by_val.c} of the
 GNU Fortran testsuite are worth a look.
 
+@node Read/Write after EOF marker
+@subsection Read/Write after EOF marker
+@cindex @code{EOF}
+@cindex @code{BACKSPACE}
+@cindex @code{REWIND}
+
+Some legacy codes rely on allowing @code{READ} or @code{WRITE} after the
+EOF file marker in order to find the end of a file. GNU Fortran normally
+rejects these codes with a run-time error message and suggests the user
+consider @code{BACKSPACE} or @code{REWIND} to properly position
+the file before the EOF marker.  As an extension, the run-time error may
+be disabled using -std=legacy.
 
 @node Extensions not implemented in GNU Fortran
 @section Extensions not implemented in GNU Fortran