https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114331

--- Comment #15 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Oh, and maybe if you want for performance reasons to avoid computing
irange_bitmask unless necessary, in cases like where irange_bitmask wasn't set
before verify if it is really different from the bitmask implied for its range
and only set if it is different from that.

Reply via email to