Don't use ANY PHI equivalences in range-on-entry.
authorAndrew MacLeod <amacleod@redhat.com>
Tue, 11 Apr 2023 21:29:03 +0000 (17:29 -0400)
committerAndrew MacLeod <amacleod@redhat.com>
Wed, 12 Apr 2023 13:07:20 +0000 (09:07 -0400)
commit24af552876eff707f75d30d3f0f0e7a5d62dd857
tree4539e782839b1fb4302ff3854e36fc2ec0d60477
parent9f10b4957ca6058d1a801c5e4bfe11bf159da809
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.
gcc/gimple-range-cache.cc
gcc/testsuite/gcc.dg/uninit-pr101912.c