https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64491

--- Comment #12 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
One possibility is just not to warn at all about loops with multiple exits,
because for those you have no guarantee the iteration that triggers undefined
behavior will be ever encountered.

Reply via email to