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++/51965] Redundant move constructions in heap algorithms Date: Mon, 23 Jan 2012 15:40:00 -0000 [thread overview] Message-ID: <bug-51965-4-kDmkRnxJvC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51965-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51965 --- Comment #4 from Paolo Carlini <paolo.carlini at oracle dot com> 2012-01-23 15:26:34 UTC --- Indeed, I double checked that *before* changing the functions to use moves we had plain copies, that is the original HP/SGI functions had copies, nothing was passed by reference. Thus just doing what is suggested is unlikely to be correct.
next prev parent reply other threads:[~2012-01-23 15:27 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-23 13:55 [Bug libstdc++/51965] New: " valyala at gmail dot com 2012-01-23 14:04 ` [Bug libstdc++/51965] " valyala at gmail dot com 2012-01-23 14:10 ` chris at bubblescope dot net 2012-01-23 14:52 ` redi at gcc dot gnu.org 2012-01-23 15:40 ` paolo.carlini at oracle dot com [this message] 2012-01-23 23:46 ` marc.glisse at normalesup dot org 2012-01-24 1:16 ` paolo.carlini at oracle dot com 2012-01-24 11:08 ` marc.glisse at normalesup dot org 2012-01-24 13:04 ` paolo.carlini at oracle dot com 2013-07-25 8:34 ` redi at gcc dot gnu.org 2013-09-06 9:52 ` glisse at gcc dot gnu.org 2014-04-22 11:36 ` jakub at gcc dot gnu.org 2014-07-16 13:28 ` jakub at gcc dot gnu.org 2014-10-30 10:38 ` jakub at gcc dot gnu.org 2015-06-26 20:03 ` jakub at gcc dot gnu.org 2015-06-26 20:30 ` jakub at gcc dot gnu.org 2020-03-29 19:20 ` glisse 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-51965-4-kDmkRnxJvC@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: linkBe 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).