public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <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 02:00:27 +0000 [thread overview]
Message-ID: <bug-101989-4-XMAV3iikp7@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
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2021-08-20
Status|UNCONFIRMED |NEW
Severity|normal |enhancement
Ever confirmed|0 |1
Host|x86_64-pc-linux-gnu |
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed. You might be able to handle it with a match_dup instead of needing
a post_reload splitter to match the the one reg that needs to be the same.
next prev parent reply other threads:[~2021-08-20 2:00 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 ` [Bug target/101989] " crazylht at gmail dot com
2021-08-20 2:00 ` pinskia at gcc dot gnu.org [this message]
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-XMAV3iikp7@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).