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

--- Comment #7 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by hongtao Liu <liuho...@gcc.gnu.org>:

https://gcc.gnu.org/g:1c51d0109a4730827c40c3bbd3a59d459828017e

commit r14-8266-g1c51d0109a4730827c40c3bbd3a59d459828017e
Author: liuhongt <hongtao....@intel.com>
Date:   Fri Jan 19 09:22:39 2024 +0800

    Fix testcase failure on many platforms which don't support vect_int_max.

    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.

    gcc/testsuite/ChangeLog:

            PR testsuite/113437
            * gcc.dg/tree-ssa/pr95906.c: Scan either MAX_EXPR or
            VEC_COND_EXPR.

Reply via email to