http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48189
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-12-20
13:10:15 UTC ---
Already the:
if (host_integerp (niter, 1)
&& compare_tree_int (niter, max-1) == -1)
nitercst = tree_low_cst (niter, 1) + 1;
looks wrong, if max is 0, then we are calling compare_tree_int with UHWI
maximum
and even huge nitercst values will make through.
IMHO we should just guard the above with max != 0 as well.
I think max_stmt_executions_int will never return 0, so both patches probably
work fine. Honza?
