public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/56267] [4.7/4.8/4.9 Regression] unordered containers require Assignable hash function
Date: Mon, 20 Jan 2014 15:50:00 -0000 [thread overview]
Message-ID: <bug-56267-4-Df1nRsg0H0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56267-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56267
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Mon Jan 20 15:49:39 2014
New Revision: 206834
URL: http://gcc.gnu.org/viewcvs?rev=206834&root=gcc&view=rev
Log:
PR libstdc++/56267
* include/bits/hashtable_policy.h (_Hash_code_base<... false>): Grant
friendship to _Local_iterator_base<..., false>.
(_Local_iterator_base): Give protected access to all existing members.
(_Local_iterator_base::_M_curr()): New public accessor.
(_Local_iterator_base::_M_get_bucket()): New public accessor.
(_Local_iterator_base<..., false>::_M_init()): New function to manage
the lifetime of the _Hash_code_base explicitly.
(_Local_iterator_base<..., false>::_M_destroy()): Likewise.
(_Local_iterator_base<..., false>): Define copy constructor and copy
assignment operator that use new functions to manage _Hash_code_base.
(operator==(const _Local_iterator_base&, const _Local_iterator_base&),
operator==(const _Local_iterator_base&, const _Local_iterator_base&)):
Use public API for _Local_iterator_base.
* include/debug/safe_local_iterator.h (_Safe_local_iterator): Likewise.
* include/debug/unordered_map (__debug::unordered_map::erase(),
__debug::unordered_multimap::erase()): Likewise.
* include/debug/unordered_set (__debug::unordered_set::erase(),
__debug::unordered_multiset::erase()): Likewise.
* testsuite/23_containers/unordered_set/56267-2.cc: New test.
Added:
trunk/libstdc++-v3/testsuite/23_containers/unordered_set/56267-2.cc
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/include/bits/hashtable_policy.h
trunk/libstdc++-v3/include/debug/safe_local_iterator.h
trunk/libstdc++-v3/include/debug/unordered_map
trunk/libstdc++-v3/include/debug/unordered_set
next prev parent reply other threads:[~2014-01-20 15:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-09 18:50 [Bug libstdc++/56267] New: [4.7/4.8 " redi at gcc dot gnu.org
2013-02-10 12:20 ` [Bug libstdc++/56267] " rguenth at gcc dot gnu.org
2013-02-10 21:57 ` redi at gcc dot gnu.org
2013-02-10 23:00 ` paolo.carlini at oracle dot com
2013-02-11 0:20 ` redi at gcc dot gnu.org
2013-02-11 0:25 ` redi at gcc dot gnu.org
2013-02-14 22:04 ` jsm28 at gcc dot gnu.org
2013-04-11 8:00 ` [Bug libstdc++/56267] [4.7/4.8/4.9 " rguenth at gcc dot gnu.org
2014-01-20 15:50 ` redi at gcc dot gnu.org [this message]
2014-01-20 18:50 ` redi at gcc dot gnu.org
2014-01-21 19:39 ` 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-56267-4-Df1nRsg0H0@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).