From: "Lehua Ding" <lehua.ding@rivai.ai>
To: 钟居哲 <juzhe.zhong@rivai.ai>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] RISC-V: Fix PR 110119
Date: Wed, 14 Jun 2023 19:07:16 +0800 [thread overview]
Message-ID: <tencent_6584C62A4395DC6C4D76B493@qq.com> (raw)
In-Reply-To: <479F6A3F68A79675+2023061418525919688041@rivai.ai>
[-- Attachment #1: Type: text/plain, Size: 163 bytes --]
Resubmitted a new, more standardized patch(bellow is the new patch link), thanks.
https://gcc.gnu.org/pipermail/gcc-patches/2023-June/621683.html
prev parent reply other threads:[~2023-06-14 11:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 10:34 Lehua Ding
2023-06-14 10:52 ` juzhe.zhong
2023-06-14 11:07 ` 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=tencent_6584C62A4395DC6C4D76B493@qq.com \
--to=lehua.ding@rivai.ai \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
/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).