public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: paolo@gcc.gnu.org
To: bkoz@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	peter@snake.iap.physik.tu-darmstadt.de
Subject: Re: libstdc++/6745: Sever io problems on branch rdbuf
Date: Thu, 24 Oct 2002 00:56:00 -0000	[thread overview]
Message-ID: <20021024075612.26909.qmail@sources.redhat.com> (raw)

Synopsis: Sever io problems on branch rdbuf

State-Changed-From-To: closed->analyzed
State-Changed-By: paolo
State-Changed-When: Thu Oct 24 00:56:11 2002
State-Changed-Why:
    After private mail with Benjamin we believe that this PR
    unfortunately must be kept open. In fact, the behaviour of
    v2 is restored but something is still NOT ok in this area.
    Consider the following run time session for the testcase:
    
    paolo~>a.out
    dddd<NEWLINE>
    sssss<NEWLINE>
    <CTRL-D>
    dddd // echoed
    sssss // echoed
    <CTRL-D>
    paolo~>
    
    That is, after a <NEWLINE> no chars are echoed at all. They
    are all output together upon a first <CTRL-D>, then another
    is needed to end program execution.
    Compare to 3.0.4/STLPort/Icc:
    
    paolo~>a.out
    dddd<NEWLINE>
    dddd  // echoed
    sssss<NEWLINE>
    sssss  // echoed
    <CTRL-D>
    paolo~>
    
    Ciao, Paolo.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6745


             reply	other threads:[~2002-10-24  7:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-24  0:56 paolo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-29  1:56 paolo
2002-10-29  8:56 Joe Buck
2002-10-29  5:56 B. Kosnik
2002-10-28 11:16 Joe Buck
2002-10-23 15:03 jbuck
2002-05-29  5:06 bkoz
2002-05-20 14:09 paolo
2002-05-20  9:56 peter

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=20021024075612.26909.qmail@sources.redhat.com \
    --to=paolo@gcc.gnu.org \
    --cc=bkoz@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=peter@snake.iap.physik.tu-darmstadt.de \
    /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).