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] [4.2 only] Last record truncated for read after short write, direct access file
Date: Wed, 18 Apr 2007 04:42:00 -0000	[thread overview]
Message-ID: <20070418044211.28224.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31366-14284@http.gcc.gnu.org/bugzilla/>



------- Comment #17 from jvdelisle at gcc dot gnu dot org  2007-04-18 05:42 -------
Will not fix on 4.1.  Fixed on 4.2 and 4.3


-- 

jvdelisle at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31366


      parent reply	other threads:[~2007-04-18  4:42 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
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 [this message]

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=20070418044211.28224.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).