https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94663
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Vladimir Makarov from comment #2)
> The best way to fix is to avoid to generate such code. But I don't know is
> it possible for this case.
I'm afraid that is hard, because the Intel intrinsic APIs have such permanent
vector type/mode casts inherent in its APIs, while for floating point vectors
they have separate types for vectors of floats and for vectors of doubles, for
vectors of integral types they have just a single type like __m{128,256,512}i
which has just (somewhat randomly) picked one particular element type; and that
is the mode of the user vars that use the Intel APIs, and then on each
operation that needs to work with different vector mode there is cast to that
and back.
