public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo dot carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/41975] [C++0x] [DR579] unordered_set::erase performs worse when nearly empty
Date: Tue, 22 Dec 2009 10:02:00 -0000 [thread overview]
Message-ID: <20091222100209.7645.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41975-11470@http.gcc.gnu.org/bugzilla/>
------- Comment #11 from paolo dot carlini at oracle dot com 2009-12-22 10:02 -------
Relevant DR reopened:
http://home.roadrunner.com/~hinnant/issue_review/lwg-active.html#579
Next, we should provide detailed wording...
--
paolo dot carlini at oracle dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |SUSPENDED
Summary|[C++0x] unordered_set::erase|[C++0x] [DR579]
|performs worse when nearly |unordered_set::erase
|empty |performs worse when nearly
| |empty
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41975
next prev parent reply other threads:[~2009-12-22 10:02 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 20:53 [Bug libstdc++/41975] New: " sjackman at gmail dot com
2009-11-06 21:36 ` [Bug libstdc++/41975] " paolo dot carlini at oracle dot com
2009-11-06 23:44 ` sjackman at gmail dot com
2009-11-06 23:50 ` paolo dot carlini at oracle dot com
2009-11-07 0:07 ` sjackman at gmail dot com
2009-11-07 1:17 ` paolo dot carlini at oracle dot com
2009-11-28 22:59 ` jzwinck at gmail dot com
2009-11-28 23:16 ` rguenth at gcc dot gnu dot org
2009-11-29 0:44 ` sjackman at gmail dot com
2009-11-29 2:29 ` sstrasser at systemhaus-gruppe dot de
2009-11-29 8:34 ` paolo dot carlini at oracle dot com
2009-12-22 10:02 ` paolo dot carlini at oracle dot com [this message]
2010-02-09 16:09 ` [Bug libstdc++/41975] [C++0x] [DR579] " paolo dot carlini at oracle dot com
2010-02-11 15:54 ` paolo dot carlini at oracle dot com
2010-02-11 18:11 ` paolo at gcc dot gnu dot org
2010-02-11 18:13 ` paolo dot carlini at oracle dot com
2010-03-09 1:57 ` paolo at gcc dot gnu dot org
2010-03-09 1:59 ` paolo dot carlini at oracle dot com
2010-03-09 18:40 ` jzwinck at gmail dot com
2010-03-09 18:49 ` paolo dot carlini at oracle dot com
2010-03-09 19:15 ` sjackman at gmail dot com
2010-03-09 19:19 ` paolo dot carlini at oracle dot com
2010-03-09 19:21 ` paolo dot carlini at oracle dot com
2010-03-09 19:56 ` jzwinck at gmail dot com
2010-03-09 20:15 ` paolo dot carlini at oracle dot com
2010-03-10 16:36 ` paolo dot carlini at oracle dot com
2010-04-06 11:25 ` rguenth at gcc dot gnu dot org
2010-07-31 9:33 ` rguenth at gcc dot gnu dot org
2010-08-08 15:03 ` paolo dot carlini at oracle dot com
2010-09-20 17:23 ` paolo dot carlini at oracle dot com
2010-09-20 17:34 ` joaquin at tid dot es
2010-09-20 17:41 ` paolo dot carlini at oracle dot com
2010-09-21 17:55 ` paolo dot carlini at oracle dot com
[not found] <bug-41975-4@http.gcc.gnu.org/bugzilla/>
2010-10-06 11:10 ` joaquin at tid dot es
2010-12-16 13:22 ` rguenth at gcc dot gnu.org
2011-11-23 21:17 ` fdumont at gcc dot gnu.org
2011-11-28 22:32 ` paolo.carlini at oracle dot com
2012-07-24 21:46 ` andrewjcg at gmail dot com
2012-07-24 21:51 ` 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=20091222100209.7645.qmail@sourceware.org \
--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: link
Be 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).