From: Jeff Law <jeffreyalaw@gmail.com>
To: Lehua Ding <lehua.ding@rivai.ai>, Edwin Lu <ewlu@rivosinc.com>,
gcc-patches@gcc.gnu.org
Cc: gnu-toolchain@rivosinc.com
Subject: Re: [PATCH] RISC-V: Finish Typing Un-Typed Instructions and Turn on Assert
Date: Tue, 19 Sep 2023 11:23:06 -0600 [thread overview]
Message-ID: <9afa97e7-8318-48bb-bcef-b1fccab27b91@gmail.com> (raw)
In-Reply-To: <9AB2FEB681FBC749+985472a7-fe60-44c9-8b59-132af9453108@rivai.ai>
On 9/18/23 01:29, Lehua Ding wrote:
> Hi Jeff,
>
> Thank you for your comments, I'm not fully convinced yet but I will
> follow the current rules. I won't dwell on this for now.
Sounds reasonable. Of all the things we need to do, this isn't that big :-)
jeff
prev parent reply other threads:[~2023-09-19 17:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 22:52 Edwin Lu
2023-09-12 0:49 ` Jeff Law
2023-09-15 22:51 ` [Committed] " Edwin Lu
2023-09-15 22:51 ` Edwin Lu
2023-09-12 2:33 ` [PATCH] " Lehua Ding
2023-09-12 3:00 ` Jeff Law
2023-09-12 3:17 ` Lehua Ding
2023-09-12 3:47 ` Jeff Law
2023-09-12 6:18 ` Lehua Ding
2023-09-17 13:46 ` Jeff Law
2023-09-18 7:29 ` Lehua Ding
2023-09-19 17:23 ` Jeff Law [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=9afa97e7-8318-48bb-bcef-b1fccab27b91@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=ewlu@rivosinc.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gnu-toolchain@rivosinc.com \
--cc=lehua.ding@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).