public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pcarlini at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/19422] assoc. containers: ctor taking range is O(n log n) even if the range is sorted
Date: Fri, 14 Jan 2005 14:28:00 -0000	[thread overview]
Message-ID: <20050114142806.25218.qmail@sourceware.org> (raw)
In-Reply-To: <20050113120525.19422.SWElef@post.sk>


------- Additional Comments From pcarlini at suse dot de  2005-01-14 14:28 -------
Yes, we are already using something similar, elsewhere (e.g., our copy_tracker
class). For the present needs, a tweaked version of your test program will do
rather well: even with std::allocator, the new numbers are very stable and much
improved, both in absolute value and as a trend. I will revisit the issue in
the context of 19433, perhaps.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19422


  parent reply	other threads:[~2005-01-14 14:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-13 12:05 [Bug c++/19422] New: " SWElef at post dot sk
2005-01-13 12:08 ` [Bug libstdc++/19422] " SWElef at post dot sk
2005-01-13 12:25 ` pcarlini at suse dot de
2005-01-13 13:05 ` pcarlini at suse dot de
2005-01-13 16:59 ` SWElef at post dot sk
2005-01-13 17:21 ` pcarlini at suse dot de
2005-01-13 17:29 ` pinskia at gcc dot gnu dot org
2005-01-13 17:30 ` pinskia at gcc dot gnu dot org
2005-01-13 17:40 ` pcarlini at suse dot de
2005-01-14  8:25 ` SWElef at post dot sk
2005-01-14 11:50 ` pcarlini at suse dot de
2005-01-14 13:33 ` SWElef at post dot sk
2005-01-14 14:28 ` pcarlini at suse dot de [this message]
2005-01-14 21:09 ` cvs-commit at gcc dot gnu dot org
2005-01-14 22:47 ` pcarlini at suse dot de

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=20050114142806.25218.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).