[Bug target/113556] New: gcc.dg/vect/vect-simd-clone-16c.c etc. FAIL

[ro at gcc dot gnu.org]

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

            Bug ID: 113556
           Summary: gcc.dg/vect/vect-simd-clone-16c.c etc. FAIL
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ro at gcc dot gnu.org
                CC: ams at gcc dot gnu.org
  Target Milestone: ---
            Target: i386-pc-solaris2.11

Since their introduction on 20230222, several tests FAIL on Solaris/x86 (both
32 and 64-bit) when using a 32-bit compiler only:

FAIL: gcc.dg/vect/vect-simd-clone-16c.c scan-tree-dump-times vect "[\\\\n\\\\r]
[^\\\\n]* = foo\\\\.simdclone" 2
FAIL: gcc.dg/vect/vect-simd-clone-16d.c scan-tree-dump-times vect "[\\\\n\\\\r]
[^\\\\n]* = foo\\\\.simdclone" 2
FAIL: gcc.dg/vect/vect-simd-clone-17c.c scan-tree-dump-times vect "[\\\\n\\\\r]
[^\\\\n]* = foo\\\\.simdclone" 2
FAIL: gcc.dg/vect/vect-simd-clone-17d.c scan-tree-dump-times vect "[\\\\n\\\\r]
[^\\\\n]* = foo\\\\.simdclone" 2
FAIL: gcc.dg/vect/vect-simd-clone-18c.c scan-tree-dump-times vect "[\\\\n\\\\r]
[^\\\\n]* = foo\\\\.simdclone" 2
FAIL: gcc.dg/vect/vect-simd-clone-18d.c scan-tree-dump-times vect "[\\\\n\\\\r]
[^\\\\n]* = foo\\\\.simdclone" 2

The same tests PASS (again, 32 and 64-bit) when using a 64-bit compiler
instead.

I noticed that those tests have something like

/* { dg-final { scan-tree-dump-times {[\n\r] [^\n]* = foo\.simdclone} 2 "vect"
{ target { ! { x86_64*-*-* || { i686*-*-* || aarch64*-*-* } } } } } } */

while the 32-bit Solaris/x86 triple still is i386-pc-solaris2.11. However, that
compiler defaults to -mpentium4.

Is there anything in the tests that require specific ISA extensions only
available on i686 or is this just an oversight, so we can switch them to use
i?u6 instead?