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++/96029] [8/9 Regression] Inconsistencies with associative/unordered containers
Date: Thu, 08 Apr 2021 23:37:43 +0000 [thread overview]
Message-ID: <bug-96029-4-ayOzYucGb4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96029-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96029
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:
https://gcc.gnu.org/g:1228154b8726a3bc903f1967f9b3aac8fd192e46
commit r9-9327-g1228154b8726a3bc903f1967f9b3aac8fd192e46
Author: François Dumont <fdumont@gcc.gnu.org>
Date: Fri Jul 3 08:13:19 2020 +0200
libstdc++: Fix [multi]map/[multi]set move constructors noexcept
qualification
Container move constructors shall not consider their allocator move
constructor qualification.
For the backport to gcc-9 the _Rb_tree_impl move constructor must be
user-provided, because prior to the implementation of P1286R2 in
r10-4094, a defaulted special member with a different exception would be
deleted.
libstdc++-v3/ChangeLog:
PR libstdc++/96029
* include/bits/stl_tree.h (_Rb_tree_impl(_Rb_tree_impl&&)): Add
noexcept
qualification based only on _Compare one.
* testsuite/23_containers/map/cons/noexcept_move_construct.cc: Add
static asserts.
* testsuite/23_containers/multimap/cons/noexcept_move_construct.cc:
Likewise.
* testsuite/23_containers/multiset/cons/noexcept_move_construct.cc:
Likewise.
* testsuite/23_containers/set/cons/noexcept_move_construct.cc:
Likewise.
(cherry picked from commit c832cf1c1d114aed70c2f84566cf4d63de0a56d0)
next prev parent reply other threads:[~2021-04-08 23:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 11:38 [Bug libstdc++/96029] New: " nknikita at niisi dot ras.ru
2020-07-02 12:44 ` [Bug libstdc++/96029] [8/9/10/11 Regression] " redi at gcc dot gnu.org
2020-07-02 13:24 ` rguenth at gcc dot gnu.org
2020-10-12 12:50 ` rguenth at gcc dot gnu.org
2021-04-08 14:35 ` [Bug libstdc++/96029] [8/9/10 " redi at gcc dot gnu.org
2021-04-08 17:00 ` cvs-commit at gcc dot gnu.org
2021-04-08 17:00 ` cvs-commit at gcc dot gnu.org
2021-04-08 17:43 ` [Bug libstdc++/96029] [8/9 " redi at gcc dot gnu.org
2021-04-08 23:37 ` cvs-commit at gcc dot gnu.org [this message]
2021-04-08 23:37 ` cvs-commit at gcc dot gnu.org
2021-04-08 23:38 ` [Bug libstdc++/96029] [8 " redi at gcc dot gnu.org
2021-04-09 14:04 ` vvinayag at arm dot com
2021-04-09 14:22 ` redi at gcc dot gnu.org
2021-05-14 13:58 ` jakub 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-96029-4-ayOzYucGb4@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).