public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "chris at bubblescope dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/57916] Improve std::sort partitioning by explicitly employing the pivot
Date: Wed, 25 Sep 2013 12:43:00 -0000	[thread overview]
Message-ID: <bug-57916-4-S8sYtACc5W@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57916-4@http.gcc.gnu.org/bugzilla/>

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

Chris Jefferson <chris at bubblescope dot net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |chris at bubblescope dot net

--- Comment #5 from Chris Jefferson <chris at bubblescope dot net> ---
I have not carefully analysed this, but it might be worth changing the names of
methods you change if interaction between the old and new methods could break
std::sort, as when code compiled using different versions of the library is
linked, the linker will choose one version of each function at random.

As I say, I haven't looked carefully enough to see if this is a real problem
(sorry).


      parent reply	other threads:[~2013-09-25 12:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-17  2:43 [Bug libstdc++/57916] New: Improve std::sort paritioning " alexey.tourbin at gmail dot com
2013-07-17  9:22 ` [Bug libstdc++/57916] " redi at gcc dot gnu.org
2013-07-18  1:25 ` alexey.tourbin at gmail dot com
2013-07-21 19:40 ` [Bug libstdc++/57916] Improve std::sort partitioning " paolo.carlini at oracle dot com
2013-07-26 12:08 ` paolo.carlini at oracle dot com
2013-09-25 12:43 ` chris at bubblescope dot net [this message]

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-57916-4-S8sYtACc5W@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: 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).