https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86843
--- Comment #6 from Jonathan Wakely ---
Oh I think I misread it ... it does enable some internal assertions, but is
mostly the same meaning as our debug mode.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86843
--- Comment #5 from Jonathan Wakely ---
It's a shame they're using "debug mode" to mean "debug the library impl itself"
when that's a term we have been using with completely different meaning for
many years.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86843
--- Comment #4 from Sam James ---
libcxx has started working towards this, see
https://discourse.llvm.org/t/rfc-hardening-in-libc/73925 and
https://libcxx.llvm.org/Hardening.html.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86843
Jonathan Wakely changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86843
--- Comment #2 from Jonathan Wakely ---
Hmm, many of the checks in algorithms rely on the fact that the iterators are
Debug Mode iterators (e.g. to check that the end iterator is reachable from the
begin one, or that the iterators are not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86843
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
