[EASY] Use runtime_var_to_range for guards (#107329)
We sometimes allow compile-time reasoning to diverge from runtime
reasoning. When we check guards, we are testing for *runtime*
properties. Thus we should use those ranges, not the compile time
ones.
Signed-off-by: Edward Z. Yang <ezyang@meta.com>
Pull Request resolved: https://github.com/pytorch/pytorch/pull/107329
Approved by: https://github.com/tugsbayasgalan