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:48 +0000 [thread overview]
Message-ID: <bug-96029-4-y9w6di1QiO@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 #7 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:5f63261c3e54995b45dd411ad76526870c4b8be3
commit r9-9328-g5f63261c3e54995b45dd411ad76526870c4b8be3
Author: François Dumont <fdumont@gcc.gnu.org>
Date: Mon Jan 20 19:15:43 2020 +0100
libstdc++: Fix unordered containers move constructors noexcept
qualification
_Hashtable move constructor is wrongly qualified as noexcept(true)
regardless of
_Equal and _H1 copy constructor qualifications.
_Hashtable allocator-aware move constructor is missing its noexcept
qualification like the depending unordered containers ones.
This backport also includes the changes from r11-8062 and r11-2438.
libstdc++-v3/ChangeLog:
PR libstdc++/96029
* include/bits/hashtable.h
(_Hashtable(_Hashtable&& __ht, __node_alloc_type&& __a,
true_type)):
Add noexcept qualification.
(_Hashtable(_Hashtable&&)): Fix noexcept qualification.
(_Hashtable(_Hashtable&&, const allocator_type&)): Add noexcept
qualification.
* include/bits/unordered_map.h
(unordered_map(unordered_map&&, const allocator_type&)): Add
noexcept
qualification.
(unordered_multimap(unordered_multimap&&, const allocator_type&)):
Likewise.
* include/bits/unordered_set.h
(unordered_set(unordered_set&&, const allocator_type&)): Likewise.
(unordered_multiset(unordered_multiset&&, const allocator_type&)):
Likewise.
* include/debug/unordered_map
(unordered_map(unordered_map&&, const allocator_type&)): Likewise.
(unordered_multimap(unordered_multimap&&, const allocator_type&)):
Likewise.
* include/debug/unordered_set
(unordered_set(unordered_set&&, const allocator_type&)): Likewise.
(unordered_multiset(unordered_multiset&&, const allocator_type&)):
Likewise.
* testsuite/23_containers/unordered_map/allocator/default_init.cc:
New test.
*
testsuite/23_containers/unordered_map/cons/noexcept_default_construct.cc:
New test.
*
testsuite/23_containers/unordered_map/cons/noexcept_move_construct.cc:
New test.
* testsuite/23_containers/unordered_map/modifiers/move_assign.cc:
New test.
*
testsuite/23_containers/unordered_multimap/cons/noexcept_default_construct.cc:
New test.
*
testsuite/23_containers/unordered_multimap/cons/noexcept_move_construct.cc:
New test.
*
testsuite/23_containers/unordered_multiset/cons/noexcept_default_construct.cc:
New test.
*
testsuite/23_containers/unordered_multiset/cons/noexcept_move_construct.cc:
New test.
* testsuite/23_containers/unordered_set/allocator/default_init.cc:
New test.
*
testsuite/23_containers/unordered_set/cons/noexcept_default_construct.cc:
New test.
*
testsuite/23_containers/unordered_set/cons/noexcept_move_construct.cc:
New test.
(cherry picked from commit 12324b9a934654a5c3bf4a614853ded2e0a958af)
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
2021-04-08 23:37 ` cvs-commit at gcc dot gnu.org [this message]
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-y9w6di1QiO@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).