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


>Number:         5457
>Category:       libstdc++
>Synopsis:       Writing to buffer stream writes each byte using a system write() call.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          pessimizes-code
>Submitter-Id:   net
>Arrival-Date:   Tue Jan 22 13:46:05 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     emaros@ligo.caltech.edu
>Release:        gcc-3.0.3
>Organization:
>Environment:
RedHat 7.2 Linux/Intel
Reading specs from /ldcg/lib/gcc-lib/i686-pc-linux-gnu/3.0.3/specs
Configured with: ../configure --prefix=/ldcg --with-prefix=/ldcg --enable-long-long
Thread model: single
gcc version 3.0.3
>Description:
When writing to cout, each character is being written via
the system write() call.Ouput of strace:

...
fstat64(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 7), ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40206000
ioctl(1, TCGETS, {B38400 opost isig icanon echo ...}) = 0
write(1, "H", 1H)                        = 1
write(1, "e", 1e)                        = 1
write(1, "l", 1l)                        = 1
write(1, "l", 1l)                        = 1
write(1, "o", 1o)                        = 1
write(1, " ", 1 )                        = 1
write(1, "W", 1W)                        = 1
write(1, "o", 1o)                        = 1
write(1, "r", 1r)                        = 1
write(1, "l", 1l)                        = 1
write(1, "d", 1d)                        = 1
write(1, "!", 1!)                        = 1
write(1, "\n", 1
)                       = 1
munmap(0x40206000, 4096)                = 0
_exit(0)                                = ?
>How-To-Repeat:
g++ t.cc
strace ./a.out
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="t.cc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="t.cc"

I2luY2x1ZGUgPGlvc3RyZWFtPgoKaW50Cm1haW4oKQp7CglzdGQ6OmNvdXQgPDwgIkhlbGxvIFdv
cmxkISIgPDwgc3RkOjplbmRsOwp9Cg==


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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-22 13:46 emaros [this message]
2002-01-22 14:01 paolo
2002-01-22 15:46 Edward Maros
2002-01-22 15:53 paolo

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=20020122214500.1326.qmail@sources.redhat.com \
    --to=emaros@ligo.caltech.edu \
    --cc=gcc-gnats@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).