[Bug target/113822] aarch64_evpc_reencode could/should use new_shrunk_vector instead of manually doing it

2024-04-27 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113822 Andrew Pinski changed: What|Removed |Added Status|ASSIGNED|RESOLVED Target Milestone|---

[Bug target/113822] aarch64_evpc_reencode could/should use new_shrunk_vector instead of manually doing it

2024-04-27 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113822 --- Comment #3 from GCC Commits --- The trunk branch has been updated by Andrew Pinski : https://gcc.gnu.org/g:f91569e779041e2723be23d31c2a79f1861efc7f commit r15-12-gf91569e779041e2723be23d31c2a79f1861efc7f Author: Andrew Pinski Date: Mon

[Bug target/113822] aarch64_evpc_reencode could/should use new_shrunk_vector instead of manually doing it

2024-02-12 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113822 --- Comment #2 from Andrew Pinski --- Patch posted: https://gcc.gnu.org/pipermail/gcc-patches/2024-February/645448.html

[Bug target/113822] aarch64_evpc_reencode could/should use new_shrunk_vector instead of manually doing it

2024-02-12 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113822 Andrew Pinski changed: What|Removed |Added Last reconfirmed||2024-02-12 Status|UNCONFIRM