https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83072
--- Comment #8 from Andrew Macleod <amacleod at redhat dot com> --- I've adjusted range-ops so that EVRP will recognize that c |= 1 is a non-zero range, and I've added a test case to check it. The rest of this PR involves exposing ranges in a better way to fold-const. Next release this should be covered.. we have a couple of options for exposing the new value-query API to fold_const and other consumers of the current get_range_info global interface. It's in the work queue to enable accessing the current ranger instance when its available, and fallback to the latest global value when there isn't one running. This should resolve this PR... stay tuned.
