This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/37129] Problems with access='direct', recl=1 I/O
- From: "burnus at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 17 Aug 2008 17:59:53 -0000
- Subject: [Bug fortran/37129] Problems with access='direct', recl=1 I/O
- References: <bug-37129-16600@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #5 from burnus at gcc dot gnu dot org 2008-08-17 17:59 -------
For completeness, I tested the program with a couple of compilers, which all
generated a run-time error message:
- Intel ifort 10 and 11beta
- Sun Studio 12 sunf95
- g95
- Portland pgf77 7.1
- Open64 openf95
- Pathscale 3.1 pathf90
Thus I'm wondering whether it makes really sense to support it with
-std=legacy; on the other hand, I don't see off hand how this can break things
and thus g77's behaviour with -std=legacy might be possible.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37129