--- Comment #10 from michael dot a dot richmond at nasa dot gov 2010-06-22
11:55 ---
(In reply to comment #9)
Michael, is this a legacy code issue? two ENDFILE in a row?
It is legacy code
--
michael dot a dot richmond at nasa dot gov changed:
What|Removed
--- Comment #11 from burnus at gcc dot gnu dot org 2010-06-22 13:01 ---
(In reply to comment #10)
(In reply to comment #9)
Michael, is this a legacy code issue? two ENDFILE in a row?
It is legacy code
Any idea how to best deal with this?
The standard is pretty clear that it is
--- Comment #12 from michael dot a dot richmond at nasa dot gov 2010-06-22
13:02 ---
I will modify my code
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44477
--- Comment #13 from jvdelisle at gcc dot gnu dot org 2010-06-23 02:37
---
Closing as fixed. If the issue of double endfile sequences pops up again we
can consider putting th errors behind -std=legacy.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44477
--- Comment #14 from jvdelisle at gcc dot gnu dot org 2010-06-23 02:37
---
Closed
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #7 from michael dot a dot richmond at nasa dot gov 2010-06-20
16:14 ---
The following occurs in the snapshot of June 19, but not in earlier snapshots:
mrich...@msc545ux:~$ cat test.f90
PROGRAM test
END FILE 10
END FILE 10
END PROGRAM test
mrich...@msc545ux:~$ gfortran
--- Comment #8 from kargl at gcc dot gnu dot org 2010-06-20 16:41 ---
(In reply to comment #7)
The following occurs in the snapshot of June 19, but not in earlier snapshots:
mrich...@msc545ux:~$ cat test.f90
PROGRAM test
END FILE 10
END FILE 10
END PROGRAM test
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2010-06-20 19:57
---
Michael, is this a legacy code issue? two ENDFILE in a row?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44477
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2010-06-19 00:58
---
Subject: Bug 44477
Author: jvdelisle
Date: Sat Jun 19 00:58:28 2010
New Revision: 161020
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=161020
Log:
2010-06-18 Jerry DeLisle jvdeli...@gcc.gnu.org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2010-06-19 01:05
---
Subject: Bug 44477
Author: jvdelisle
Date: Sat Jun 19 01:05:05 2010
New Revision: 161021
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=161021
Log:
2010-06-18 Jerry DeLisle jvdeli...@gcc.gnu.org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2010-06-12 22:33
---
How about this when attempting a READ or WRITE after an ENDFILE. (original
testcase)
$ gfc pr44477.f90
$ ./a.out
At line 5 of file pr44477.f90 (unit = 10, file = 'XXX')
Fortran runtime error: Sequential READ
--- Comment #3 from burnus at gcc dot gnu dot org 2010-06-11 16:27 ---
For completeness, also Cray Fortran 7.2.3 prints:
A WRITE operation is invalid if the file is positioned after the end-of-file.
Updated summary:
- Error with: NAG f95 v5.1, Pathscale pathf95 3.2.99, Cray ftn
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2010-06-09 19:24
---
As I read this, the test case is invalid since it does not have a rewind or
backspace before the write?
If we want to change this to be an intended extension, I suppose we should
issue a warning or error for
--- Comment #2 from burnus at gcc dot gnu dot org 2010-06-09 19:41 ---
(In reply to comment #1)
As I read this, the test case is invalid since it does not have a rewind or
backspace before the write?
Yes - I expect that gfortran should issue an EOR error instead of happily
accepting
14 matches
Mail list logo
