After r14-7124-g6686e16fda4190, the testcase can be optimized to MAX_EXPR if the backends support that. So I adjust the testcase to scan for MAX_EXPR, but it failed many platforms which don't support that. As pinski mentioned, target vect_no_int_min_max is only available under vect directory, so for simplicity, I adjust the testcase to scan either MAX_EXPR or original VEC_COND_EXPR.
Commit as an obvious fix. gcc/testsuite/ChangeLog: PR testsuite/113437 * gcc.dg/tree-ssa/pr95906.c: Scan either MAX_EXPR or VEC_COND_EXPR. --- gcc/testsuite/gcc.dg/tree-ssa/pr95906.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/testsuite/gcc.dg/tree-ssa/pr95906.c b/gcc/testsuite/gcc.dg/tree-ssa/pr95906.c index d15670f3e9e..ce43983f341 100644 --- a/gcc/testsuite/gcc.dg/tree-ssa/pr95906.c +++ b/gcc/testsuite/gcc.dg/tree-ssa/pr95906.c @@ -9,4 +9,4 @@ v16i8 f(v16i8 a, v16i8 b) } /* { dg-final { scan-tree-dump-not "bit_(and|ior)_expr" "forwprop3" } } */ -/* { dg-final { scan-tree-dump-times "max_expr" 1 "forwprop3" } } */ +/* { dg-final { scan-tree-dump-times {(?n)(?:max_expr|vec_cond_expr)} 1 "forwprop3" } } */ -- 2.31.1