public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Paolo Carlini <pcarlini@unitus.it> To: bkoz@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: libstdc++/2211 Date: Wed, 27 Jun 2001 14:36:00 -0000 [thread overview] Message-ID: <20010627213603.32586.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR libstdc++/2211; it has been noted by GNATS. From: Paolo Carlini <pcarlini@unitus.it> To: bkoz@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org, Theodore.Papadopoulo@sophia.inria.fr Cc: Subject: Re: libstdc++/2211 Date: Wed, 27 Jun 2001 23:27:51 +0200 Hi all, Benjamin, I have just read your reply concerning the use of std::ios::sync_with_stdio(false). Therefore I tried my favorite test, that is a short program from the 2nd Ed. of Programming Pearls by Jon Bentley: ----------- /* Copyright (C) 1999 Lucent Technologies */ /* From 'Programming Pearls' by Jon Bentley */ /* wordlist.cpp -- Sorted list of words (between white space) in file */ #include <iostream> #include <set> #include <string> using namespace std; int main() { set<string> S; string t; set<string>::iterator j; while (cin >> t) S.insert(t); for (j = S.begin(); j != S.end(); ++j) cout << *j << "\n"; return 0; } ------------ On my Linux-x86 box, I don't see significant speed differences bring about by std::ios::sync_with_stdio(false). Indeed, I always see a significant run time regression vs libstdc++v2 (between 2x and 3x, unfortunately) when processing a long test file (usually I use electronic version of "The King James Bible", 4445260 chars, for this purpose) http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2211&database=gcc
reply other threads:[~2001-06-27 14: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=20010627213603.32586.qmail@sourceware.cygnus.com \ --to=pcarlini@unitus.it \ --cc=bkoz@gcc.gnu.org \ --cc=gcc-prs@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).