diff options
| author | Jerry DeLisle <jvdelisle@gcc.gnu.org> | 2015-03-22 21:37:13 +0000 |
|---|---|---|
| committer | Jerry DeLisle <jvdelisle@gcc.gnu.org> | 2015-03-22 21:37:13 +0000 |
| commit | 34d417be31db4900811d9294f4f42371d576d340 (patch) | |
| tree | 3d3c013bc3132d23f40197c75753dac8458eb130 | |
| parent | dcbde1f881e5e15f9e3e2efde0680734a74d327e (diff) | |
| download | gcc-34d417be31db4900811d9294f4f42371d576d340.zip gcc-34d417be31db4900811d9294f4f42371d576d340.tar.gz gcc-34d417be31db4900811d9294f4f42371d576d340.tar.bz2 | |
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
| -rw-r--r-- | gcc/fortran/ChangeLog | 5 | ||||
| -rw-r--r-- | gcc/fortran/gfortran.texi | 13 |
2 files changed, 18 insertions, 0 deletions
diff --git a/gcc/fortran/ChangeLog b/gcc/fortran/ChangeLog index 3fc259c..c8c0308 100644 --- 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 c980fe3..9eca6c7 100644 --- 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 |