[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

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

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|unassigned at gcc dot gnu.org      |pinskia at gcc dot gnu.org
            Summary|Vect module test failures   |Vect module test failures
                   |while running on remote     |while running on remote
                   |host                        |host due to default dg-do
                   |                            |set to compile and
                   |                            |additional-sources being
                   |                            |used
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2024-02-13
             Status|UNCONFIRMED                 |ASSIGNED

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed.

Basically the testcases with additional-sources should always have a `{ dg-do
run } ` set for them instead of doing the default (which can either be run or
compile depending on what target-supports.exp sets).

There is only 2 testcases which uses additional-sources:
gcc.dg/vect/vect-simd-clone-10.c
gcc.dg/vect/vect-simd-clone-12.c


So I am going to fix those 2 to use `{ dg-do run }`