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/96906] New: Failure to optimize __builtin_ia32_psubusw128 compared to 0 to __builtin_ia32_pminuw128 compared to operand Date: Wed, 02 Sep 2020 20:22:35 +0000 [thread overview] Message-ID: <bug-96906-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96906 Bug ID: 96906 Summary: Failure to optimize __builtin_ia32_psubusw128 compared to 0 to __builtin_ia32_pminuw128 compared to operand Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: gabravier at gmail dot com Target Milestone: --- typedef int16_t v8i16 __attribute__((vector_size(16))); v8i16 cmple_epu16(v8i16 x, v8i16 y) { return __builtin_ia32_psubusw128(x, y) == 0; } With -msse4.1, this can be optimized to `return __builtin_ia32_pminuw128(x, y) == x;`. This transformation is done by LLVM, but not by GCC. PS: I'm not 100% sure this is faster but it logically should be, since the `pminuw` version doesn't have to handle zeroing an SSE register.
next reply other threads:[~2020-09-02 20:22 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-02 20:22 gabravier at gmail dot com [this message] 2020-09-03 3:06 ` [Bug target/96906] " crazylht at gmail dot com 2020-09-03 3:29 ` crazylht at gmail dot com 2020-09-03 3:54 ` crazylht at gmail dot com 2020-11-24 17:20 ` jakub at gcc dot gnu.org 2020-11-26 7:48 ` cvs-commit at gcc dot gnu.org 2020-11-26 8:58 ` jakub at gcc dot gnu.org 2020-11-26 9:03 ` crazylht at gmail dot com 2020-12-03 5:45 ` cvs-commit at gcc dot gnu.org 2020-12-03 5:46 ` crazylht at gmail dot com 2021-01-12 15:21 ` jakub 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-96906-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).