https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89536
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> --- (In reply to Eric Botcazou from comment #5) > There is very likely the same issue in the BIT_AND_EXPR case then. Isn't that different though? I mean, even if we have int type and have [0, 1] range and have a check that the value isn't 0, then it must be 1.
