mirror of git://gcc.gnu.org/git/gcc.git
031cb46341
Because of PR c++/85944 we have several bugs where _GLIBCXX_DEBUG causes
errors for constexpr code. Although Bug 117966 could be fixed by
avoiding redundant debug checks in std::span, and Bug 106212 could be
fixed by avoiding redundant debug checks in std::array, there are many
more cases where similar __glibcxx_requires_valid_range checks fail to
compile and removing the checks everywhere isn't desirable.
This just disables the __gnu_debug::__check_singular(T*) check during
constant evaluation. Attempting to dereference a null pointer will
certainly fail during constant evaluation (if it doesn't fail then it's
a compiler bug and not the library's problem). Disabling this check
during constant evaluation shouldn't do any harm.
libstdc++-v3/ChangeLog:
PR libstdc++/109517
PR libstdc++/109976
* include/debug/helper_functions.h (__valid_range_aux): Treat
all input iterator ranges as valid during constant evaluation.
(cherry picked from commit
|
||
|---|---|---|
| .. | ||
| array | ||
| assertions.h | ||
| bitset | ||
| debug.h | ||
| deque | ||
| formatter.h | ||
| forward_list | ||
| functions.h | ||
| helper_functions.h | ||
| list | ||
| macros.h | ||
| map | ||
| map.h | ||
| multimap.h | ||
| multiset.h | ||
| safe_base.h | ||
| safe_container.h | ||
| safe_iterator.h | ||
| safe_iterator.tcc | ||
| safe_local_iterator.h | ||
| safe_local_iterator.tcc | ||
| safe_sequence.h | ||
| safe_sequence.tcc | ||
| safe_unordered_base.h | ||
| safe_unordered_container.h | ||
| safe_unordered_container.tcc | ||
| set | ||
| set.h | ||
| stl_iterator.h | ||
| string | ||
| unordered_map | ||
| unordered_set | ||
| vector | ||