[Bug target/113537] ext should be used more for __builtin_shufflevector

[pinskia at gcc dot gnu.org via Gcc-bugs]

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

Andrew Pinski  changed:

   What|Removed |Added

 Status|ASSIGNED|NEW
   See Also||https://gcc.gnu.org/bugzill
   ||a/show_bug.cgi?id=101846

--- Comment #4 from Andrew Pinski  ---
Actually part of this is the "don't care" part, which is referenced in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101846#c10 (and maybe others).
That is something I can't fix ...

[Bug target/113537] ext should be used more for __builtin_shufflevector

[pinskia at gcc dot gnu.org via Gcc-bugs]

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

Andrew Pinski  changed:

   What|Removed |Added

 Ever confirmed|0   |1
   Assignee|unassigned at gcc dot gnu.org  |pinskia at gcc dot 
gnu.org
 Status|UNCONFIRMED |ASSIGNED
   Last reconfirmed||2024-01-22

--- Comment #3 from Andrew Pinski  ---
I am going to implement at least the aarch64_vectorize_vec_perm_const  part.
I will check the other side later on.

Note this will be part of the patch set am doing for PR 113458 .

[Bug target/113537] ext should be used more for __builtin_shufflevector

[pinskia at gcc dot gnu.org via Gcc-bugs]

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

--- Comment #2 from Andrew Pinski  ---
aarch64_vectorize_vec_perm_const does not handle at all the case where the 2
modes are different.

[Bug target/113537] ext should be used more for __builtin_shufflevector

[pinskia at gcc dot gnu.org via Gcc-bugs]

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

--- Comment #1 from Andrew Pinski  ---
One gimple level thing I noticed is we produce:
```
  _1 = VEC_PERM_EXPR ;
  _3 = BIT_FIELD_REF <_1, 64, 0>;
```

But Maybe that should just be:
```
_3 = VEC_PERM_EXPR ;
```

Which is what the vector might produce but maybe it is because
aarch64_vectorize_vec_perm_const does not know how to handle that ...