public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/52387] I/O output of write after nonadvancing read
Date: Thu, 01 Mar 2012 01:48:00 -0000	[thread overview]
Message-ID: <bug-52387-4-7ye5ReFPvU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52387-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> 2012-03-01 01:48:23 UTC ---
Are all the cards played here yet?  I assume we won't waste time implementing
any changes until the requirements are clearly understood.  Please ping me when
that point is reached.  There are plenty more important issues then this one
out there.
;)


  parent reply	other threads:[~2012-03-01  1:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-26 10:02 [Bug fortran/52387] New: I/O wrong output with nonadvancing output burnus at gcc dot gnu.org
2012-02-26 10:13 ` [Bug fortran/52387] " burnus at gcc dot gnu.org
2012-02-26 11:12 ` burnus at gcc dot gnu.org
2012-02-26 12:29 ` burnus at gcc dot gnu.org
2012-02-27  9:23 ` burnus at gcc dot gnu.org
2012-02-28 10:15 ` [Bug fortran/52387] I/O output of write after nonadvancing read burnus at gcc dot gnu.org
2012-02-29 13:03 ` burnus at gcc dot gnu.org
2012-02-29 21:13 ` burnus at gcc dot gnu.org
2012-03-01  1:48 ` jvdelisle at gcc dot gnu.org [this message]
2012-03-03  8:10 ` burnus at gcc dot gnu.org
2012-10-28  0:36 ` jvdelisle at gcc dot gnu.org
2014-01-07 14:29 ` dominiq at lps dot ens.fr

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=bug-52387-4-7ye5ReFPvU@http.gcc.gnu.org/bugzilla/ \
    --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).