https://gcc.gnu.org/bugzilla/show_bug.cgi?id=123873
Kees Cook <kees at outflux dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kees at outflux dot net
--- Comment #6 from Kees Cook <kees at outflux dot net> ---
I think it is a mistake to consider ubsan-bounds checking as non-production.
This is objectively false: it is used in all major Linux distros (and have been
enabled for literal years now) and is a foundational building block of
providing memory safety to C. If there are bugs in the resulting optimizations,
we can address those. Disabling the bounds checker in project that use it is a
dangerous weakening of the security flaw mitigation work that has been going on
for almost a decade now. I won't speak to the other ub-related sanitizers, but
the bounds checker is a critical part of the Linux kernel's memory safety
endeavor.
