public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rs2740 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/67200] New: Copy elision and implicit move in return performed in cases not allowed by standard Date: Thu, 13 Aug 2015 05:25:00 -0000 [thread overview] Message-ID: <bug-67200-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67200 Bug ID: 67200 Summary: Copy elision and implicit move in return performed in cases not allowed by standard Product: gcc Version: 6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: rs2740 at gmail dot com Target Milestone: --- Consider: struct A { A() = default; A(const A&) = delete; A(A&&) = default; }; A f() { A a; return true ? a : a; } This code is ill-formed; `true ? a : a` is an lvalue of type `A`; it neither qualifies for copy elision under [class.copy]/p31 (it is not "the name of a nonvolatile automatic object") nor for implicit moving under [class.copy]/p32 (it's not an id-expression, either). Therefore, overload resolution should select the copy constructor, which in the above example is deleted. GCC compiles this code and in fact elides a move.
next reply other threads:[~2015-08-13 5:25 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-08-13 5:25 rs2740 at gmail dot com [this message] 2015-08-13 7:59 ` [Bug c++/67200] " redi 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-67200-4@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: linkBe 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).