https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99983
Maxim Kuvyrkov <mkuvyrkov at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Build|powerpc64*-linux-gnu |powerpc64*-linux-gnu
| |x86_64-linux-gnu
| |aarch64-linux-gnu
| |arm-linux-gnueabihf
Target|powerpc64*-linux-gnu |powerpc64*-linux-gnu
| |x86_64-linux-gnu
| |aarch64-linux-gnu
| |arm-linux-gnueabihf
CC| |fdumont at gcc dot gnu.org,
| |mkuvyrkov at gcc dot gnu.org
Host|powerpc64*-linux-gnu |powerpc64*-linux-gnu
| |x86_64-linux-gnu
| |aarch64-linux-gnu
| |arm-linux-gnueabihf
--- Comment #3 from Maxim Kuvyrkov <mkuvyrkov at gcc dot gnu.org> ---
(In reply to seurer from comment #1)
> The failures shown were on a power 8 LE system for
> g:348fb9db7858b0fe852da3cd1195b90b2211b983, r10-9675. I have something
> running to look for what revision started it.
It appears to be
===
commit 1c4e8a96cd695c03ff85299bf2392476feae99bb
Author: François Dumont <fdum...@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 also confirmed on x86_64, aarch64, and aarch32.
