public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/101960] std::tuple with an array element is rejected as a named return type Date: Tue, 12 Oct 2021 15:49:55 +0000 [thread overview] Message-ID: <bug-101960-4-kDpQZ01K3z@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101960-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101960 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:7481021364e75ba583972e15ed421a53988368ea commit r12-4356-g7481021364e75ba583972e15ed421a53988368ea Author: Jonathan Wakely <jwakely@redhat.com> Date: Tue Oct 12 15:09:50 2021 +0100 libstdc++: Fix move construction of std::tuple with array elements [PR101960] The r12-3022 commit only fixed the case where an array is the last element of the tuple. This fixes the other cases too. We can just define the move constructor as defaulted, which does the right thing. Changing the move constructor to be trivial would be an ABI break, but since the last base class still has a non-trivial move constructor, defining the derived ones as defaulted doesn't change anything. libstdc++-v3/ChangeLog: PR libstdc++/101960 * include/std/tuple (_Tuple_impl(_Tuple_impl&&)): Define as defauled. * testsuite/20_util/tuple/cons/101960.cc: Check tuples with array elements before the last element.
next prev parent reply other threads:[~2021-10-12 15:49 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-18 14:01 [Bug libstdc++/101960] New: " wjwray at gmail dot com 2021-08-18 14:26 ` [Bug libstdc++/101960] " redi at gcc dot gnu.org 2021-08-18 14:28 ` redi at gcc dot gnu.org 2021-08-19 12:03 ` cvs-commit at gcc dot gnu.org 2021-08-19 14:09 ` redi at gcc dot gnu.org 2021-09-03 17:02 ` hewillk at gmail dot com 2021-10-12 10:59 ` cvs-commit at gcc dot gnu.org 2021-10-12 15:49 ` cvs-commit at gcc dot gnu.org [this message] 2021-10-12 16:24 ` cvs-commit at gcc dot gnu.org 2021-10-12 17:46 ` 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-101960-4-kDpQZ01K3z@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).