public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jb at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/30162] [4.7/4.8 Regression] Unformatted sequential I/O with named pipes does not work
Date: Thu, 21 Feb 2013 20:40:00 -0000	[thread overview]
Message-ID: <bug-30162-4-5AFk8N7Bkn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-30162-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #54 from Janne Blomqvist <jb at gcc dot gnu.org> 2013-02-21 20:39:58 UTC ---
I'd suggest to close the unformatted sequential part of this PR as WONTFIX.
Maybe it worked sometime in the past for small record sizes when buffered IO
was used for pipes, but that was by accident not by design. I think re-enabling
buffering for pipes would open up a can of worms for very little benefit.

A way to "properly" enable this would be to rework the IO library so that we
know how much we're writing before writing the initial record marker (so that
we don't need to seek back and fill in the correct value later), however that
implies a rather major rework of how we do IO, so IMHO the benefit is not worth
it.


  parent reply	other threads:[~2013-02-21 20:40 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-30162-4@http.gcc.gnu.org/bugzilla/>
2012-08-02 17:34 ` [Bug libfortran/30162] " iliev at rz dot rwth-aachen.de
2012-08-03 19:45 ` jb at gcc dot gnu.org
2012-08-06 13:43 ` burnus at gcc dot gnu.org
2012-10-30 11:37 ` [Bug libfortran/30162] [4.7/4.8 Regression] " burnus at gcc dot gnu.org
2012-11-10 14:38 ` tkoenig at gcc dot gnu.org
2012-11-10 20:22 ` jb at gcc dot gnu.org
2012-11-20 12:19 ` jakub at gcc dot gnu.org
2012-11-24 12:06 ` tkoenig at gcc dot gnu.org
2012-11-25 15:08 ` jb at gcc dot gnu.org
2012-12-14 23:09 ` tkoenig at gcc dot gnu.org
2012-12-15 11:04 ` tkoenig at gcc dot gnu.org
2012-12-21 20:51 ` tkoenig at gcc dot gnu.org
2012-12-22 10:47 ` tkoenig at gcc dot gnu.org
2012-12-22 10:49 ` tkoenig at gcc dot gnu.org
2012-12-22 12:03 ` dominiq at lps dot ens.fr
2012-12-22 15:38 ` tkoenig at netcologne dot de
2012-12-22 19:13 ` dominiq at lps dot ens.fr
2012-12-22 20:16 ` tkoenig at netcologne dot de
2012-12-22 21:23 ` dominiq at lps dot ens.fr
2012-12-22 22:15 ` tkoenig at gcc dot gnu.org
2012-12-23 14:17 ` dominiq at lps dot ens.fr
2012-12-23 15:10 ` tkoenig at netcologne dot de
2012-12-25 15:27 ` tkoenig at gcc dot gnu.org
2013-02-17 20:11 ` [Bug libfortran/30162] [4.7/4.8 Regression] I/O with named pipes does not work on Darwin dominiq at lps dot ens.fr
2013-02-18 18:44 ` tkoenig at gcc dot gnu.org
2013-02-18 19:16 ` dominiq at lps dot ens.fr
2013-02-18 20:17 ` jb at gcc dot gnu.org
2013-02-18 21:25 ` tkoenig at netcologne dot de
2013-02-18 21:29 ` tkoenig at netcologne dot de
2013-02-18 21:47 ` [Bug libfortran/30162] [4.7/4.8 Regression] Unformatted sequential I/O with named pipes does not work tkoenig at gcc dot gnu.org
2013-02-19 10:59 ` jb at gcc dot gnu.org
2013-02-19 22:49 ` jb at gcc dot gnu.org
2013-02-21 19:03 ` jb at gcc dot gnu.org
2013-02-21 20:13 ` jb at gcc dot gnu.org
2013-02-21 20:40 ` jb at gcc dot gnu.org [this message]
2013-02-22  8:54 ` burnus at gcc dot gnu.org
2013-04-11  7:58 ` [Bug libfortran/30162] [4.7/4.8/4.9 " rguenth at gcc dot gnu.org
2013-08-09  9:25 ` [Bug libfortran/30162] Document when sequential I/O with named pipes works tkoenig at gcc dot gnu.org
2015-02-01 13:20 ` jvdelisle at gcc dot gnu.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=bug-30162-4-5AFk8N7Bkn@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).