https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108139
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Andrew Macleod <amacl...@gcc.gnu.org>: https://gcc.gnu.org/g:24af552876eff707f75d30d3f0f0e7a5d62dd857 commit r13-7150-g24af552876eff707f75d30d3f0f0e7a5d62dd857 Author: Andrew MacLeod <amacl...@redhat.com> Date: Tue Apr 11 17:29:03 2023 -0400 Don't use ANY PHI equivalences in range-on-entry. PR 108139 dissallows PHI equivalencies in the on-entry calculator, but it was only checking if the equivlaence was a PHI. In this case, NAME itself is a PHI with an equivlaence caused by an undefined value, so we also need to check that case. Unfortunately this un-fixes 101912. PR tree-optimization/109462 gcc/ * gimple-range-cache.cc (ranger_cache::fill_block_cache): Don't check for equivalences if NAME is a phi node. gcc/testsuite/ * gcc.dg/uninit-pr101912.c: XFAIL the warning.
