From: Jeff Law <jeffreyalaw@gmail.com>
To: Kito Cheng <kito.cheng@gmail.com>, Palmer Dabbelt <palmer@dabbelt.com>
Cc: lidie@eswincomputing.com, gcc-patches@gcc.gnu.org, jeffeyalaw@gmail.com
Subject: Re: [PATCH] RISC-V: Remove the redundant expressions in the and<mode>3.
Date: Thu, 13 Jul 2023 20:52:08 -0600 [thread overview]
Message-ID: <1db1c7ea-d3a5-6a54-e4a2-8e4b644e286e@gmail.com> (raw)
In-Reply-To: <CA+yXCZDayiNHQ-XvvPQMNCd7jT4nBrqziWmiCfEoXLwU56Q2_A@mail.gmail.com>
On 7/13/23 20:41, Kito Cheng via Gcc-patches wrote:
> Expanding without DONE or FAIL will leave the pattern as well, so this
> patch is fine IMO, so this patch LGTM, but anyway I will test this and
> commit if passed :)
THanks. I looked fine to me, but I wasn't going to have the time to
commit/push it tonight.
jeff
next prev parent reply other threads:[~2023-07-14 2:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 2:02 Die Li
2023-07-14 2:34 ` Palmer Dabbelt
2023-07-14 2:41 ` Kito Cheng
2023-07-14 2:44 ` Palmer Dabbelt
2023-07-14 2:50 ` Jeff Law
2023-07-14 2:52 ` Jeff Law [this message]
2023-07-14 12:32 ` Kito Cheng
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=1db1c7ea-d3a5-6a54-e4a2-8e4b644e286e@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffeyalaw@gmail.com \
--cc=kito.cheng@gmail.com \
--cc=lidie@eswincomputing.com \
--cc=palmer@dabbelt.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).