public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/100711] New: Miss optimization for pandn Date: Fri, 21 May 2021 02:22:00 +0000 [thread overview] Message-ID: <bug-100711-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100711 Bug ID: 100711 Summary: Miss optimization for pandn Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: crazylht at gmail dot com CC: hjl.tools at gmail dot com Target Milestone: --- Target: x86_64-*-* i?86-*-* cat test.c typedef int v4si __attribute__((vector_size (16))); v4si foo (int a, v4si b) { return (__extension__ (v4si) {~a, ~a, ~a, ~a}) & b; } generate notl %edi vmovdqa %xmm0, %xmm1 vpbroadcastd %edi, %xmm0 vpand %xmm1, %xmm0, %xmm0 ret it should be better as vmovdqa %xmm0, %xmm1 vpbroadcastd %edi, %xmm0 vpandn %xmm1, %xmm0, %xmm0
next reply other threads:[~2021-05-21 2:22 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-21 2:22 crazylht at gmail dot com [this message] 2021-05-21 6:42 ` [Bug target/100711] " rguenth at gcc dot gnu.org 2021-05-21 10:36 ` segher at gcc dot gnu.org 2021-05-25 5:40 ` crazylht at gmail dot com 2021-05-25 6:52 ` crazylht at gmail dot com 2021-05-25 10:09 ` segher at gcc dot gnu.org 2021-11-30 8:37 ` cvs-commit at gcc dot gnu.org 2021-11-30 8:46 ` crazylht at gmail dot com 2023-05-24 8:42 ` jbeulich at suse dot com 2023-05-25 6:52 ` crazylht at gmail dot com 2023-05-25 8:36 ` jbeulich at suse dot com 2023-05-25 8:50 ` crazylht at gmail dot com 2023-05-27 9:28 ` cvs-commit at gcc dot gnu.org 2023-07-05 7:49 ` cvs-commit at gcc dot gnu.org 2023-07-05 7:49 ` cvs-commit at gcc dot gnu.org 2023-07-05 7:49 ` cvs-commit 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-100711-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).