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 10:59:50 +0000 [thread overview]
Message-ID: <bug-101960-4-G1z9S79ZJS@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 #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:
https://gcc.gnu.org/g:00967465fe8093661a4d42356821eeb04170e09d
commit r11-9116-g00967465fe8093661a4d42356821eeb04170e09d
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Thu Aug 19 11:48:40 2021 +0100
libstdc++: Fix move construction of std::tuple with array elements
[PR101960]
An array member cannot be direct-initialized in a ctor-initializer-list,
so use the base class' move constructor, which does the right thing for
both arrays and non-arrays.
This constructor could be defaulted, but that would make it trivial for
some specializations, which would change the argument passing ABI. Do
that for the versioned namespace only.
Signed-off-by: Jonathan Wakely <jwakely@redhat.com>
libstdc++-v3/ChangeLog:
PR libstdc++/101960
* include/std/tuple (_Tuple_impl(_Tuple_impl&&)): Use base
class' move constructor. Define as defaulted for versioned
namespace.
* testsuite/20_util/tuple/cons/101960.cc: New test.
(cherry picked from commit 0187e0d7360f327f88d8b2294668669306ae4630)
next prev parent reply other threads:[~2021-10-12 10:59 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 [this message]
2021-10-12 15:49 ` cvs-commit at gcc dot gnu.org
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-G1z9S79ZJS@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).