https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118910
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rguenth at gcc dot gnu.org
Keywords| |missed-optimization
Version|unknown |15.0
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Note I still want to get rid of DOM itself. I would have expected that
ranger tell us b == 0 on that edge?
When working on marrying VN with ranger I was wondering how to make it
aware of the VNs value lattice and it's optimistic knowledge of
executable edges and specifically how to make it aware previous optimistic
values/non-executable edge state has been revisited (and how to ensure
ranges will only become less precise during iteration).
Do you have a testcase along your POC?
