https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110233
--- Comment #4 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
FWIW, a less intrusive and probably more correct way of seeing what ranger
knows at this point would be to put a breakpoint where you're seeing:
Queued stmt for removal. Folds to: 2147483647
This is in tree-ssa-propagate.cc.
There you can do:
(gdb) p cfun->x_range_query->dump (stderr)
which will pick up the current ranger and dump what it knows about the IL,
without tickling any new queries:
...
...
=========== BB 3 ============
b.6_9 [irange] int [1334323000, +INF] NONZERO 0x7fffffff
<bb 3> [local count: 357878153]:
_28 = b.6_9 * 2;
ivtmp.19_27 = 2147483647;
ivtmp.22_31 = (unsigned long) &f;
goto <bb 5>; [100.00%]
_28 : [irange] int [+INF, +INF] NONZERO 0x7ffffffe
