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] Miss optimization for pandn
Date: Thu, 25 May 2023 08:50:56 +0000 [thread overview]
Message-ID: <bug-100711-4-Nu57XvSt7k@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 #11 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to jbeulich from comment #10)
> (In reply to Hongtao.liu from comment #9)
> > We don't have single instruction for V8HI/V16QImode broadcast without AVX2,
> > that's why the first splitter only have VI48_128.
>
> Does this matter? The splitters are about subsuming the "not". How the
> "vec_duplicate" is carried out isn't really relevant here, is it?
It's splitted to 2 patterns, but there's no V8HI/V16QImode define_insn for the
first pattern w/o AVX2, there will be ICE of unrecognisable insn.
17110 [(set (match_dup 3)
17111 (vec_duplicate:VI48_128 (match_dup 1)))
17112 (set (match_dup 0)
17113 (and:VI48_128 (not:VI48_128 (match_dup 3))
17114 (match_dup 2)))]
next prev parent reply other threads:[~2023-05-25 8:51 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 [this message]
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-Nu57XvSt7k@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).