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/39072] I/O READing logical value beyond end of string
Date: Tue, 03 Feb 2009 10:02:00 -0000 [thread overview]
Message-ID: <20090203100218.22398.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39072-13404@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from burnus at gcc dot gnu dot org 2009-02-03 10:02 -------
> I believe gfortran is correct as far as giving an error. The last logical
> value does not begin with a T(t) or F(f).
That was my impression in comment 0 ("maybe wontfix"), which was confirmed by
the standard (comment 2); when I filled I was unsure since so many compilers
support it. (I encountered it in Fleur (www.flapw.de) and it took me a while to
figure out what was wrong.)
> The only thing remaining here to me is are we attempting to read past the end
> of record with the error case and so should we really be giving an EOR.
Hmm, I wonder whether it should be EOR. NAG f95 and g95 also give an error for
an invalid logical and not an EOR.
("No value found in LOGICAL input field", "Bad value on logical read")
Testing for "iostat=" using IS_IOSTAT_EOR(I),IS_IOSTAT_END(I), gives with all
three compilers a F(alse).
Thus, I would suggest WONTFIX.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39072
next prev parent reply other threads:[~2009-02-03 10:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-01 23:08 [Bug fortran/39072] New: " burnus at gcc dot gnu dot org
2009-02-01 23:09 ` [Bug fortran/39072] " burnus at gcc dot gnu dot org
2009-02-01 23:18 ` burnus at gcc dot gnu dot org
2009-02-03 4:43 ` jvdelisle at gcc dot gnu dot org
2009-02-03 10:02 ` burnus at gcc dot gnu dot org [this message]
2009-02-04 1:55 ` 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=20090203100218.22398.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).