https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82694
--- Comment #14 from Richard Biener <rguenth at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #13) > Does the kernel still need this workaround? Shall we just add the option > and gradually add the checks? Yes - note I got stuck in the attempt to do the -f[no-]strict-overflow aliasing in common.opt in a way to also cover this new option and then forgot about it. Appearantly we can't have two Aliases nor does EnabledBy work here :/ Also note my remark on not re-introducing POINTER_OVERFLOW_UNDEFINED but instead allowing TYPE_OVERFLOW_* on pointers. Want to give it a try?
