From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16244 invoked by alias); 7 Nov 2012 22:03:15 -0000 Received: (qmail 16130 invoked by uid 55); 7 Nov 2012 22:03:01 -0000 From: "frs.dumont at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/54075] [4.7.1] unordered_map insert still slower than 4.6.2 Date: Wed, 07 Nov 2012 22:03:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: frs.dumont at gmail dot com X-Bugzilla-Status: REOPENED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: fdumont at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2012-11/txt/msg00658.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D54075 --- Comment #40 from frs.dumont at gmail dot com 2012-11-07 22:02:56 UTC --- Here is the patch to fix the redundant rehash/reserve issue. 2012-11-07 Fran=C3=A7ois Dumont PR libstdc++/54075 * include/bits/hashtable.h (_Hashtable<>::rehash): Reset hash policy state if no rehash. * testsuite/23_containers/unordered_set/modifiers/reserve.cc (test02): New. I had prepared and tested it in 4.7 branch but I can apply the same on=20 trunk. Ok to commit ? If so, where ? Fran=C3=A7ois On 11/06/2012 10:33 PM, paolo.carlini at oracle dot com wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D54075 > > --- Comment #39 from Paolo Carlini 2012= -11-06 21:33:57 UTC --- > Ok thanks. I guess depending on the complexity of the fixes we can apply = some > only to mainline first and reconsider the 4_7 branch later. Please do you= r best > to work on both issues: we just entered Stage 3 thus no new features from= now > on, we are all concentrated on bug fixes until the release. >