path solver: Use range_on_path_entry instead of looking at equivalences.
authorAldy Hernandez <aldyh@redhat.com>
Wed, 22 Sep 2021 07:34:15 +0000 (09:34 +0200)
committerAldy Hernandez <aldyh@redhat.com>
Wed, 22 Sep 2021 11:28:08 +0000 (13:28 +0200)
commit7e5e44bd1729b7a9b458d512ddf61bfba5031869
tree467be1ab1d3f12fbf1f32a2018a2e186ddf6ff92
parent6b0e0b29c639451dd8e2234907b68806e51019c7
path solver: Use range_on_path_entry instead of looking at equivalences.

Cycling through equivalences to improve a range is nowhere near as
efficient as asking the ranger what the range on entry is.

Testing on a hybrid VRP threader, shows that this improves our VRP
threading benefit from 14.5% to 18.5% and our overall jump threads from
0.85% to 1.28%.

Tested on x86-64 Linux.

gcc/ChangeLog:

* gimple-range-path.cc (path_range_query::internal_range_of_expr):
Remove call to improve_range_with_equivs.
(path_range_query::improve_range_with_equivs): Remove
* gimple-range-path.h: Remove improve_range_with_equivs.
gcc/gimple-range-path.cc
gcc/gimple-range-path.h