public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: kw+gnats@cs.cmu.edu
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/4470: Thousands of seeks per read from cin
Date: Thu, 04 Oct 2001 12:56:00 -0000	[thread overview]
Message-ID: <20011004195116.15804.qmail@sourceware.cygnus.com> (raw)

>Number:         4470
>Category:       libstdc++
>Synopsis:       Thousands of seeks per read from cin
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Oct 04 12:56:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Kevin Watkins
>Release:        gcc version 3.0.1
>Organization:
>Environment:
RedHat 7.1 (Linux 2.4.10 i686)
gcc was built from source with ./configure && make && make install
>Description:
The following code:

  #include <iostream>
  int main() {
    char buf[1024];
    while (std::cin.read(buf, 1024));
  }

when compiled thus:

  g++ -static qwe.cc

and run thus:

  ./a.out < /usr/dict/words

generates thousands of seek system calls per read system
call, as revealed by strace.  This is an insurmountable
performance problem.
The problem is specific to cin; it has not been observed
for files opened via the ifstream constructor.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-10-04 12:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-04 12:56 kw+gnats [this message]
2001-10-04 15:49 ljrittle
2002-05-17  3:12 bkoz
2002-05-21 15:16 Kevin Watkins
2002-05-27  2:33 bkoz

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=20011004195116.15804.qmail@sourceware.cygnus.com \
    --to=kw+gnats@cs.cmu.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).