Fix testsuite bugs
authorJonathan Wakely <jwakely@redhat.com>
Thu, 23 May 2019 21:41:08 +0000 (22:41 +0100)
committerJonathan Wakely <redi@gcc.gnu.org>
Thu, 23 May 2019 21:41:08 +0000 (22:41 +0100)
commit5f303216e5e321f759a88c7c1cbffd84b0997ead
tree7c0f6ee0d52382f510cea9ee0717d81598baedd1
parentfb3fc4bded8d934b603a7f07ab3cfe3b644ee971
Fix testsuite bugs

One of the static assertions in 20_util/function_objects/invoke/1.cc was
wrong, but didn't fail because by default it was compiled with
-std=gnu++14 which didn't use that static assertion. Split out the C++17
parts to a new file that always runs with -std=gnu++17, so those checks
are always done.

The 23_containers/unordered_set/allocator/ext_ptr.cc test is supposed to
be a run-time test but was unintentionally compile-only.

* testsuite/20_util/function_objects/invoke/1.cc: Move C++17-specific
tests to ...
* testsuite/20_util/function_objects/invoke/3.cc: New test.
* testsuite/23_containers/unordered_set/allocator/ext_ptr.cc: Change
"compile" test to "run".

From-SVN: r271584
libstdc++-v3/ChangeLog
libstdc++-v3/testsuite/20_util/function_objects/invoke/1.cc
libstdc++-v3/testsuite/20_util/function_objects/invoke/3.cc [new file with mode: 0644]
libstdc++-v3/testsuite/23_containers/unordered_set/allocator/ext_ptr.cc