https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61597
--- Comment #14 from Jonathan Wakely <redi at gcc dot gnu.org> --- Yes, I can't convince gcc or clang to give a warning. Even address sanitizer and undefined-behaviour sanitizer don't catch the problem.
