public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113537] New: ext should be used more for __builtin_shufflevector Date: Mon, 22 Jan 2024 06:06:18 +0000 [thread overview] Message-ID: <bug-113537-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113537 Bug ID: 113537 Summary: ext should be used more for __builtin_shufflevector Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: enhancement Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: pinskia at gcc dot gnu.org Target Milestone: --- Target: aarch64 Take: ``` #define vector4 __attribute__((vector_size(4))) #define vector8 __attribute__((vector_size(8))) #define vector16 __attribute__((vector_size(16))) vector8 char f3(vector16 char a) { return __builtin_shufflevector (a, a, 1, 2, 3, 4, 5, 6, 7, 8); } vector8 char f2(vector16 char a) { return __builtin_shufflevector (a, a, 1, 2, 3, 4, 5, 6, 7, 0); } ``` Currently GCC produces: ``` f3: adrp x0, .LC0 ldr q31, [x0, #:lo12:.LC0] tbl v0.16b, {v0.16b}, v31.16b ret f2: adrp x0, .LC1 ldr q31, [x0, #:lo12:.LC1] tbl v0.16b, {v0.16b}, v31.16b ret ``` But these should be optimized to just: ``` f3: ext v0.16b, v0.16b, v0.16b, #1 ret f2: ext v0.8b, v0.8b, v0.8b, #1 ret ```
next reply other threads:[~2024-01-22 6:06 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-22 6:06 pinskia at gcc dot gnu.org [this message] 2024-01-22 6:11 ` [Bug target/113537] " pinskia at gcc dot gnu.org 2024-01-22 6:23 ` pinskia at gcc dot gnu.org 2024-01-22 6:51 ` pinskia at gcc dot gnu.org 2024-02-12 7:14 ` pinskia at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-113537-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).