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: Wed, 05 Jul 2023 07:49:41 +0000	[thread overview]
Message-ID: <bug-100711-4-7JeHSk5P4O@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 #15 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:e007369c8b67bcabd57c4fed8cff2a6db82e78e6

commit r14-2314-ge007369c8b67bcabd57c4fed8cff2a6db82e78e6
Author: Jan Beulich <jbeulich@suse.com>
Date:   Wed Jul 5 09:49:16 2023 +0200

    x86: yet more PR target/100711-like splitting

    Following two-operand bitwise operations, add another splitter to also
    deal with not followed by broadcast all on its own, which can be
    expressed as simple embedded broadcast instead once a broadcast operand
    is actually permitted in the respective insn. While there also permit
    a broadcast operand in the corresponding expander.

    gcc/

            PR target/100711
            * config/i386/sse.md: New splitters to simplify
            not;vec_duplicate as a singular vpternlog.
            (one_cmpl<mode>2): Allow broadcast for operand 1.
            (<mask_codefor>one_cmpl<mode>2<mask_name>): Likewise.

    gcc/testsuite/

            PR target/100711
            * gcc.target/i386/pr100711-6.c: New test.

      parent reply	other threads:[~2023-07-05  7:49 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
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 [this message]

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-7JeHSk5P4O@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: link
Be 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).