On 4/26/21 10:16 AM, Aldy Hernandez wrote:
This does for num_pairs() what my previous patch did for VR_UNDEFINED
and VR_VARYING.
Note that VR_ANTI_RANGE for legacy is always set to 2 ranges. There
is only one way of representing a range, so a range that can be
represented as a VR_RANGE will never have a kind of VR_ANTI_RANGE.
Also legacy symbolics can also use VR_ANTI_RANGE, but no one will ever
ask for the bounds of such range, so m_num_ranges is irrelevant.
OK?
Took my a while to work it through, but I think its still correct even
if ~[a,a] is the range that num_pairs is requested.. ~[a,a] is basically
varying, and num_pairs will produce 1.
Assuming bootstrap and no regressions, OK.
Andrew
