public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Pal Benko <benko@sztaki.hu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: libstdc++/5799: streams reading from fifo (regression???) Date: Wed, 13 Mar 2002 00:36:00 -0000 [thread overview] Message-ID: <20020313083602.14019.qmail@sources.redhat.com> (raw) The following reply was made to PR libstdc++/5799; it has been noted by GNATS. From: Pal Benko <benko@sztaki.hu> To: rodrigc@gcc.gnu.org, benko@sztaki.hu, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: libstdc++/5799: streams reading from fifo (regression???) Date: Wed, 13 Mar 2002 09:28:30 +0100 Please re-open the bugreport. Yours is certainly a better test case. Perhaps it's unfair to call it a regression, but the fact is that compiling with 2.95.3 (with the old libstdc++) gets this right. The problem is that if I read from a named pipe through an ifstream, I can read only when the buffer is full or the pipe is closed, but cannot read when the pipe is just flushed on the writing side. Regards, Pal Benko
reply other threads:[~2002-03-13 8:36 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020313083602.14019.qmail@sources.redhat.com \ --to=benko@sztaki.hu \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).