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/31366] Last record truncated for read after short write, direct access file Date: Sun, 01 Apr 2007 15:24:00 -0000 [thread overview] Message-ID: <20070401152401.8972.qmail@sourceware.org> (raw) In-Reply-To: <bug-31366-14284@http.gcc.gnu.org/bugzilla/> ------- Comment #10 from jvdelisle at gcc dot gnu dot org 2007-04-01 16:24 ------- Subject: Bug 31366 Author: jvdelisle Date: Sun Apr 1 16:23:48 2007 New Revision: 123401 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=123401 Log: 2007-04-01 Jerry DeLisle <jvdelisle@gcc.gnu.org> PR libgfortran/31366 * io/transfer.c (read_block_direct): Do not generate error when reading past EOF on a short record that is less than the RECL= specified. 2007-04-01 Jerry DeLisle <jvdelisle@gcc.gnu.org> PR libgfortran/31207 * io/unit.c (close_unit_1): If there are bytes previously written from ADVANCE="no", move to the end before closing. Modified: trunk/libgfortran/ChangeLog trunk/libgfortran/io/transfer.c trunk/libgfortran/io/unit.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31366
next prev parent reply other threads:[~2007-04-01 15:24 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-03-26 16:27 [Bug fortran/31366] New: When the last record written to a direct access file is shorter than the record length of the file, gfortran truncates the record michael dot a dot richmond at nasa dot gov 2007-03-26 21:18 ` [Bug fortran/31366] " jvdelisle at gcc dot gnu dot org 2007-03-27 19:05 ` tkoenig at gcc dot gnu dot org 2007-03-28 0:53 ` jvdelisle at gcc dot gnu dot org 2007-03-31 0:45 ` [Bug fortran/31366] Last record truncated for read after short write, direct access file jvdelisle at gcc dot gnu dot org 2007-03-31 0:46 ` jvdelisle at gcc dot gnu dot org 2007-03-31 5:06 ` jvdelisle at gcc dot gnu dot org 2007-03-31 7:11 ` tkoenig at alice-dsl dot net 2007-03-31 16:28 ` jvdelisle at gcc dot gnu dot org 2007-04-01 7:11 ` patchapp at dberlin dot org 2007-04-01 15:24 ` jvdelisle at gcc dot gnu dot org [this message] 2007-04-01 15:29 ` jvdelisle at gcc dot gnu dot org 2007-04-01 17:56 ` [Bug fortran/31366] [4.2 only] " jvdelisle at gcc dot gnu dot org 2007-04-17 18:10 ` fxcoudert at gcc dot gnu dot org 2007-04-18 3:00 ` jvdelisle at gcc dot gnu dot org 2007-04-18 4:01 ` jvdelisle at gcc dot gnu dot org 2007-04-18 4:36 ` jvdelisle at gcc dot gnu dot org 2007-04-18 4:37 ` jvdelisle at gcc dot gnu dot org 2007-04-18 4:42 ` 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=20070401152401.8972.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: linkBe 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).