https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97909
Andrew Macleod changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97909
--- Comment #5 from CVS Commits ---
The master branch has been updated by Andrew Macleod :
https://gcc.gnu.org/g:49d5fb4feee831868d80fff4d024c271911c92ca
commit r12-6559-g49d5fb4feee831868d80fff4d024c271911c92ca
Author: Andrew MacLeod
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97909
--- Comment #4 from Andrew Macleod ---
This functionality was added with fc4076752067fb400b43adbd629081df658da246
Commentary here
https://gcc.gnu.org/pipermail/gcc-patches/2021-November/583216.html
All one needs is an active ranger via the enab
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97909
--- Comment #3 from Andrew Macleod ---
It should be able to access the currently known global values that have been
computed, or if there isn't one, it could still go and calculate a global
range. Which is what the default condition would be (
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97909
--- Comment #2 from Richard Biener ---
Note that all folding may only ever access SSA use-def chains and cannot rely
on immediate uses. Also it may not use context (aka gimple_bb of def stmts) so
I have a hard time seeing on-demand range compute
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97909
--- Comment #1 from Andrew Macleod ---
Yeah, I'm planning as one of the next steps to replace the
SSA_NAME_RANGE_INFO/get_range_info interface with the new range_query interface
from value-query.h
Then we can wire that into the Ranger instance t
