> And even this is insufficient, since you need to distinguish between multiple > integer vector sizes and multiple fp vector sizes, aka AVX vs AVX2.
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? On 13 December 2011 00:46, Richard Henderson <r...@redhat.com> wrote: > On 12/12/2011 12:07 AM, Jakub Jelinek wrote: >> Which is why introducing >> vect_multiple_sizes_32B_16B (for -mno-prefer-128) and >> vect_multiple_sizes_16B_32B (for -mprefer-128) and using it in the tests >> could solve it. > > And even this is insufficient, since you need to distinguish between multiple > integer vector sizes and multiple fp vector sizes, aka AVX vs AVX2. > > r~
