Thomas Schwinge <tho...@codesourcery.com> writes:
> Hi Marc! > > On 2023-11-06T11:59:18+0100, Marc Poulhiès <poulh...@adacore.com> wrote: >> These 3 tests fails parsing the 'vect' dump when not using -mavx. Make >> the dependency explicit. > > But that means that the tests are now enabled *only* for > effective-target 'avx_runtime', so, for example, on GCN I see: > > -PASS: gcc.dg/vect/vect-ifcvt-18.c (test for excess errors) > -PASS: gcc.dg/vect/vect-ifcvt-18.c execution test > +UNSUPPORTED: gcc.dg/vect/vect-ifcvt-18.c > > -PASS: gcc.dg/vect/vect-simd-clone-16f.c (test for excess errors) > -PASS: gcc.dg/vect/vect-simd-clone-16f.c execution test > -PASS: gcc.dg/vect/vect-simd-clone-16f.c scan-tree-dump-times vect > "[\\n\\r] [^\\n]* = foo\\.simdclone" 2 > +UNSUPPORTED: gcc.dg/vect/vect-simd-clone-16f.c > > -PASS: gcc.dg/vect/vect-simd-clone-18f.c (test for excess errors) > -PASS: gcc.dg/vect/vect-simd-clone-18f.c execution test > -PASS: gcc.dg/vect/vect-simd-clone-18f.c scan-tree-dump-times vect > "[\\n\\r] [^\\n]* = foo\\.simdclone" 2 > +UNSUPPORTED: gcc.dg/vect/vect-simd-clone-18f.c > > ..., which was not the intention, I suppose? Hello Thomas, No, that was an oversight, Jakub also spotted that in another patch. I'll revert it now. Sorry for the inconvenience, Marc
