public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/52822] [C++11] stable_partition destroys sequence due to inappropriate self-move-assignment
Date: Sun, 01 Apr 2012 22:10:00 -0000	[thread overview]
Message-ID: <bug-52822-4-lBw04i6t9f@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52822-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Paolo Carlini <paolo.carlini at oracle dot com> 2012-04-01 22:09:45 UTC ---
PS: then shall we just do the assignment only when __result1 != __first, or
algorithmically we can do better? In case we can also imagine having the
trivial fix for 4.6 and maybe even 4.7.1 and committing it to mainline too
without considering the issue resolved, in case later on somebody figures out
something smarter algorithmically.


  parent reply	other threads:[~2012-04-01 22:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-01 18:51 [Bug libstdc++/52822] New: " jyasskin at gcc dot gnu.org
2012-04-01 20:42 ` [Bug libstdc++/52822] " jyasskin at gcc dot gnu.org
2012-04-01 21:15 ` redi at gcc dot gnu.org
2012-04-01 21:51 ` paolo.carlini at oracle dot com
2012-04-01 22:10 ` paolo.carlini at oracle dot com [this message]
2012-04-02  2:15 ` jyasskin at gcc dot gnu.org
2012-04-02  9:10 ` paolo.carlini at oracle dot com
2012-04-02 16:41 ` jyasskin at gcc dot gnu.org
2012-04-12 12:21 ` paolo.carlini at oracle dot com
2012-04-12 20:59 ` jyasskin at gcc dot gnu.org
2012-04-12 21:42 ` jyasskin at gcc dot gnu.org
2012-04-12 22:26 ` jyasskin at gcc dot gnu.org
2012-04-12 22:30 ` jyasskin 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-52822-4-lBw04i6t9f@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).