public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Edward Maros <emaros@ligo.caltech.edu>
To: paolo@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/5457: Writing to buffer stream writes each byte using a  system write() call.
Date: Tue, 22 Jan 2002 15:46:00 -0000	[thread overview]
Message-ID: <20020122234601.18558.qmail@sources.redhat.com> (raw)

The following reply was made to PR libstdc++/5457; it has been noted by GNATS.

From: Edward Maros <emaros@ligo.caltech.edu>
To: paolo@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
        nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: libstdc++/5457: Writing to buffer stream writes each byte using a 
 system write() call.
Date: Tue, 22 Jan 2002 15:28:06 -0800

 paolo@gcc.gnu.org wrote:
 
 > Synopsis: Writing to buffer stream writes each byte using a system write() call.
 >
 > Responsible-Changed-From-To: unassigned->paolo
 > Responsible-Changed-By: paolo
 > Responsible-Changed-When: Tue Jan 22 14:01:13 2002
 > Responsible-Changed-Why:
 >     Analyzed
 > State-Changed-From-To: open->feedback
 > State-Changed-By: paolo
 > State-Changed-When: Tue Jan 22 14:01:13 2002
 > State-Changed-Why:
 >     Could you please check if your applications benefit from
 >     calling:
 >
 >       std::ios::sync_with_stdio(false);
 >
 >     before any I/O operation??
 >
 >     Thanks,
 >     Paolo.
 >
 >     P.S. For some details on this, see, f.i., Josuttis, pp. 682.
 >
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5457
 
 This does address my issue. Thank you for your help.
 
 Ed
 
 --
 ------
 Edward Maros                            emaros@ligo.caltech.edu
 
 
 


             reply	other threads:[~2002-01-22 23:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-22 15:46 Edward Maros [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-22 15:53 paolo
2002-01-22 14:01 paolo
2002-01-22 13:46 emaros

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=20020122234601.18558.qmail@sources.redhat.com \
    --to=emaros@ligo.caltech.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=paolo@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).