public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/100711] Miss optimization for pandn Date: Sat, 27 May 2023 09:28:43 +0000 [thread overview] Message-ID: <bug-100711-4-FtlYqY4MaG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100711-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100711 --- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by hongtao Liu <liuhongt@gcc.gnu.org>: https://gcc.gnu.org/g:ed6a9a35799c9298321d1589533767c2bb6f8d42 commit r14-1307-ged6a9a35799c9298321d1589533767c2bb6f8d42 Author: liuhongt <hongtao.liu@intel.com> Date: Thu May 25 16:14:14 2023 +0800 Split notl + pbraodcast + pand to pbroadcast + pandn more modes. r12-5595-gc39d77f252e895306ef88c1efb3eff04e4232554 adds 2 splitter to transform notl + pbroadcast + pand to pbroadcast + pandn for VI124_AVX2 which leaves out all DI-element-size ones as well as all 512-bit ones. This patch extend the splitter to VI_AVX2 which will handle DImode for AVX2, and V64QImode,V32HImode,V16SImode,V8DImode for AVX512. gcc/ChangeLog: PR target/100711 * config/i386/sse.md (*andnot<mode>3): Extend below splitter to VI_AVX2 to cover more modes. gcc/testsuite/ChangeLog: * gcc.target/i386/pr100711-2.c: Add v4di/v2di testcases. * gcc.target/i386/pr100711-3.c: New test.
next prev parent reply other threads:[~2023-05-27 9:28 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-21 2:22 [Bug target/100711] New: " crazylht at gmail dot com 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 [this message] 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-FtlYqY4MaG@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).