Tests that FAIL in C++17 mode

Jonathan Wakely jwakely@redhat.com
Wed Oct 12 13:32:00 GMT 2016

On 11/10/16 21:08 +0100, Jonathan Wakely wrote:
>On 11/10/16 11:49 +0100, Jonathan Wakely wrote:
>>The following tests are failing with -std=gnu++17
>I suspect these two fail because of guaranteed copy-elision in C++17
>mode, so they should use { target c++14_down }

Hmm, this might be a front-end regression, I need to reduce it.


This is because the unordered containers don't support fancy pointers.
_M_insert_unique_node should take __node_alloc_traits::pointer not


Fixed at r241047.


This is because we get a circular include in C++17 mode, because
<functional> includes <unordered_map>, so the profile mode headers
can't include it. I'll try splitting <functional>
into smaller pieces.

More information about the Libstdc++ mailing list