From: Marc Glisse <marc.glisse@inria.fr>
To: "Henrik Mannerström" <henrik.mannerstrom@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: RVO (let the compiler copy)
Date: Thu, 19 Dec 2013 10:41:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.10.1312191139310.3784@laptop-mg.saclay.inria.fr> (raw)
In-Reply-To: <52B2AED7.9090203@gmail.com>
On Thu, 19 Dec 2013, Henrik Mannerström wrote:
> This question came up on SO (
> http://stackoverflow.com/questions/7320520/optimizing-the-number-of-constructor-calls)
> and I was baffled since it went against the mantra "let the compiler do
> the copying". Do you have an idea of what is going on? Why is the
> commented version of operator+ worse?
See:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57176
--
Marc Glisse
next prev parent reply other threads:[~2013-12-19 10:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 8:31 Henrik Mannerström
2013-12-19 10:41 ` Marc Glisse [this message]
2013-12-19 10:50 ` Henrik Mannerström
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=alpine.DEB.2.10.1312191139310.3784@laptop-mg.saclay.inria.fr \
--to=marc.glisse@inria.fr \
--cc=gcc-help@gcc.gnu.org \
--cc=henrik.mannerstrom@gmail.com \
/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).