public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marc at kdab dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/53637] NRVO not applied in branches when it could be
Date: Wed, 04 Feb 2015 22:28:00 -0000 [thread overview]
Message-ID: <bug-53637-4-lAk14CE6Di@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53637-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53637
marc at kdab dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marc at kdab dot com
--- Comment #1 from marc at kdab dot com ---
Similar situation in
https://codereview.qt-project.org/#/c/104079/1/src/network/ssl/qsslellipticcurve_openssl.cpp,unified
(click on the comment in line 61 to see GCC 4.9.3 (from svn) disassembly.
Qt is full of functions structured like that and it's not an option to rewrite
them all.
Lawrence Crowl calls (N)RVO the most important optimisation in C++, and it's
really sad that GCC doesn't apply NRVO even in those cases where there is only
one possible object returned per basic block, ie. where the compiler knows
which object will be returned by at the time of construction of each object.
It's even more sad that this report has been sitting here, unconfirmed and
ignored by the GCC developers, for 19 months.
next prev parent reply other threads:[~2015-02-04 22:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 19:29 [Bug c++/53637] New: " kenton at google dot com
2015-02-04 22:28 ` marc at kdab dot com [this message]
2015-02-04 22:51 ` [Bug c++/53637] NRVO not applied where there are two different variables involved pinskia at gcc dot gnu.org
2021-12-17 4:45 ` pinskia at gcc dot gnu.org
2023-06-07 22:08 ` cvs-commit 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-53637-4-lAk14CE6Di@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).