public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/94034] [10 Regression] Broken diagnostic: 'result_decl' not supported by dump_expr
Date: Thu, 09 Apr 2020 18:41:52 +0000 [thread overview]
Message-ID: <bug-94034-4-pUelLVDEJ8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94034-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94034
--- Comment #7 from Jason Merrill <jason at gcc dot gnu.org> ---
(In reply to Jason Merrill from comment #6)
> So I suppose my comment on Paolo's patch was wrong, and this is only a
> diagnostic quality issue after all.
Ah, there is a constexpr issue to fix: if we add constructors to A, we should
get guaranteed RVO, but still see the same bogus error.
struct A {
A() = default; A(const A&);
A *ap = this;
};
constexpr A foo() { return {}; }
static constexpr A a = foo(); // works without 'constexpr'
int main() {
if (&a != a.ap)
__builtin_abort();
}
next prev parent reply other threads:[~2020-04-09 18:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-94034-4@http.gcc.gnu.org/bugzilla/>
2020-03-20 11:43 ` rguenth at gcc dot gnu.org
2020-03-31 14:44 ` ppalka at gcc dot gnu.org
2020-04-01 14:36 ` paolo.carlini at oracle dot com
2020-04-02 15:29 ` ppalka at gcc dot gnu.org
2020-04-08 16:34 ` ppalka at gcc dot gnu.org
2020-04-09 18:31 ` jason at gcc dot gnu.org
2020-04-09 18:41 ` jason at gcc dot gnu.org [this message]
2020-04-14 15:23 ` cvs-commit at gcc dot gnu.org
2020-04-14 15:24 ` ppalka at gcc dot gnu.org
2021-02-17 1:49 ` cvs-commit at gcc dot gnu.org
2021-02-17 15:01 ` 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-94034-4-pUelLVDEJ8@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).