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++/114147] [11/12/13/14 Regression] tuple allocator-extended constructor requires non-explicit default constructor Date: Mon, 04 Mar 2024 20:25:28 +0000 [thread overview] Message-ID: <bug-114147-4-wGSQBmbJwu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114147-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114147 --- Comment #8 from GCC 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:0a545ac7000501844670add0b3560ebdbcb123c6 commit r14-9307-g0a545ac7000501844670add0b3560ebdbcb123c6 Author: Jonathan Wakely <jwakely@redhat.com> Date: Fri Mar 1 11:16:58 2024 +0000 libstdc++: Add missing std::tuple constructor [PR114147] I caused a regression with commit r10-908 by adding a constraint to the non-explicit allocator-extended default constructor, but seemingly forgot to add an explicit overload with the corresponding constraint. libstdc++-v3/ChangeLog: PR libstdc++/114147 * include/std/tuple (tuple::tuple(allocator_arg_t, const Alloc&)): Add missing overload of allocator-extended default constructor. (tuple<T1,T2>::tuple(allocator_arg_t, const Alloc&)): Likewise. * testsuite/20_util/tuple/cons/114147.cc: New test.
next prev parent reply other threads:[~2024-03-04 20:25 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-28 10:39 [Bug libstdc++/114147] New: " victor.dyachenko at protonmail dot com 2024-02-28 10:48 ` [Bug libstdc++/114147] " victor.dyachenko at protonmail dot com 2024-02-28 11:18 ` victor.dyachenko at protonmail dot com 2024-02-28 11:21 ` [Bug libstdc++/114147] [10/11/12/13 Regression] " redi at gcc dot gnu.org 2024-02-28 13:49 ` [Bug libstdc++/114147] [11/12/13 " victor.dyachenko at protonmail dot com 2024-02-28 14:31 ` [Bug libstdc++/114147] [11/12/13/14 " redi at gcc dot gnu.org 2024-02-29 20:38 ` redi at gcc dot gnu.org 2024-03-01 15:12 ` redi at gcc dot gnu.org 2024-03-04 20:25 ` cvs-commit at gcc dot gnu.org [this message] 2024-03-16 10:19 ` [Bug libstdc++/114147] [11/12/13 " cvs-commit at gcc dot gnu.org 2024-03-18 14:03 ` [Bug libstdc++/114147] [11/12 " cvs-commit at gcc dot gnu.org 2024-03-18 14:14 ` [Bug libstdc++/114147] [11 " redi at gcc dot gnu.org 2024-05-02 10:53 ` cvs-commit at gcc dot gnu.org 2024-05-02 10:54 ` 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-114147-4-wGSQBmbJwu@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).