https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102650
--- Comment #8 from Andrew Macleod <amacleod at redhat dot com> --- Aldy had some ideas of how to extend the threaders new path evaluation capabilities to determine if there are any paths between bbX and bbY which meet specific range conditions like UNDEFINED, or [0, 0] for null tracking. This could add more robustness to some of the warnings and other passes by isolating each path and checking it with more specificity than the generalized range query provides. It could also provide the specific path(s) and conditions upon which the failure occurs.
