From: "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Cc: kito.cheng <kito.cheng@gmail.com>, palmer <palmer@dabbelt.com>,
jeffreyalaw <jeffreyalaw@gmail.com>,
wangfeng <wangfeng@eswincomputing.com>
Subject: [PATCH] RISC-V: Optimize zbb ins sext.b and sext.h in rv64
Date: Fri, 24 Mar 2023 10:45:50 +0800 [thread overview]
Message-ID: <D8CDCA89C9C276DA+20230324104549469046125@rivai.ai> (raw)
[-- Attachment #1: Type: text/plain, Size: 424 bytes --]
Sounds like you are looking at redundant extension problem in RISC-V port.
This is the issue I want to fix but I don't find the time to do that.
My first impression is that we need to fix redundant extension in "ree" PASS.
I am not sure.
Base on you are looking at this kind of issues, would you mind looking at this issue?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108016
Thanks.
juzhe.zhong@rivai.ai
next reply other threads:[~2023-03-24 2:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 2:45 juzhe.zhong [this message]
2023-03-24 6:13 ` Feng Wang
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=D8CDCA89C9C276DA+20230324104549469046125@rivai.ai \
--to=juzhe.zhong@rivai.ai \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=kito.cheng@gmail.com \
--cc=palmer@dabbelt.com \
--cc=wangfeng@eswincomputing.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).