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/31199] write with "t1" + nonadvancing transfer format gives wrong output
Date: Tue, 20 Mar 2007 00:41:00 -0000	[thread overview]
Message-ID: <20070320004126.14079.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31199-6642@http.gcc.gnu.org/bugzilla/>



------- Comment #9 from jvdelisle at gcc dot gnu dot org  2007-03-20 00:41 -------
Reply to comment #8: that was my take on this, that ifort is correct.  It
passed my intuitive sense of it.  Non-advancing means what it says so that the
subsequent write must continue from there and overwrite what was previously
written.  Then,  bytes written already after that are still there and define
the end of the record/line.

Regardless, I am close to a fix.  I will post to list in the next day or so. 


-- 


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


  parent reply	other threads:[~2007-03-20  0:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-16 11:26 [Bug fortran/31199] New: wrong code generated with gfortran jv244 at cam dot ac dot uk
2007-03-16 13:54 ` [Bug fortran/31199] write with "t1" format gives wrong output burnus at gcc dot gnu dot org
2007-03-16 22:57 ` jvdelisle at gcc dot gnu dot org
2007-03-17 16:00 ` jvdelisle at gcc dot gnu dot org
2007-03-19  5:50 ` jvdelisle at gcc dot gnu dot org
2007-03-19 11:12 ` burnus at gcc dot gnu dot org
2007-03-19 12:15 ` dominiq at lps dot ens dot fr
2007-03-19 12:18 ` dominiq at lps dot ens dot fr
2007-03-19 12:53 ` [Bug fortran/31199] write with "t1" + nonadvancing transfer " burnus at gcc dot gnu dot org
2007-03-20  0:41 ` jvdelisle at gcc dot gnu dot org [this message]
2007-03-23 16:20 ` patchapp at dberlin dot org
2007-03-26  3:23 ` jvdelisle at gcc dot gnu dot org
2007-03-26  3:41 ` jvdelisle at gcc dot gnu dot org
2007-03-28  0:48 ` 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=20070320004126.14079.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).