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++/108952] [10/11 Regression] Regression in uses_allocator_construction_args for pair of rvalue references Date: Thu, 27 Apr 2023 22:01:02 +0000 [thread overview] Message-ID: <bug-108952-4-C2nWoglTGG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108952-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108952 --- Comment #11 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:6930165acd05c8eef88a99b9546742b108e0c84e commit r11-10656-g6930165acd05c8eef88a99b9546742b108e0c84e Author: Jonathan Wakely <jwakely@redhat.com> Date: Mon Feb 27 22:34:57 2023 +0000 libstdc++: Fix uses_allocator_construction_args for pair<T&&, U&&> [PR108952] This implements LWG 3527 which fixes the handling of pair<T&&, U&&> in std::uses_allocator_construction_args. libstdc++-v3/ChangeLog: PR libstdc++/108952 * include/bits/uses_allocator_args.h (uses_allocator_construction_args): Implement LWG 3527. * testsuite/20_util/pair/astuple/get-2.cc: New test. * testsuite/20_util/scoped_allocator/108952.cc: New test. * testsuite/20_util/uses_allocator/lwg3527.cc: New test. (cherry picked from commit 8e342c04550466ab088c33746091ce7f3498ee44)
next prev parent reply other threads:[~2023-04-27 22:01 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-27 16:14 [Bug libstdc++/108952] New: " christian.mazakas at gmail dot com 2023-02-27 16:15 ` [Bug libstdc++/108952] " pinskia at gcc dot gnu.org 2023-02-27 17:03 ` redi at gcc dot gnu.org 2023-02-27 17:18 ` rs2740 at gmail dot com 2023-02-27 17:33 ` pdimov at gmail dot com 2023-02-27 17:34 ` redi at gcc dot gnu.org 2023-02-27 21:27 ` [Bug libstdc++/108952] [10/11/12/13 Regression] " redi at gcc dot gnu.org 2023-02-28 9:50 ` cvs-commit at gcc dot gnu.org 2023-02-28 9:53 ` [Bug libstdc++/108952] [10/11/12 " redi at gcc dot gnu.org 2023-02-28 10:40 ` rguenth at gcc dot gnu.org 2023-04-27 14:44 ` cvs-commit at gcc dot gnu.org 2023-04-27 14:52 ` [Bug libstdc++/108952] [10/11 " redi at gcc dot gnu.org 2023-04-27 22:01 ` cvs-commit at gcc dot gnu.org [this message] 2023-04-27 23:04 ` cvs-commit at gcc dot gnu.org 2023-04-27 23:05 ` 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-108952-4-C2nWoglTGG@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).