On 02/01/2017 03:45 AM, Richard Biener wrote:
I agree. But this means we should look for a vectorizer-local fix
without a new global predicate then (there seem to be subtly different
needs and coming up with good names for all of them sounds difficult...).
Well, we could go with Jakub's INTEGRAL_BOOLEAN_TYPE as posted, but in
contexts where we use it and really depend on single bit objects, we add
the precision == 1 check back. Jakub's patch removes the type precision
check in tree-vect-patterns for example. There's likely all kinds of
places where we need to add that check as well.
/me is frustrated that we have booleans with nonstandard precision, even
though I understand why it was done. It creates numerous headaches.
Jeff
