public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc r10-9680] libstdc++: Fix bootstrap error due to inconsistent noexcept-specifier [PR 99983] Date: Fri, 9 Apr 2021 15:15:09 +0000 (GMT) [thread overview] Message-ID: <20210409151509.0FEB4399C00D@sourceware.org> (raw) https://gcc.gnu.org/g:2ed860be33b61ea553bf44976ef877c8356d601b commit r10-9680-g2ed860be33b61ea553bf44976ef877c8356d601b Author: Jonathan Wakely <jwakely@redhat.com> Date: Fri Apr 9 15:47:26 2021 +0100 libstdc++: Fix bootstrap error due to inconsistent noexcept-specifier [PR 99983] The backport of r11-8062 as r10-9673 missed out a piece, which causes bootstrap failures. PR bootstrap/99983 * include/bits/hashtable.h (_Hashtable): Fix noexcept-speciofier on definition to match the one on the declaration. Diff: --- libstdc++-v3/include/bits/hashtable.h | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/libstdc++-v3/include/bits/hashtable.h b/libstdc++-v3/include/bits/hashtable.h index e9a6cfe8b83..310eb52dd51 100644 --- a/libstdc++-v3/include/bits/hashtable.h +++ b/libstdc++-v3/include/bits/hashtable.h @@ -1319,8 +1319,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION _H1, _H2, _Hash, _RehashPolicy, _Traits>:: _Hashtable(_Hashtable&& __ht, __node_alloc_type&& __a, true_type /* alloc always equal */) - noexcept(std::is_nothrow_copy_constructible<_H1>::value && - std::is_nothrow_copy_constructible<_Equal>::value) + noexcept(_S_nothrow_move()) : __hashtable_base(__ht), __map_base(__ht), __rehash_base(__ht),
reply other threads:[~2021-04-09 15:15 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210409151509.0FEB4399C00D@sourceware.org \ --to=redi@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ --cc=libstdc++-cvs@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).