public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ibuclaw at gdcproject dot 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: Thu, 01 Jul 2021 10:29:50 +0000 [thread overview]
Message-ID: <bug-101273-4-DBRz7Z2Zy6@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 #1 from Iain Buclaw <ibuclaw at gdcproject dot org> ---
(In reply to Iain Buclaw from comment #0)
> It looks like fixing PR d/100882 introduced a small regression:
On further inspection, this is not the case. The front-end semantic pass
returns us code that uses an intermediate temporary. i.e:
return __ctor((S tmp = S(), &tmp), 42);
The code generator in D just doesn't detect this pattern and replace `tmp' with
the DECL_RESULT variable to give us a more desired representation:
S tmp [value-expr: <retval>];
__ctor(<retval> = S(), &<retval>, 42);
return <retval>;
next prev parent reply other threads:[~2021-07-01 10:29 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 ` ibuclaw at gdcproject dot org [this message]
2021-07-03 11:08 ` [Bug d/101273] " cvs-commit at gcc dot gnu.org
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-DBRz7Z2Zy6@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).