https://gcc.gnu.org/bugzilla/show_bug.cgi?id=123195
--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
We are expecting to have these codes covered by pattern recognition which in
turn has checks like
if (!target_has_vecop_for_code (NEGATE_EXPR, vectype)
|| !target_has_vecop_for_code (BIT_XOR_EXPR, vectype)
|| !target_has_vecop_for_code (BIT_IOR_EXPR, vectype)
|| !target_has_vecop_for_code (PLUS_EXPR, vectype)
|| !target_has_vecop_for_code (MINUS_EXPR, vectype)
|| !expand_vec_cmp_expr_p (vectype, mask_vectype, LT_EXPR)
|| !expand_vec_cond_expr_p (vectype, mask_vectype))
I wonder if you can step through the pattern recog process and see which
of these fail? It's probably the vec_cmp or vec_cond one? So the testcase
would need a dg-require-effective-target vect_condition? At least sparc
is not in this class but we already require this!?
