public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pluto at agmk dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/46659] std::list iterator debugging (_GLIBCXX_DEBUG) is much slower than stlport's one. Date: Tue, 07 Dec 2010 22:19:00 -0000 [thread overview] Message-ID: <bug-46659-4-tXSxz2IYv2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46659-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46659 Pawel Sikora <pluto at agmk dot net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED --- Comment #8 from Pawel Sikora <pluto at agmk dot net> 2010-12-07 22:19:39 UTC --- here're the results for current git: 54486c25c3df3bdb314929fe30855f0d3bd2e0b5 200000 elements: $ time ./t-libstdcxx ./t-libstdcxx 0,09s user 0,01s system 98% cpu 0,109 total $ time ./t-stlport ./t-stlport 170,91s user 0,01s system 99% cpu 2:50,93 total 100000 elements: $ time ./t-libstdcxx ./t-libstdcxx 0,05s user 0,00s system 95% cpu 0,056 total $ time ./t-stlport ./t-stlport 31,59s user 0,02s system 99% cpu 31,622 total 50000 elements: $ time ./t-libstdcxx ./t-libstdcxx 0,02s user 0,00s system 93% cpu 0,029 total $ time ./t-stlport ./t-stlport 7,28s user 0,00s system 99% cpu 7,287 total so... it's fixed.
next prev parent reply other threads:[~2010-12-07 22:19 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-25 15:34 [Bug libstdc++/46659] New: " pluto at agmk dot net 2010-11-25 15:59 ` [Bug libstdc++/46659] " redi at gcc dot gnu.org 2010-11-25 17:06 ` paolo.carlini at oracle dot com 2010-11-25 19:48 ` pluto at agmk dot net 2010-12-07 11:06 ` paolo.carlini at oracle dot com 2010-12-07 21:40 ` redi at gcc dot gnu.org 2010-12-07 22:05 ` pluto at agmk dot net 2010-12-07 22:10 ` paolo.carlini at oracle dot com 2010-12-07 22:19 ` pluto at agmk dot net [this message] 2010-12-07 22:30 ` paolo.carlini at oracle dot com 2010-12-09 21:05 ` fdumont 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-46659-4-tXSxz2IYv2@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).