diff options
| author | Jonathan Wakely <jwakely@redhat.com> | 2021-09-30 11:25:15 +0100 |
|---|---|---|
| committer | Jonathan Wakely <jwakely@redhat.com> | 2021-10-01 15:04:02 +0100 |
| commit | c67339d12653c33f85f8141789d7a7cf38831cbd (patch) | |
| tree | 302b3b263e2b706df3a165a2e1a75344b121ce0f /gcc | |
| parent | b8d42cfa84fb31e592411e6cea41bdde980c51d7 (diff) | |
| download | gcc-c67339d12653c33f85f8141789d7a7cf38831cbd.zip gcc-c67339d12653c33f85f8141789d7a7cf38831cbd.tar.gz gcc-c67339d12653c33f85f8141789d7a7cf38831cbd.tar.bz2 | |
libstdc++: Fix _ForwardIteratorConcept for __gnu_debug::vector<bool>
The recent changes to the _GLIBCXX_CONCEPT_CHECKS checks for forward
iterators don't work for vector<bool> iterators in debug mode, because
the _Safe_iterator specializations don't match the special cases I added
for _Bit_iterator and _Bit_const_iterator.
This refactors the _ForwardIteratorReferenceConcept class template to
identify vector<bool> iterators using a new trait, which also works for
debug iterators.
libstdc++-v3/ChangeLog:
* include/bits/boost_concept_check.h (_Is_vector_bool_iterator):
New trait to identify vector<bool> iterators, including debug
ones.
(_ForwardIteratorReferenceConcept): Add default template
argument using _Is_vector_bool_iterator and use it in partial
specialization for the vector<bool> cases.
(_Mutable_ForwardIteratorReferenceConcept): Likewise.
* testsuite/24_iterators/operations/prev_neg.cc: Adjust dg-error
line number.
Diffstat (limited to 'gcc')
0 files changed, 0 insertions, 0 deletions