[Bug testsuite/113899] Vect module test failures while running on remote host due to default dg-do set to compile and additional-sources being used

["cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>]

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

--- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Andrew Pinski <pinskia@gcc.gnu.org>:

https://gcc.gnu.org/g:948dbc5ee45f9ffd5f41fd6782704081cc7c8c27

commit r14-8978-g948dbc5ee45f9ffd5f41fd6782704081cc7c8c27
Author: Andrew Pinski <quic_apinski@quicinc.com>
Date:   Tue Feb 13 13:39:16 2024 -0800

    vect/testsuite: Fix vect-simd-clone-1[02].c when dg-do default is compile
[PR113899]

    The vect testsuite will chose the dg-do default based on if it knows the
    running target does not support running with the vector extensions enabled
    (for easy of testing). The problem is when it is decided the default is
compile
    instead of run, dg-additional-sources does not work. So the fix is to set
    dg-do on these two testcases to run explicitly.

    Tested on x86_64 with a hack to check_vect_support_and_set_flags to set the
dg-default
    to compile.

    gcc/testsuite/ChangeLog:

            PR testsuite/113899
            * gcc.dg/vect/vect-simd-clone-10.c: Add `dg-do run`
            * gcc.dg/vect/vect-simd-clone-12.c: Likewise.

    Signed-off-by: Andrew Pinski <quic_apinski@quicinc.com>