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/93768] Use vpternlog for composite logical operations Date: Wed, 05 Jul 2023 07:41:27 +0000 [thread overview] Message-ID: <bug-93768-4-qhZ3p4Z3Ri@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-93768-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93768 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jan Beulich <jbeulich@gcc.gnu.org>: https://gcc.gnu.org/g:607613e516670dd817e7467e774ed2e3440bdb21 commit r14-2309-g607613e516670dd817e7467e774ed2e3440bdb21 Author: Jan Beulich <jbeulich@suse.com> Date: Wed Jul 5 09:40:40 2023 +0200 x86: use VPTERNLOG for further bitwise two-vector operations All combinations of and, ior, xor, and not involving two operands can be expressed that way in a single insn. gcc/ PR target/93768 * config/i386/i386.cc (ix86_rtx_costs): Further special-case bitwise vector operations. * config/i386/sse.md (*iornot<mode>3): New insn. (*xnor<mode>3): Likewise. (*<nlogic><mode>3): Likewise. (andor): New code iterator. (nlogic): New code attribute. (ternlog_nlogic): Likewise. gcc/testsuite/ PR target/93768 * gcc.target/i386/avx512-binop-not-1.h: New. * gcc.target/i386/avx512-binop-not-2.h: New. * gcc.target/i386/avx512f-orn-si-zmm-1.c: New test. * gcc.target/i386/avx512f-orn-si-zmm-2.c: New test.
next prev parent reply other threads:[~2023-07-05 7:41 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-93768-4@http.gcc.gnu.org/bugzilla/> 2022-09-25 19:35 ` ak at gcc dot gnu.org 2023-06-08 16:51 ` jbeulich at suse dot com 2023-07-05 7:41 ` cvs-commit at gcc dot gnu.org [this message] 2023-07-05 7:41 ` 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-93768-4-qhZ3p4Z3Ri@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).