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/113859] New: popcount HI can be vectorized for non-SVE Date: Sat, 10 Feb 2024 02:15:01 +0000 [thread overview] Message-ID: <bug-113859-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113859 Bug ID: 113859 Summary: popcount HI can be vectorized for non-SVE 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: ``` void f(unsigned short * __restrict b, unsigned short * __restrict d) { for(int i = 0; i < 1024; i++) d[i] = __builtin_popcount(b[i]); } ``` This can be vectorized to: ``` ldr q0, [x9] cnt v0.16b, v0.16b uaddlp v0.8h, v0.16b stp q0, [x9] ```
next reply other threads:[~2024-02-10 2:15 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-10 2:15 pinskia at gcc dot gnu.org [this message] 2024-02-10 3:41 ` [Bug target/113859] " pinskia at gcc dot gnu.org 2024-03-05 0:58 ` pinskia at gcc dot gnu.org 2024-05-09 18:05 ` pinskia at gcc dot gnu.org 2024-06-16 0:10 ` 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-113859-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).