public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/43265] [4.3/4.4/4.5 Regression] No EOF condition if reading with '(x)' from an empty file
Date: Fri, 12 Mar 2010 14:33:00 -0000 [thread overview]
Message-ID: <20100312143252.21280.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43265-14178@http.gcc.gnu.org/bugzilla/>
------- Comment #17 from jvdelisle at gcc dot gnu dot org 2010-03-12 14:32 -------
Subject: Bug 43265
Author: jvdelisle
Date: Fri Mar 12 14:32:39 2010
New Revision: 157404
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=157404
Log:
2010-03-12 Jerry DeLisle <jvdelisle@gcc.gnu.org>
PR libfortran/43265
Backport from trunk.
* io/read.c (read_x): Replace the use of read_sf with equivalent lower
level I/O, eliminating unneeded code and handling EOF and EOR
conditions.
* io/io.h: Revise prototype for read_sf.
* io/transfer.c (read_sf): Delete no_error parameter and all uses of
it.
Set eof and eor condition flags. (read_block_form): Likewise.
(next_record_r): Add condition to call to hit_eof.
Modified:
branches/gcc-4_4-branch/libgfortran/ChangeLog
branches/gcc-4_4-branch/libgfortran/io/io.h
branches/gcc-4_4-branch/libgfortran/io/read.c
branches/gcc-4_4-branch/libgfortran/io/transfer.c
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43265
next prev parent reply other threads:[~2010-03-12 14:33 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 6:05 [Bug fortran/43265] New: Read no longer jumps on end terry at chem dot gu dot se
2010-03-05 9:08 ` [Bug fortran/43265] [4.3/4.4/4.5 Regression] No EOF condition if reading with '(x)' from an empty file burnus at gcc dot gnu dot org
2010-03-05 17:02 ` hjl dot tools at gmail dot com
2010-03-05 18:08 ` burnus at gcc dot gnu dot org
2010-03-05 23:07 ` jvdelisle at gcc dot gnu dot org
2010-03-06 1:08 ` jvdelisle at gcc dot gnu dot org
2010-03-06 3:32 ` jvdelisle at gcc dot gnu dot org
2010-03-06 3:37 ` terry at chem dot gu dot se
2010-03-06 3:54 ` jvdelisle at gcc dot gnu dot org
2010-03-06 5:30 ` jvdelisle at gcc dot gnu dot org
2010-03-06 9:49 ` burnus at gcc dot gnu dot org
2010-03-08 20:20 ` jvdelisle at gcc dot gnu dot org
2010-03-09 14:41 ` jvdelisle at gcc dot gnu dot org
2010-03-09 15:36 ` burnus at gcc dot gnu dot org
2010-03-09 20:14 ` jvdelisle at gcc dot gnu dot org
2010-03-10 12:42 ` burnus at gcc dot gnu dot org
2010-03-10 16:27 ` rguenth at gcc dot gnu dot org
2010-03-11 2:27 ` jvdelisle at gcc dot gnu dot org
2010-03-12 14:33 ` jvdelisle at gcc dot gnu dot org [this message]
2010-03-12 14:36 ` jvdelisle at gcc dot gnu dot org
2010-03-18 2:38 ` jvdelisle at gcc dot gnu dot org
2010-03-18 2:43 ` jvdelisle at gcc dot gnu dot org
2010-03-18 2:52 ` jvdelisle at gcc dot gnu dot org
2010-03-18 2:54 ` jvdelisle at gcc dot gnu dot org
2010-03-18 3:52 ` jvdelisle at gcc dot gnu dot org
2010-03-18 3:56 ` jvdelisle at gcc dot gnu dot org
2010-03-18 3:58 ` jvdelisle at gcc dot gnu dot org
2010-03-29 2:50 ` jvdelisle at gcc dot gnu dot org
2010-03-30 3:22 ` jvdelisle at gcc dot gnu dot org
2010-03-30 3:25 ` jvdelisle at gcc dot gnu dot org
2010-03-30 3:54 ` jvdelisle at gcc dot gnu dot org
2010-03-30 3:56 ` jvdelisle at gcc dot gnu dot org
2010-03-30 3:57 ` 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=20100312143252.21280.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).