This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [Patch] Adjust diag-scans in vect-tests to fix fails on AVX/AVX2


On 12/12/2011 09:44 PM, Michael Zolotukhin wrote:
> Should we introduce checks for each possible vector datatype (e.g.
> vect_8byte_int_available, vect_16byte_int_available,
> vect_32byte_int_available, vect_16byte_float_available,
> vect_32byte_float_available etc.) along with a check for
> prefer_something (e.g. vect_prefer_16byte)? Having such info, we'll be
> able to distinguish all the cases, right?

Meh.  This seems excruciatingly error prone.

I think we should simply re-write the test cases so that it doesn't
matter how many times we see a particular string.  Don't combine so
many (potentially vectorizable) loops within a test case that it matters.


r~


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]