public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fchelnokov at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/104282] New: Copy elision when initializing a base-class subobject with aggregate initialization Date: Sat, 29 Jan 2022 13:10:20 +0000 [thread overview] Message-ID: <bug-104282-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104282 Bug ID: 104282 Summary: Copy elision when initializing a base-class subobject with aggregate initialization Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: fchelnokov at gmail dot com Target Milestone: --- The program ``` #include <iostream> struct A { A() { std::cout << "A "; } A(const A&) { std::cout << "Acopy "; } A(A&&) { std::cout << "Amove "; } ~A() { std::cout << "~A "; } }; struct B : A { }; int main() { B b{ A{} }; } ``` if compiled by GCC, prints `A ~A `, showing that there is no copy/move of the temporary `A{}`. Clang prints on the other hand `A Amove ~A ~A `, which looks correct, because of "no elision when initializing a base-class subobject", see https://en.cppreference.com/w/cpp/language/copy_elision Demo: https://gcc.godbolt.org/z/rafEsTdd9
next reply other threads:[~2022-01-29 13:10 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-29 13:10 fchelnokov at gmail dot com [this message] 2022-01-29 17:11 ` [Bug c++/104282] " pinskia at gcc dot gnu.org 2022-01-29 17:12 ` pinskia at gcc dot gnu.org 2022-01-29 17:15 ` fchelnokov at gmail dot com 2022-01-29 19:26 ` redi at gcc dot gnu.org 2022-01-29 19:29 ` redi at gcc dot gnu.org 2022-01-29 23:34 ` pinskia at gcc dot gnu.org 2023-01-16 4:23 ` pinskia at gcc dot gnu.org 2024-03-22 7:52 ` fchelnokov at gmail dot com
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-104282-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).