public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/61655] Copy constructor not called on CRTP schema
Date: Mon, 30 Jun 2014 07:49:00 -0000	[thread overview]
Message-ID: <bug-61655-4-bmPx9aYG6C@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61655-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61655

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The copy constructor does not need to be called if there is no copying going
on. There is two optimizations going on here. The first is the named return
value optimization. The second is related to that in the intilization of the
new variable is handled inside the function itself.


  parent reply	other threads:[~2014-06-30  7:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-30  7:38 [Bug c++/61655] New: " fabien.picarougne@univ-nantes.fr
2014-06-30  7:46 ` [Bug c++/61655] " glisse at gcc dot gnu.org
2014-06-30  7:49 ` pinskia at gcc dot gnu.org [this message]
2014-06-30  8:17 ` fabien.picarougne@univ-nantes.fr
2014-06-30  8:29 ` 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-61655-4-bmPx9aYG6C@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).