OpenE2K
/
gcc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

re PR libfortran/59513 (Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE) 

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

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

From-SVN: r221575
This commit is contained in:
Jerry DeLisle 2015-03-22 21:37:13 +00:00
parent dcbde1f881
commit 34d417be31
2 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gcc/fortran/ChangeLog
View File

@ -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

13
gcc/fortran/gfortran.texi
View File

@ -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