Re: [PATCH 2/2] Cache irange::num_pairs() for non-legacy code.

2021-04-26 Thread Andrew MacLeod via Gcc-patches
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 nev

[PATCH 2/2] Cache irange::num_pairs() for non-legacy code.

2021-04-26 Thread Aldy Hernandez via Gcc-patches
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