public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "andi-gcc at firstfloor dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/63466] sstream is very slow Date: Mon, 06 Oct 2014 18:13:00 -0000 [thread overview] Message-ID: <bug-63466-4-MQSZk886tT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63466-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63466 --- Comment #2 from Andi Kleen <andi-gcc at firstfloor dot org> --- Looking at the profile there's plenty of room for optimization. e.g. not using getc/ungetc, but directly accessing the buffer, or maybe even some kind of template specialization. With the variables pulled out it's faster, but still a lot slower than C: % time ./a.out < testfile real 0m0.400s user 0m0.397s sys 0m0.002s % time ./tstream-c < testfile real 0m0.033s user 0m0.028s sys 0m0.004s
next prev parent reply other threads:[~2014-10-06 18:13 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-10-06 16:56 [Bug libstdc++/63466] New: " andi-gcc at firstfloor dot org 2014-10-06 17:59 ` [Bug libstdc++/63466] " glisse at gcc dot gnu.org 2014-10-06 18:13 ` andi-gcc at firstfloor dot org [this message] 2014-10-07 10:31 ` redi at gcc dot gnu.org 2014-10-07 10:39 ` redi at gcc dot gnu.org
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=bug-63466-4-MQSZk886tT@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).