public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "andrewjcg at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/56493] New: Performance regression in google dense hashmap Date: Fri, 01 Mar 2013 13:10:00 -0000 [thread overview] Message-ID: <bug-56493-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56493 Bug #: 56493 Summary: Performance regression in google dense hashmap Classification: Unclassified Product: gcc Version: 4.7.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: andrewjcg@gmail.com When compared to gcc-4.6.2, gcc-4.7.1 shows about a 10-20% performance regression when inserting into a google dense hashmap in a tight loop. A small sample program is attached and was compiled with '-O3' and on a linux x86_64 box (using -std=gnu++0x, as required by sparsehash). Potentially related, the generated binary under gcc-4.7 is also over 50% bigger.
next reply other threads:[~2013-03-01 13:10 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-01 13:10 andrewjcg at gmail dot com [this message] 2013-03-01 13:12 ` [Bug c++/56493] " andrewjcg at gmail dot com 2013-03-01 13:13 ` andrewjcg at gmail dot com 2013-03-01 14:29 ` redi at gcc dot gnu.org 2013-03-01 22:09 ` andrewjcg at gmail dot com 2013-03-01 22:11 ` andrewjcg at gmail dot com 2013-03-02 0:57 ` redi at gcc dot gnu.org 2013-03-09 4:18 ` andrewjcg at gmail dot com 2013-03-09 10:57 ` redi at gcc dot gnu.org 2013-04-13 1:37 ` cberner at fb dot com 2013-04-13 1:44 ` andrewjcg at gmail dot com 2013-06-15 7:12 ` jakub at gcc dot gnu.org 2013-06-16 0:03 ` jim at meyering dot net 2013-06-16 10:25 ` jakub at gcc dot gnu.org 2014-12-03 9:40 ` ubizjak at gmail dot com 2014-12-03 9:56 ` [Bug c++/56493] [4.8/4.9/5 Regression] " jakub at gcc dot gnu.org 2014-12-03 10:13 ` rguenth at gcc dot gnu.org 2014-12-03 10:20 ` rguenth at gcc dot gnu.org 2014-12-03 10:21 ` rguenth at gcc dot gnu.org 2014-12-03 10:34 ` jakub at gcc dot gnu.org 2014-12-03 11:26 ` rguenth at gcc dot gnu.org 2014-12-04 9:47 ` jakub at gcc dot gnu.org 2014-12-04 9:48 ` jakub at gcc dot gnu.org 2014-12-04 9:49 ` jakub at gcc dot gnu.org 2014-12-10 12:34 ` rguenth 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-56493-4@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).