From: "Feng Wang" <wangfeng@eswincomputing.com>
To: "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
gcc-patches <gcc-patches@gcc.gnu.org>
Cc: kito.cheng <kito.cheng@gmail.com>, palmer <palmer@dabbelt.com>,
"Jeff Law" <jeffreyalaw@gmail.com>
Subject: Re: [PATCH] RISC-V: Optimize zbb ins sext.b and sext.h in rv64
Date: Fri, 24 Mar 2023 14:13:40 +0800 [thread overview]
Message-ID: <202303241413404628257@eswincomputing.com> (raw)
In-Reply-To: <D8CDCA89C9C276DA+20230324104549469046125@rivai.ai>
Hi Juzhe,
Thank you for your reply, I'm really doing some optimization work right now.
I am very interested in the question you have raised, and I will take the time to try to optimize it.
I hope I can communicate with you and learn from you more in the future.
Thanks.
next prev parent reply other threads:[~2023-03-24 6:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 2:45 juzhe.zhong
2023-03-24 6:13 ` Feng Wang [this message]
2023-03-25 18:18 ` Jeff Law
2023-03-27 1:32 ` Feng Wang
2023-03-27 2:05 ` Jeff Law
-- strict thread matches above, loose matches on Subject: below --
2023-03-24 1:53 Feng Wang
2023-04-22 0:08 ` Jeff Law
2023-04-22 0:13 ` 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=202303241413404628257@eswincomputing.com \
--to=wangfeng@eswincomputing.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.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).