https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105834
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=109695
Keywords|needs-bisection |
--- Comment #6 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
On trunk, this was fixed by r14-1163-gd8b058d3ca4ebb, one of the
patchset which fixed PR 109695:
d8b058d3ca4ebbef5575105164417f125696f5ce is the first new commit
commit d8b058d3ca4ebbef5575105164417f125696f5ce
Author: Andrew MacLeod <amacl...@redhat.com>
Date: Tue May 23 15:11:44 2023 -0400
Choose better initial values for ranger.
Instead of defaulting to VARYING, fold the stmt using just global ranges.
PR tree-optimization/109695
* gimple-range-cache.cc (ranger_cache::get_global_range): Call
fold_range with global query to choose an initial value.
gcc/gimple-range-cache.cc | 17 ++++++++++++++++-
1 file changed, 16 insertions(+), 1 deletion(-)
Would this patch be something that could reasonably be backported?
