public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/101273] d: missed RVO optimization with non-pod structs
Date: Sat, 03 Jul 2021 11:08:56 +0000	[thread overview]
Message-ID: <bug-101273-4-nXoMONfsjM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101273-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Iain Buclaw <ibuclaw@gcc.gnu.org>:

https://gcc.gnu.org/g:152f4d0e4d3b524ce30d05f20e23a44b0dd29765

commit r12-1995-g152f4d0e4d3b524ce30d05f20e23a44b0dd29765
Author: Iain Buclaw <ibuclaw@gdcproject.org>
Date:   Sat Jul 3 02:42:14 2021 +0200

    d: Missed RVO optimization with non-POD structs

    The D front-end semantic pass sometimes declares a temporary inside a
    return expression.  This is now detected with the RESULT_DECL replacing
    the temporary, allowing for RVO to be done.

            PR d/101273

    gcc/d/ChangeLog:

            * toir.cc (IRVisitor::visit (ReturnStatement *)): Detect returns
that
            use a temporary, and replace with return value.

    gcc/testsuite/ChangeLog:

            * gdc.dg/torture/pr101273.d: New test.

  parent reply	other threads:[~2021-07-03 11:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-30 15:03 [Bug d/101273] New: " ibuclaw at gdcproject dot org
2021-07-01 10:29 ` [Bug d/101273] " ibuclaw at gdcproject dot org
2021-07-03 11:08 ` cvs-commit at gcc dot gnu.org [this message]
2021-07-03 11:09 ` cvs-commit at gcc dot gnu.org
2021-07-03 17:06 ` ibuclaw at gdcproject dot 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-101273-4-nXoMONfsjM@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).