public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gabravier at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/102591] New: Failure to optimize search for value in vector-sized area to use SIMD Date: Mon, 04 Oct 2021 12:12:24 +0000 [thread overview] Message-ID: <bug-102591-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102591 Bug ID: 102591 Summary: Failure to optimize search for value in vector-sized area to use SIMD Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: gabravier at gmail dot com Target Milestone: --- bool match8(char *tpl) { int found = 0; for (int at = 0; at < 16; at++) if (tpl[at] == 0) found = 1; return found; } This function can be greatly optimized by using SIMD. It can be optimized to something like this: typedef char v16i8 __attribute__((vector_size(16))); bool match8v2(char *tpl) { v16i8 values; __builtin_memcpy(&values, tpl, 16); v16i8 compared = (values == 0); return _mm_movemask_epi8((__m128i)compared) != 0; } This optimization is done by LLVM, but not by GCC. PS: I've marked this as an x86 bug, but only because I could not find a portable way of expressing `_mm_movemask_epi8((__m128i)compared)`, I would assume other architectures have similar ways of expressing the same thing cheaply. (For example, Altivec should be able to implement that operation with a `vec_extract(vec_vbpermq((__vector unsigned char)compared, perm), 1)` with `perm` looking like this: `{120, 112, 104, 96, 88, 80, 72, 64, 56, 48, 40, 32, 24, 16, 8, 0}` and the 1 replaced with 14 on big-endian)
next reply other threads:[~2021-10-04 12:12 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-04 12:12 gabravier at gmail dot com [this message] 2021-10-05 6:44 ` [Bug target/102591] " rguenth at gcc dot gnu.org 2021-10-05 9:46 ` gabravier at gmail dot com 2021-10-05 10:19 ` [Bug tree-optimization/102591] " rguenth 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-102591-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).