https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85435
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
This isn't important to fix just because ubsan will be happy, but the
optimizers actively derive non-NULL range for the pointers from the memmove
call and so could optimize away say comparisons against NULL of those pointers
etc.
So, if it is valid for the move method on char_traits to be called with NULL,
the fix is very important.
