[Bug testsuite/113418] Use of vect_* target selectors in tests out of vect directories

[cvs-commit at gcc dot gnu.org]

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

--- Comment #6 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Xi Ruoyao <xry111@gcc.gnu.org>:

https://gcc.gnu.org/g:889fbc9454e2d4e2b9a11a9e02b3b7e698edcd1c

commit r14-9290-g889fbc9454e2d4e2b9a11a9e02b3b7e698edcd1c
Author: Xi Ruoyao <xry111@xry111.site>
Date:   Tue Jan 23 19:58:21 2024 +0800

    testsuite: Make pr104992.c irrelated to target vector feature [PR113418]

    The vect_int_mod target selector is evaluated with the options in
    DEFAULT_VECTCFLAGS in effect, but these options are not automatically
    passed to tests out of the vect directories.  So this test fails on
    targets where integer vector modulo operation is supported but requiring
    an option to enable, for example LoongArch.

    In this test case, the only expected optimization not happened in
    original is in corge because it needs forward propogation.  So we can
    scan the forwprop2 dump (where the vector operation is not expanded to
    scalars yet) instead of optimized, then we don't need to consider
    vect_int_mod or not.

    gcc/testsuite/ChangeLog:

            PR testsuite/113418
            * gcc.dg/pr104992.c (dg-options): Use -fdump-tree-forwprop2
            instead of -fdump-tree-optimized.
            (dg-final): Scan forwprop2 dump instead of optimized, and remove
            the use of vect_int_mod.
            * lib/target-supports.exp (check_effective_target_vect_int_mod):
            Remove because it's not used anymore.