[Bug tree-optimization/122296] [16 Regression] ICE on valid code at -O1 on x86_64-linux-gnu: verify_gimple failed since r16-4219
cvs-commit at gcc dot gnu.org
gcc-bugzilla@gcc.gnu.org
Fri Oct 17 05:01:31 GMT 2025
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=122296
--- Comment #7 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Andrew Pinski <pinskia@gcc.gnu.org>:
https://gcc.gnu.org/g:eb717a8f4ea9f5eebb3d5add0ca4a33d74febd1a
commit r16-4463-geb717a8f4ea9f5eebb3d5add0ca4a33d74febd1a
Author: Andrew Pinski <andrew.pinski@oss.qualcomm.com>
Date: Thu Oct 16 17:02:52 2025 -0700
match: Fix (a != b) | ((a|b) != 0) and (a == b) & ((a|b) == 0) match
pattern [PR122296]
There are 2 fixes for these 2 patterns.
1) Reuse the (a|b) expression instead of recreating it
Fixed by capturing the bit_ior expression and using that instead
of a new expression.
2) Use the correct 0. Fixed by capturing the integer_zerop and using that
instead of integer_zero_node.
2) could be fuxed by using `build_cst_zero (TREE_TYPE (@0))` But since
we already have the correct 0, capturing it would be faster.
Pushed as obvious after a bootstrap/test on x86_64-linux-gnu.
PR tree-optimization/122296
gcc/ChangeLog:
* match.pd (`(a != b) | ((a|b) != 0)`): Reuse both
the ior and zero instead of recreating them.
(`(a == b) & ((a|b) == 0)`): Likewise
gcc/testsuite/ChangeLog:
* gcc.dg/torture/int-bwise-opt-1.c: New test.
Signed-off-by: Andrew Pinski <andrew.pinski@oss.qualcomm.com>
More information about the Gcc-bugs
mailing list