From: Jeff Law <jeffreyalaw@gmail.com>
To: liuhongt <hongtao.liu@intel.com>, gcc-patches@gcc.gnu.org
Cc: crazylht@gmail.com, hjl.tools@gmail.com
Subject: Re: [PATCH] Canonicalize vec_merge when mask is constant.
Date: Sun, 30 Apr 2023 13:37:01 -0600 [thread overview]
Message-ID: <1995c643-47bb-6376-ce72-d5440e59196b@gmail.com> (raw)
In-Reply-To: <20230420035821.4113007-1-hongtao.liu@intel.com>
On 4/19/23 21:58, liuhongt via Gcc-patches wrote:
> Use swap_communattive_operands_p for canonicalization. When both value
> has same operand precedence value, then first bit in the mask should
> select first operand.
>
> The canonicalization should help backends for pattern match. .i.e. x86
> backend has lots of vec_merge patterns, combine will create any form
> of vec_merge(mask, or inverted mask), then backend need to add 2
> patterns to match exact 1 instruction. The canonicalization can
> simplify 2 patterns to 1.
>
> Bootstrapped and regtested on x86_64-pc-linux-gnu{-m32,}, aarch64-linux-gnu.
> Ok for trunk?
>
> gcc/ChangeLog:
>
> * combine.cc (maybe_swap_commutative_operands): Canonicalize
> vec_merge when mask is constant.
ISTM that if we're going to call this the canonical form, then we should
document it in rtl.texi.
Otherwise it looks pretty good to me. So let's get the docs updated and
get this installed.
jeff
next prev parent reply other threads:[~2023-04-30 19:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 3:58 liuhongt
2023-04-30 19:37 ` Jeff Law [this message]
2023-05-04 2:49 ` Hongtao Liu
2023-05-04 3:25 ` [PATCH v2] " liuhongt
2023-05-05 23:34 ` Jeff Law
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=1995c643-47bb-6376-ce72-d5440e59196b@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=crazylht@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=hongtao.liu@intel.com \
/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).