* [Bug libfortran/59513] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
@ 2013-12-15 22:19 ` jvdelisle at gcc dot gnu.org
2013-12-15 22:33 ` aruopp at gmx dot de
` (31 subsequent siblings)
32 siblings, 0 replies; 33+ messages in thread
From: jvdelisle at gcc dot gnu.org @ 2013-12-15 22:19 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jvdelisle at gcc dot gnu.org
--- Comment #1 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
This depends a lot on what is in the file polarfile_1.dat.
Can you reduce the code to a small failing example?
Also, on the snippet attached, what do you mean the compiler has a problem?
Likewise can you send a complete small example of valid code? I assume you are
getting some sort of compilation error, but not sure what you mean.
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
2013-12-15 22:19 ` [Bug libfortran/59513] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE jvdelisle at gcc dot gnu.org
@ 2013-12-15 22:33 ` aruopp at gmx dot de
2013-12-16 0:02 ` aruopp at gmx dot de
` (30 subsequent siblings)
32 siblings, 0 replies; 33+ messages in thread
From: aruopp at gmx dot de @ 2013-12-15 22:33 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
--- Comment #2 from aruopp at gmx dot de ---
Hi,
compilation of code works without any problems.
Only if I execute the code, the problem exists with this error message.
The file 'polarfile_1.dat' is written during executing xfoil, but no values are
written into the file.
I tried to fix it, since error message during run points to mentioned code line
in iopol.f, at line 652 (see previous error message with link):
DO IA = IA1, IA2
OPEN(LU,FILE=FNPOL,STATUS='OLD',POSITION='APPEND',ERR=90)
WRITE(LU,LINEF)
& (CPOL(IA,IPOL(KP)), KP=1, NIPOL),
& ((CPOLSD(IA,IS,JPOL(KP)), IS=1, 2*NBL), KP=1, NJPOL)
CLOSE(LU)
ENDDO
But this didn't work, too.
Why is it working with an older gcc-version?
I will try to make a small code example but I'm not a fortran expert.
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
2013-12-15 22:19 ` [Bug libfortran/59513] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE jvdelisle at gcc dot gnu.org
2013-12-15 22:33 ` aruopp at gmx dot de
@ 2013-12-16 0:02 ` aruopp at gmx dot de
2013-12-18 14:53 ` aruopp at gmx dot de
` (29 subsequent siblings)
32 siblings, 0 replies; 33+ messages in thread
From: aruopp at gmx dot de @ 2013-12-16 0:02 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
--- Comment #3 from aruopp at gmx dot de ---
Inserting the backspace:
BACKSPACE(LU)
before loop
DO 40 IA = IA1, IA2
WRITE(LU,LINEF)
& (CPOL(IA,IPOL(KP)), KP=1, NIPOL),
& ((CPOLSD(IA,IS,JPOL(KP)), IS=1, 2*NBL), KP=1, NJPOL)
40 CONTINUE
works now.
I guess, gfortran standard changed?
I'm not sure, because older gcc-versions worked with this code without any
problems.
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
` (2 preceding siblings ...)
2013-12-16 0:02 ` aruopp at gmx dot de
@ 2013-12-18 14:53 ` aruopp at gmx dot de
2013-12-18 14:56 ` aruopp at gmx dot de
` (28 subsequent siblings)
32 siblings, 0 replies; 33+ messages in thread
From: aruopp at gmx dot de @ 2013-12-18 14:53 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
--- Comment #5 from ARuopp <aruopp at gmx dot de> ---
Created attachment 31469
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31469&action=edit
test script for running xfoil with output in file
this is a test script for testing xfoil in running in batch mode.
what it does:
starting xfoil
loading a test profil naca 0018
setting values
calculating some lift and drag values for different aoa
writing solution in polarfile_1.dat
then it finishes
in shell execute the program like this:
xfoil < xfoil.naca.run1
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
` (3 preceding siblings ...)
2013-12-18 14:53 ` aruopp at gmx dot de
@ 2013-12-18 14:56 ` aruopp at gmx dot de
2013-12-18 14:57 ` aruopp at gmx dot de
` (27 subsequent siblings)
32 siblings, 0 replies; 33+ messages in thread
From: aruopp at gmx dot de @ 2013-12-18 14:56 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
--- Comment #6 from ARuopp <aruopp at gmx dot de> ---
Hi,
thank you very much for your effort.
Compiling is not the problem.
Try to execute the script, which I attached.
Without the "backspace" modification, xfoil ends with the error message:
At line 655 of file ../src/iopol.f (unit = 9, file = 'polarfile_1.dat')
Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker,
possibly use REWIND or BACKSPACE
Is your xfoil running without the modification?
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
` (4 preceding siblings ...)
2013-12-18 14:56 ` aruopp at gmx dot de
@ 2013-12-18 14:57 ` aruopp at gmx dot de
2013-12-18 15:04 ` dominiq at lps dot ens.fr
` (26 subsequent siblings)
32 siblings, 0 replies; 33+ messages in thread
From: aruopp at gmx dot de @ 2013-12-18 14:57 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
--- Comment #7 from ARuopp <aruopp at gmx dot de> ---
Execute with:
xfoil < xfoil.naca.run1
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
` (5 preceding siblings ...)
2013-12-18 14:57 ` aruopp at gmx dot de
@ 2013-12-18 15:04 ` dominiq at lps dot ens.fr
2013-12-18 15:19 ` aruopp at gmx dot de
` (25 subsequent siblings)
32 siblings, 0 replies; 33+ messages in thread
From: dominiq at lps dot ens.fr @ 2013-12-18 15:04 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2013-12-18
Ever confirmed|0 |1
--- Comment #8 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Running your script on xfoil built by fink (gfortran 4.8.2) ends with the
reported error:
10 rms: 0.6268E-05 max: -.8920E-04 D at 83 1
a = 0.000 CL = -0.0000
Cm = 0.0000 CD = 0.00773 => CDf = 0.00549 CDp = 0.00224
Point added to stored polar 1
At line 652 of file ../src/iopol.f (unit = 9, file = 'polarfile_1.dat')
Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker,
possibly use REWIND or BACKSPACE
I'll try to find some time to build foil myself with earlier versions (don't
hold your breath!-).
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
` (6 preceding siblings ...)
2013-12-18 15:04 ` dominiq at lps dot ens.fr
@ 2013-12-18 15:19 ` aruopp at gmx dot de
2013-12-18 16:23 ` dominiq at lps dot ens.fr
` (24 subsequent siblings)
32 siblings, 0 replies; 33+ messages in thread
From: aruopp at gmx dot de @ 2013-12-18 15:19 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
--- Comment #9 from ARuopp <aruopp at gmx dot de> ---
BTW:
"At line 652 of file...."is correct.
Line 655 was including some comments from my side... I didn't want to
confuse....
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
` (7 preceding siblings ...)
2013-12-18 15:19 ` aruopp at gmx dot de
@ 2013-12-18 16:23 ` dominiq at lps dot ens.fr
2013-12-18 16:35 ` [Bug libfortran/59513] [4.7/4.8/4.9] " dominiq at lps dot ens.fr
` (23 subsequent siblings)
32 siblings, 0 replies; 33+ messages in thread
From: dominiq at lps dot ens.fr @ 2013-12-18 16:23 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
--- Comment #10 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
I also see the problem with gfortran 4.7.3.
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] [4.7/4.8/4.9] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
` (8 preceding siblings ...)
2013-12-18 16:23 ` dominiq at lps dot ens.fr
@ 2013-12-18 16:35 ` dominiq at lps dot ens.fr
2013-12-19 15:21 ` rguenth at gcc dot gnu.org
` (22 subsequent siblings)
32 siblings, 0 replies; 33+ messages in thread
From: dominiq at lps dot ens.fr @ 2013-12-18 16:35 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Fortran runtime error: |[4.7/4.8/4.9] Fortran
|Sequential READ or WRITE |runtime error: Sequential
|not allowed after EOF |READ or WRITE not allowed
|marker, possibly use REWIND |after EOF marker, possibly
|or BACKSPACE |use REWIND or BACKSPACE
--- Comment #11 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
No error with gfortran 4.4.7, 4.5.4, but gfortran 4.6.4 gives the error. So
marked as a 4.7/4.8/4.9 regression.
When I'll have learnt how to build foil myself, I'll try to do some bisection
and some reduction.
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] [4.7/4.8/4.9] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
` (9 preceding siblings ...)
2013-12-18 16:35 ` [Bug libfortran/59513] [4.7/4.8/4.9] " dominiq at lps dot ens.fr
@ 2013-12-19 15:21 ` rguenth at gcc dot gnu.org
2013-12-19 15:43 ` rguenth at gcc dot gnu.org
` (21 subsequent siblings)
32 siblings, 0 replies; 33+ messages in thread
From: rguenth at gcc dot gnu.org @ 2013-12-19 15:21 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |4.7.4
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] [4.7/4.8/4.9] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
` (10 preceding siblings ...)
2013-12-19 15:21 ` rguenth at gcc dot gnu.org
@ 2013-12-19 15:43 ` rguenth at gcc dot gnu.org
2014-05-27 13:01 ` giorgio.signorini at unifi dot it
` (20 subsequent siblings)
32 siblings, 0 replies; 33+ messages in thread
From: rguenth at gcc dot gnu.org @ 2013-12-19 15:43 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P5
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] [4.7/4.8/4.9] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
` (11 preceding siblings ...)
2013-12-19 15:43 ` rguenth at gcc dot gnu.org
@ 2014-05-27 13:01 ` giorgio.signorini at unifi dot it
2014-06-12 13:52 ` [Bug libfortran/59513] [4.8/4.9 Regression] " rguenth at gcc dot gnu.org
` (19 subsequent siblings)
32 siblings, 0 replies; 33+ messages in thread
From: giorgio.signorini at unifi dot it @ 2014-05-27 13:01 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
giorgio.signorini at unifi dot it changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |giorgio.signorini at unifi dot it
--- Comment #13 from giorgio.signorini at unifi dot it ---
(In reply to Dominique d'Humieres from comment #11)
> No error with gfortran 4.4.7, 4.5.4, but gfortran 4.6.4 gives the error. So
> marked as a 4.7/4.8/4.9 regression.
>
> When I'll have learnt how to build foil myself, I'll try to do some
> bisection and some reduction.
I think this is connected to bug 44477
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44477), which has been fixed in
gfortran 4.6.
Could it be that the POSITION='APPEND' option acts like a sequence of READs up
to EOF, which in gfortran < 4.6 did a silent, non-standard BACKSPACE?
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] [4.8/4.9 Regression] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
` (12 preceding siblings ...)
2014-05-27 13:01 ` giorgio.signorini at unifi dot it
@ 2014-06-12 13:52 ` rguenth at gcc dot gnu.org
2014-07-11 17:33 ` [Bug libfortran/59513] [4.8/4.9/4.10 " dominiq at lps dot ens.fr
` (18 subsequent siblings)
32 siblings, 0 replies; 33+ messages in thread
From: rguenth at gcc dot gnu.org @ 2014-06-12 13:52 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|4.7.4 |4.8.4
Summary|[4.7/4.8/4.9] Fortran |[4.8/4.9 Regression]
|runtime error: Sequential |Fortran runtime error:
|READ or WRITE not allowed |Sequential READ or WRITE
|after EOF marker, possibly |not allowed after EOF
|use REWIND or BACKSPACE |marker, possibly use REWIND
| |or BACKSPACE
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] [4.8/4.9/4.10 Regression] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
` (13 preceding siblings ...)
2014-06-12 13:52 ` [Bug libfortran/59513] [4.8/4.9 Regression] " rguenth at gcc dot gnu.org
@ 2014-07-11 17:33 ` dominiq at lps dot ens.fr
2014-07-12 11:39 ` dominiq at lps dot ens.fr
` (17 subsequent siblings)
32 siblings, 0 replies; 33+ messages in thread
From: dominiq at lps dot ens.fr @ 2014-07-11 17:33 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[4.8/4.9 Regression] |[4.8/4.9/4.10 Regression]
|Fortran runtime error: |Fortran runtime error:
|Sequential READ or WRITE |Sequential READ or WRITE
|not allowed after EOF |not allowed after EOF
|marker, possibly use REWIND |marker, possibly use REWIND
|or BACKSPACE |or BACKSPACE
--- Comment #14 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Still present at r212457, updating the summary.
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] [4.8/4.9/4.10 Regression] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
` (14 preceding siblings ...)
2014-07-11 17:33 ` [Bug libfortran/59513] [4.8/4.9/4.10 " dominiq at lps dot ens.fr
@ 2014-07-12 11:39 ` dominiq at lps dot ens.fr
2014-07-12 13:11 ` dominiq at lps dot ens.fr
` (16 subsequent siblings)
32 siblings, 0 replies; 33+ messages in thread
From: dominiq at lps dot ens.fr @ 2014-07-12 11:39 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
--- Comment #16 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
The change occurred between revisions r158253 (2010-04-13, "working?") and
r162456 (2010-07-23, error). It could be r161021 (pr44477).
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] [4.8/4.9/4.10 Regression] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
` (15 preceding siblings ...)
2014-07-12 11:39 ` dominiq at lps dot ens.fr
@ 2014-07-12 13:11 ` dominiq at lps dot ens.fr
2014-07-12 13:24 ` dominiq at lps dot ens.fr
` (15 subsequent siblings)
32 siblings, 0 replies; 33+ messages in thread
From: dominiq at lps dot ens.fr @ 2014-07-12 13:11 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
--- Comment #17 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
I wonder if the gfortran present behavior is not the *RIGHT* one. It is
obviously for any READ following 'CALL BOTTOM(LU)', I am not 100% confident for
WRITE. Not that replacing
90 RETURN
with
90 BACKSPACE(LU)
RETURN
allows the test to run.
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] [4.8/4.9/4.10 Regression] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
` (16 preceding siblings ...)
2014-07-12 13:11 ` dominiq at lps dot ens.fr
@ 2014-07-12 13:24 ` dominiq at lps dot ens.fr
2014-07-12 18:02 ` dominiq at lps dot ens.fr
` (14 subsequent siblings)
32 siblings, 0 replies; 33+ messages in thread
From: dominiq at lps dot ens.fr @ 2014-07-12 13:24 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
--- Comment #18 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> It could be r161021 (pr44477).
Read r161020 and the error message has been introduced in
libgfortran/io/transfer.c at this revision.
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] [4.8/4.9/4.10 Regression] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
` (17 preceding siblings ...)
2014-07-12 13:24 ` dominiq at lps dot ens.fr
@ 2014-07-12 18:02 ` dominiq at lps dot ens.fr
2014-07-12 19:43 ` jvdelisle at gcc dot gnu.org
` (13 subsequent siblings)
32 siblings, 0 replies; 33+ messages in thread
From: dominiq at lps dot ens.fr @ 2014-07-12 18:02 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
--- Comment #19 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
I have rebuilt a clean Xfoil with the following patch
--- src_orig/xpol.f 2007-09-16 03:56:31.000000000 +0200
+++ src/xpol.f 2014-07-12 19:55:40.000000000 +0200
@@ -606,8 +606,7 @@ C---- add point to save file
IPOL(NIPOL) = ICH
ENDIF
C
- OPEN(LU,FILE=PFNAME(IP),STATUS='OLD')
- CALL BOTTOM(LU)
+ OPEN(LU,FILE=PFNAME(IP),STATUS='OLD', POSITION = 'APPEND')
IA = NAPOL(IP)
CALL POLWRIT(LU,' ',ERROR, .FALSE.,
& NAX, IA,IA, CPOL(1,1,IP), IPOL,NIPOL,
@@ -648,8 +647,8 @@ C
BETA = SQRT(1.0 - MINF**2)
BFAC = 0.5*MINF**2 / (1.0 + BETA)
C
- OPEN(LU,FILE=PFNAMX(IP),STATUS='OLD',FORM='UNFORMATTED')
- CALL BOTTOMX(LU)
+ OPEN(LU,FILE=PFNAMX(IP),STATUS='OLD',FORM='UNFORMATTED',
+ & POSITION='APPEND')
C
C---- write integrated forces to unformatted dump file
IF(LVISC) THEN
@@ -920,26 +919,3 @@ C
RETURN
END ! POLAXI
-
-
- SUBROUTINE BOTTOM(LU)
- CHARACTER*1 DUMMY
-C
- 10 READ(LU,1000,END=90,ERR=90) DUMMY
- 1000 FORMAT(A)
- GO TO 10
-C
- 90 RETURN
- END
-
-
- SUBROUTINE BOTTOMX(LU)
- CHARACTER*1 DUMMY
-C
- 10 READ(LU,END=90,ERR=90) DUMMY
- GO TO 10
-C
- 90 RETURN
- END
-
-
and the script works fine.
Note that the following patch is also needed
diff -Naur Xfoil_orig/src/pplot.f Xfoil/src/pplot.f
--- Xfoil_orig/src/pplot.f 2008-04-07 17:05:29.000000000 -0400
+++ Xfoil/srcpplot.f 2008-04-09 18:50:59.000000000 -0400
@@ -36,7 +36,7 @@
PROGRAM PPLOT
INCLUDE 'PPLOT.INC'
C
- LOGICAL ERROR, LGETFN
+ LOGICAL ERROR, LGETFN, LERR
REAL RINP(10)
REAL CPOLO(NAX,IPTOT,NPX), VPOLO(NAX,2,NPX)
C
otherwise gfortran complains about INTEGER instead of LOGICAL for 'IF(LERR)'.
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] [4.8/4.9/4.10 Regression] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
` (18 preceding siblings ...)
2014-07-12 18:02 ` dominiq at lps dot ens.fr
@ 2014-07-12 19:43 ` jvdelisle at gcc dot gnu.org
2014-07-15 16:39 ` dominiq at lps dot ens.fr
` (12 subsequent siblings)
32 siblings, 0 replies; 33+ messages in thread
From: jvdelisle at gcc dot gnu.org @ 2014-07-12 19:43 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
--- Comment #20 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
I think gfortran behavior is correct. The problem with the sample code is in
the lack of handling in subroutine BOTTOM. The loop is reading past the end of
the file. END= is not a true error condition, but a file condition. One can not
just ignore it, the read has gone past the End-Of-File marker. It is necessary
to position the file.
Also, this is really not good coding practice to do nothing on ERR=. ERR=
really is an ERROR.
SUBROUTINE BOTTOM(LU)
CHARACTER*1 DUMMY
10 READ(LU,1000,END=90,ERR=90) DUMMY
1000 FORMAT(A)
GO TO 10
90 BACKSPACE(LU)
RETURN
END
Fortran 2003 Standard: 9.2.3.2 File position prior to data transfer
If the file contains an endfile record, the file shall not be positioned after
the endfile record prior to data transfer. However, a REWIND or BACKSPACE
statement may be used to reposition the file.
Based on this I believe the resolution of this bug is 'INVALID'. The bug is in
xfoil. We could choose to disable the error on -std=legacy. I do not know
what the old g77 did. I will check that.
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] [4.8/4.9/4.10 Regression] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
` (19 preceding siblings ...)
2014-07-12 19:43 ` jvdelisle at gcc dot gnu.org
@ 2014-07-15 16:39 ` dominiq at lps dot ens.fr
2014-07-15 21:44 ` manfred99 at gmx dot ch
` (11 subsequent siblings)
32 siblings, 0 replies; 33+ messages in thread
From: dominiq at lps dot ens.fr @ 2014-07-15 16:39 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
--- Comment #21 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
(In reply to Jerry DeLisle from comment #20)
> Based on this I believe the resolution of this bug is 'INVALID'. ...
I fully agree. If there is no objection before next Wednesday (July 23, 21014),
I'll close the PR.
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] [4.8/4.9/4.10 Regression] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
` (20 preceding siblings ...)
2014-07-15 16:39 ` dominiq at lps dot ens.fr
@ 2014-07-15 21:44 ` manfred99 at gmx dot ch
2014-07-15 22:07 ` dominiq at lps dot ens.fr
` (10 subsequent siblings)
32 siblings, 0 replies; 33+ messages in thread
From: manfred99 at gmx dot ch @ 2014-07-15 21:44 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
Manfred Schwarb <manfred99 at gmx dot ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |manfred99 at gmx dot ch
--- Comment #22 from Manfred Schwarb <manfred99 at gmx dot ch> ---
I just encountered the same issue, with some convoluted legacy code.
The scheme seems to be the same:
READ(lun,END=100) buffer
100 WRITE(lun,*) "whatever"
As the used code definitely was used in practice, mainly before the year
2000, I guess that older compiler supported this.
And yes, the BACKSPACE() trick works. However, common sense suggest
that with END= we are at the end of the file. This sounds a bit like the
old joke, where you have a room with 5 people, you are taking 6 out, so
someone has to go in for the room to be empty. Beyond EOF simply does
not exist.
Jerry, concerning your cited standard:
"If the file contains an endfile record" suggests that there is some
special marker in the file to be read/written.
In this example, we are doing some formatted IO to a plain text file,
there are no special markers.
Do I miss something?
What does/should ftell() report in such a case? That we are one
character beyond EOF?
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] [4.8/4.9/4.10 Regression] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
` (21 preceding siblings ...)
2014-07-15 21:44 ` manfred99 at gmx dot ch
@ 2014-07-15 22:07 ` dominiq at lps dot ens.fr
2014-07-16 1:45 ` jvdelisle at gcc dot gnu.org
` (9 subsequent siblings)
32 siblings, 0 replies; 33+ messages in thread
From: dominiq at lps dot ens.fr @ 2014-07-15 22:07 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
--- Comment #23 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> Jerry, concerning your cited standard:
> "If the file contains an endfile record" suggests that there is some
> special marker in the file to be read/written.
>From the standard:
> NOTE 9.2
> An endfile record does not necessarily have any physical embodiment. The
> processor may use a record count or other means to register the position
> of the file at the time an ENDFILE statement is executed, so that it can take
> appropriate action when that position is reached again during a read
> operation. The endfile record, however it is implemented, is considered
> to exist for the BACKSPACE statement (9.8.2).
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] [4.8/4.9/4.10 Regression] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
` (22 preceding siblings ...)
2014-07-15 22:07 ` dominiq at lps dot ens.fr
@ 2014-07-16 1:45 ` jvdelisle at gcc dot gnu.org
2014-07-16 10:37 ` manfred99 at gmx dot ch
` (8 subsequent siblings)
32 siblings, 0 replies; 33+ messages in thread
From: jvdelisle at gcc dot gnu.org @ 2014-07-16 1:45 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
--- Comment #24 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
(In reply to Manfred Schwarb from comment #22)
--- snip ---
> Jerry, concerning your cited standard:
> "If the file contains an endfile record" suggests that there is some
> special marker in the file to be read/written.
> In this example, we are doing some formatted IO to a plain text file,
> there are no special markers.
> Do I miss something?
>
> What does/should ftell() report in such a case? That we are one
> character beyond EOF?
I think Dominique has answered as far as the physical aspect.
FTELL just returns the current physical location.
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] [4.8/4.9/4.10 Regression] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
` (23 preceding siblings ...)
2014-07-16 1:45 ` jvdelisle at gcc dot gnu.org
@ 2014-07-16 10:37 ` manfred99 at gmx dot ch
2014-07-16 10:49 ` manfred99 at gmx dot ch
` (7 subsequent siblings)
32 siblings, 0 replies; 33+ messages in thread
From: manfred99 at gmx dot ch @ 2014-07-16 10:37 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
--- Comment #25 from Manfred Schwarb <manfred99 at gmx dot ch> ---
OK, thanks Jerry and Dominique for the explanations.
It seems the correct syntax then is:
READ(lun,END=100) buffer
GOTO 101
100 BACKSPACE(lun)
101 WRITE(lun,*) "whatever"
Not that the above code would make sense to me as a mere user,
but it works both with gfortran 4.5 and 4.6 upwards.
I just wrote a small test program, the output is identical for
gfortran 4.5 and 4.6+:
CHARACTER*20 buffer,buffer2
INTEGER i
buffer=""
buffer2=""
OPEN(10,FILE="test.txt")
WRITE(10,'(a)') "0123456789"
CLOSE(10)
OPEN(10,FILE="test.txt",POSITION="APPEND")
CALL ftell(10,i)
print*,"file position in append mode:",i
CLOSE(10)
OPEN(10,FILE="test.txt")
READ(10,'(a20)') buffer
print*,"X",buffer,"X"
CALL ftell(10,i)
print*,"file position after reading buffer:",i
CC BACKSPACE(10) ! then below write will overwrite first line
WRITE(10,'(a)') "ABC"
CLOSE(10)
CALL system("cat test.txt")
OPEN(10,FILE="test.txt")
WRITE(10,'(a)') "0123456789"
CLOSE(10)
OPEN(10,FILE="test.txt")
READ(10,'(a20)',END=100) buffer,buffer2
GOTO 101
100 CALL ftell(10,i)
print*,"END clause encountered: file position:",i
BACKSPACE(10)
101 CALL ftell(10,i)
print*,"file position:",i
print*,"X",buffer,"X",buffer2,"X"
WRITE(10,'(a)') "ABC"
CLOSE(10)
CALL system("cat test.txt")
END
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] [4.8/4.9/4.10 Regression] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
` (24 preceding siblings ...)
2014-07-16 10:37 ` manfred99 at gmx dot ch
@ 2014-07-16 10:49 ` manfred99 at gmx dot ch
2014-12-19 13:34 ` [Bug libfortran/59513] [4.8/4.9/5 " jakub at gcc dot gnu.org
` (6 subsequent siblings)
32 siblings, 0 replies; 33+ messages in thread
From: manfred99 at gmx dot ch @ 2014-07-16 10:49 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
--- Comment #26 from Manfred Schwarb <manfred99 at gmx dot ch> ---
I just tested g77.
As suspected, g77 is in line with gfortran 4.5.
It happily accepts the following and does not throw an error
in the END clause case:
READ(lun,END=100) buffer
100 WRITE(lun,*) "whatever"
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] [4.8/4.9/5 Regression] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
` (25 preceding siblings ...)
2014-07-16 10:49 ` manfred99 at gmx dot ch
@ 2014-12-19 13:34 ` jakub at gcc dot gnu.org
2015-03-22 22:59 ` jvdelisle at gcc dot gnu.org
` (5 subsequent siblings)
32 siblings, 0 replies; 33+ messages in thread
From: jakub at gcc dot gnu.org @ 2014-12-19 13:34 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|4.8.4 |4.8.5
--- Comment #27 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
GCC 4.8.4 has been released.
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] [4.8/4.9/5 Regression] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
` (26 preceding siblings ...)
2014-12-19 13:34 ` [Bug libfortran/59513] [4.8/4.9/5 " jakub at gcc dot gnu.org
@ 2015-03-22 22:59 ` jvdelisle at gcc dot gnu.org
2015-03-22 23:56 ` jvdelisle at gcc dot gnu.org
` (4 subsequent siblings)
32 siblings, 0 replies; 33+ messages in thread
From: jvdelisle at gcc dot gnu.org @ 2015-03-22 22:59 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
--- Comment #29 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
Author: jvdelisle
Date: Sun Mar 22 21:37:13 2015
New Revision: 221575
URL: https://gcc.gnu.org/viewcvs?rev=221575&root=gcc&view=rev
Log:
2015-03-22 Jerry DeLisle <jvdelisle@gcc.gnu.org>
PR libgfortran/59513
* gfortran.texi (Read/Write after EOF marker): New information.
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/gfortran.texi
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] [4.8/4.9/5 Regression] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
` (27 preceding siblings ...)
2015-03-22 22:59 ` jvdelisle at gcc dot gnu.org
@ 2015-03-22 23:56 ` jvdelisle at gcc dot gnu.org
2015-03-25 18:46 ` dominiq at lps dot ens.fr
` (3 subsequent siblings)
32 siblings, 0 replies; 33+ messages in thread
From: jvdelisle at gcc dot gnu.org @ 2015-03-22 23:56 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |jvdelisle at gcc dot gnu.org
--- Comment #30 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
Fixed on 5.0, will backport in a few days.
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] [4.8/4.9/5 Regression] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
` (28 preceding siblings ...)
2015-03-22 23:56 ` jvdelisle at gcc dot gnu.org
@ 2015-03-25 18:46 ` dominiq at lps dot ens.fr
2015-03-30 17:45 ` jvdelisle at gcc dot gnu.org
` (2 subsequent siblings)
32 siblings, 0 replies; 33+ messages in thread
From: dominiq at lps dot ens.fr @ 2015-03-25 18:46 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tkoenig at gcc dot gnu.org
--- Comment #31 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
*** Bug 65565 has been marked as a duplicate of this bug. ***
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] [4.8/4.9/5 Regression] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
` (29 preceding siblings ...)
2015-03-25 18:46 ` dominiq at lps dot ens.fr
@ 2015-03-30 17:45 ` jvdelisle at gcc dot gnu.org
2015-03-30 21:59 ` jvdelisle at gcc dot gnu.org
2015-03-30 22:35 ` jvdelisle at gcc dot gnu.org
32 siblings, 0 replies; 33+ messages in thread
From: jvdelisle at gcc dot gnu.org @ 2015-03-30 17:45 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
--- Comment #32 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
Author: jvdelisle
Date: Mon Mar 30 16:51:37 2015
New Revision: 221772
URL: https://gcc.gnu.org/viewcvs?rev=221772&root=gcc&view=rev
Log:
2015-03-30 Jerry DeLisle <jvdelisle@gcc.gnu.org>
PR libgfortran/59513
* io/transfer.c (data_transfer_init): Do not error for
-std=legacy.
Modified:
branches/gcc-4_9-branch/libgfortran/ChangeLog
branches/gcc-4_9-branch/libgfortran/io/transfer.c
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] [4.8/4.9/5 Regression] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
` (30 preceding siblings ...)
2015-03-30 17:45 ` jvdelisle at gcc dot gnu.org
@ 2015-03-30 21:59 ` jvdelisle at gcc dot gnu.org
2015-03-30 22:35 ` jvdelisle at gcc dot gnu.org
32 siblings, 0 replies; 33+ messages in thread
From: jvdelisle at gcc dot gnu.org @ 2015-03-30 21:59 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
--- Comment #33 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
Author: jvdelisle
Date: Mon Mar 30 20:47:40 2015
New Revision: 221778
URL: https://gcc.gnu.org/viewcvs?rev=221778&root=gcc&view=rev
Log:
2015-03-30 Jerry DeLisle <jvdelisle@gcc.gnu.org>
PR libgfortran/59513
* io/transfer.c (data_transfer_init): Do not error for
-std=legacy.
Modified:
branches/gcc-4_8-branch/libgfortran/ChangeLog
branches/gcc-4_8-branch/libgfortran/io/transfer.c
^ permalink raw reply [flat|nested] 33+ messages in thread* [Bug libfortran/59513] [4.8/4.9/5 Regression] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE
[not found] <bug-59513-4@http.gcc.gnu.org/bugzilla/>
` (31 preceding siblings ...)
2015-03-30 21:59 ` jvdelisle at gcc dot gnu.org
@ 2015-03-30 22:35 ` jvdelisle at gcc dot gnu.org
32 siblings, 0 replies; 33+ messages in thread
From: jvdelisle at gcc dot gnu.org @ 2015-03-30 22:35 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513
Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #34 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
Fixed on 4.8, 4.9, and 5.0 Closing.
^ permalink raw reply [flat|nested] 33+ messages in thread