From: Lehua Ding <lehua.ding@rivai.ai>
To: "juzhe.zhong" <juzhe.zhong@rivai.ai>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"kito.cheng@gmail.com" <kito.cheng@gmail.com>,
"rdapp.gcc@gmail.com" <rdapp.gcc@gmail.com>,
"palmer@rivosinc.com" <palmer@rivosinc.com>,
"jeffreyalaw@gmail.com" <jeffreyalaw@gmail.com>
Subject: Re: [PATCH] RISC-V: Fixed ICE caused by missing operand
Date: Wed, 20 Sep 2023 14:16:19 +0800 [thread overview]
Message-ID: <1CF5E708081E4E13+81c0e729-bc2b-4937-a537-efa1b3683f6c@rivai.ai> (raw)
In-Reply-To: <2F27A0EC795BA91C+FBDD6248-6460-446A-8BA6-B3A03027755A@rivai.ai>
Committed, thanks Juzhe.
On 2023/9/20 14:03, juzhe.zhong wrote:
> LGTM
> ---- Replied Message ----
> From Lehua Ding<lehua.ding@rivai.ai> <mailto:lehua.ding@rivai.ai>
> Date 09/20/2023 13:39
> To gcc-patches@gcc.gnu.org<gcc-patches@gcc.gnu.org>
> <mailto:gcc-patches@gcc.gnu.org>
> Cc juzhe.zhong@rivai.ai<juzhe.zhong@rivai.ai> <mailto:juzhe.zhong@rivai.ai>,
> kito.cheng@gmail.com<kito.cheng@gmail.com> <mailto:kito.cheng@gmail.com>,
> rdapp.gcc@gmail.com<rdapp.gcc@gmail.com> <mailto:rdapp.gcc@gmail.com>,
> palmer@rivosinc.com<palmer@rivosinc.com> <mailto:palmer@rivosinc.com>,
> jeffreyalaw@gmail.com<jeffreyalaw@gmail.com> <mailto:jeffreyalaw@gmail.com>,
> lehua.ding@rivai.ai<lehua.ding@rivai.ai> <mailto:lehua.ding@rivai.ai>
> Subject [PATCH] RISC-V: Fixed ICE caused by missing operand
>
--
Best,
Lehua
prev parent reply other threads:[~2023-09-20 6:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 5:39 Lehua Ding
[not found] ` <2F27A0EC795BA91C+FBDD6248-6460-446A-8BA6-B3A03027755A@rivai.ai>
2023-09-20 6:16 ` Lehua Ding [this message]
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=1CF5E708081E4E13+81c0e729-bc2b-4937-a537-efa1b3683f6c@rivai.ai \
--to=lehua.ding@rivai.ai \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=palmer@rivosinc.com \
--cc=rdapp.gcc@gmail.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).