From: Jeff Law <jeffreyalaw@gmail.com>
To: Lehua Ding <lehua.ding@rivai.ai>,
gcc-patches@gcc.gnu.org, richard.sandiford@arm.com
Cc: richard.guenther@gmail.com, juzhe.zhong@rivai.ai
Subject: Re: [PATCH 1/2] match.pd: Support combine cond_len_op + vec_cond similar to cond_op
Date: Wed, 27 Sep 2023 16:24:15 -0600 [thread overview]
Message-ID: <ba0a67bb-7955-4c42-bdfb-4e3d5b9d9f44@gmail.com> (raw)
In-Reply-To: <20230920130904.2329151-1-lehua.ding@rivai.ai>
On 9/20/23 07:09, Lehua Ding wrote:
> This patch adds combine cond_len_op and vec_cond to cond_len_op like
> cond_op.
>
> gcc/ChangeLog:
>
> * gimple-match.h (gimple_match_op::gimple_match_op):
> Add interfaces for more arguments.
> (gimple_match_op::set_op): Add interfaces for more arguments.
> * match.pd: Add support of combining cond_len_op + vec_cond
OK
jeff
next prev parent reply other threads:[~2023-09-27 22:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 13:09 Lehua Ding
2023-09-27 22:24 ` Jeff Law [this message]
2023-10-31 6:19 ` Lehua Ding
2023-10-31 6:48 ` Andrew Pinski
2023-10-31 7:08 ` Lehua Ding
2023-10-31 7:16 ` Andrew Pinski
2023-10-31 8:20 ` Lehua Ding
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=ba0a67bb-7955-4c42-bdfb-4e3d5b9d9f44@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=lehua.ding@rivai.ai \
--cc=richard.guenther@gmail.com \
--cc=richard.sandiford@arm.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).