diff options
| author | Andrew Pinski <quic_apinski@quicinc.com> | 2024-02-12 15:48:48 -0800 |
|---|---|---|
| committer | Andrew Pinski <quic_apinski@quicinc.com> | 2024-04-27 17:15:07 -0700 |
| commit | f91569e779041e2723be23d31c2a79f1861efc7f (patch) | |
| tree | c742efb74478c08c1227594bbef006ae8a867b5c /gcc/tree-vect-loop.cc | |
| parent | 140124ad54eef88ca87909f63aedc8aaeacefc65 (diff) | |
| download | gcc-f91569e779041e2723be23d31c2a79f1861efc7f.zip gcc-f91569e779041e2723be23d31c2a79f1861efc7f.tar.gz gcc-f91569e779041e2723be23d31c2a79f1861efc7f.tar.bz2 | |
aarch64: Use vec_perm_indices::new_shrunk_vector in aarch64_evpc_reencode
While working on PERM related stuff, I can across that aarch64_evpc_reencode
was manually figuring out if we shrink the perm indices instead of
using vec_perm_indices::new_shrunk_vector; shrunk was added after reencode
was added.
Built and tested for aarch64-linux-gnu with no regressions.
gcc/ChangeLog:
PR target/113822
* config/aarch64/aarch64.cc (aarch64_evpc_reencode): Use
vec_perm_indices::new_shrunk_vector instead of manually
going through the indices.
Signed-off-by: Andrew Pinski <quic_apinski@quicinc.com>
Diffstat (limited to 'gcc/tree-vect-loop.cc')
0 files changed, 0 insertions, 0 deletions