public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/44477] Sequential I/O with END FILE: File position should be at EoF
Date: Fri, 11 Jun 2010 16:27:00 -0000 [thread overview]
Message-ID: <20100611162700.18313.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44477-13404@http.gcc.gnu.org/bugzilla/>
------- 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 8.2.3, Open64
4.2
- No error with: ifort 11.1, gfortran, g95, sunf95 8.3 (sunstudio12),
Portland's pgf90
v6.2 and v10.3.
- Unknown: g77, ...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44477
next prev parent reply other threads:[~2010-06-11 16:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 8:13 [Bug fortran/44477] New: " burnus at gcc dot gnu dot org
2010-06-09 19:24 ` [Bug fortran/44477] " jvdelisle at gcc dot gnu dot org
2010-06-09 19:41 ` burnus at gcc dot gnu dot org
2010-06-11 16:27 ` burnus at gcc dot gnu dot org [this message]
2010-06-12 22:33 ` jvdelisle at gcc dot gnu dot org
2010-06-19 0:58 ` jvdelisle at gcc dot gnu dot org
2010-06-19 1:05 ` jvdelisle at gcc dot gnu dot org
2010-06-20 16:15 ` michael dot a dot richmond at nasa dot gov
2010-06-20 16:41 ` kargl at gcc dot gnu dot org
2010-06-20 19:58 ` jvdelisle at gcc dot gnu dot org
2010-06-22 11:56 ` michael dot a dot richmond at nasa dot gov
2010-06-22 13:01 ` burnus at gcc dot gnu dot org
2010-06-22 13:02 ` michael dot a dot richmond at nasa dot gov
2010-06-23 2:37 ` jvdelisle at gcc dot gnu dot org
2010-06-23 2:38 ` jvdelisle at gcc dot gnu dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100611162700.18313.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).