[Bug tree-optimization/126601] [13/14/15 Regression] ICE in match_arith_overflow with widen-mul since r11-6580
cvs-commit at gcc dot gnu.org
gcc-bugzilla@gcc.gnu.org
Thu Aug 27 14:11:55 GMT 2026
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=126601
--- Comment #7 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-15 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:c36af846344625a4c8172479f1acb5760f4c18f2
commit r15-11517-gc36af846344625a4c8172479f1acb5760f4c18f2
Author: Jakub Jelinek <jakub@redhat.com>
Date: Tue Aug 4 10:37:09 2026 +0200
widening_mul: Fix up ICE in maybe_optimize_guarding_check [PR126601]
The following testcase ICEs, because we try to quick_push into an already
full vector.
The caller (match_arith_overflow) has
auto_vec<gimple *, 8> mul_stmts;
and 0-6 mul_stmts.quick_push (...); calls (none of that in a loop), and
then
call to that maybe_optimize_guarding_check function which does one
quick_push, but the function is called in a
FOR_EACH_IMM_USE_STMT (use_stmt, iter, cast_lhs ? cast_lhs : lhs)
loop, so if we are unlucky as on the attached testcase, it is called more
than twice and either triggers ICE, or worse with checking disabled buffer
overflow.
The following patch fixes that by using safe_push in that spot instead.
2026-08-04 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/126601
* tree-ssa-math-opts.cc (maybe_optimize_guarding_check): Use
safe_push
on mul_stmts rather than quick_push.
* gcc.dg/tree-ssa/pr126601.c: New test.
Reviewed-by: Richard Biener <rguenth@suse.de>
(cherry picked from commit a49c114c7b3edd33a6ff2e50e6276ca1fbe8ad83)
More information about the Gcc-bugs
mailing list