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/101989] Fail to optimize (a & b) | (c & ~b) to vpternlog instruction.
Date: Fri, 20 Aug 2021 01:50:09 +0000	[thread overview]
Message-ID: <bug-101989-4-Zp7bv7Eggi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101989-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101989

--- Comment #1 from Hongtao.liu <crazylht at gmail dot com> ---
Another testcase is from pr91796

    __m256d copysign2_pd(__m256d from, __m256d to) {
        auto a = _mm256_castpd_si256(from);
        auto avx_signbit =
_mm256_castsi256_pd(_mm256_slli_epi64(_mm256_cmpeq_epi64(a, a), 63));
        return _mm256_or_pd(_mm256_and_pd(avx_signbit, from),
_mm256_andnot_pd(avx_signbit, to)); // (avx_signbit & from) | (~avx_signbit &
to)
    }


Failed to match this instruction:
(set (reg:V4DF 93)
    (ior:V4DF (and:V4DF (reg:V4DF 89)
            (reg:V4DF 95))
        (and:V4DF (not:V4DF (reg:V4DF 89))
            (reg:V4DF 96))))
Failed to match this instruction:

  reply	other threads:[~2021-08-20  1:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-20  1:46 [Bug target/101989] New: " crazylht at gmail dot com
2021-08-20  1:50 ` crazylht at gmail dot com [this message]
2021-08-20  2:00 ` [Bug target/101989] " pinskia at gcc dot gnu.org
2021-08-24  9:45 ` cvs-commit at gcc dot gnu.org
2021-08-24 10:34 ` cvs-commit at gcc dot gnu.org
2021-08-24 10:35 ` crazylht at gmail dot com
2021-08-25  1:57 ` cvs-commit at gcc dot gnu.org
2021-08-25  2:32 ` pinskia at gcc dot gnu.org
2021-11-04  8:10 ` cvs-commit at gcc dot gnu.org
2022-09-25 19:35 ` ak 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-101989-4-Zp7bv7Eggi@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).