diff options
author | Jonathan Wakely <jwakely@redhat.com> | 2025-01-15 21:24:15 +0000 |
---|---|---|
committer | Jonathan Wakely <redi@gcc.gnu.org> | 2025-01-15 23:34:28 +0000 |
commit | f079feecab1dda0ea8c7fe632c41dbb3ee1892b8 (patch) | |
tree | b0fd5fc2243c1fe4ea56354a4357975fa0ae9609 /libgo/configure | |
parent | 903ab914dd48c3131ded0cf427da50c23168024c (diff) | |
download | gcc-f079feecab1dda0ea8c7fe632c41dbb3ee1892b8.zip gcc-f079feecab1dda0ea8c7fe632c41dbb3ee1892b8.tar.gz gcc-f079feecab1dda0ea8c7fe632c41dbb3ee1892b8.tar.bz2 |
libstdc++: Fix fancy pointer test for std::set
The alloc_ptr.cc test for std::set tries to use C++17 features
unconditionally, and tries to use the C++23 range members which haven't
been implemented for std::set yet.
Some of the range checks are left in place but commented out, so they
can be added after the ranges members are implemented. Others (such as
prepend_range) are not valid for std::set at all.
Also fix uses of internal feature test macros in two other tests, which
should use the standard __cpp_lib_xxx macros.
libstdc++-v3/ChangeLog:
* testsuite/23_containers/set/requirements/explicit_instantiation/alloc_ptr.cc:
Guard node extraction checks with feature test macro. Remove
calls to non-existent range members.
* testsuite/23_containers/forward_list/requirements/explicit_instantiation/alloc_ptr.cc:
Use standard macro not internal one.
* testsuite/23_containers/list/requirements/explicit_instantiation/alloc_ptr.cc:
Likewise.
Diffstat (limited to 'libgo/configure')
0 files changed, 0 insertions, 0 deletions