From: Jim Wilson <jimw@sifive.com>
To: Nelson Chu <nelson.chu@sifive.com>
Cc: Binutils <binutils@sourceware.org>,
Andrew Burgess <andrew.burgess@embecosm.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH v5 0/3] RISC-V: Support more rigorous check for CSR
Date: Fri, 21 Feb 2020 00:55:00 -0000 [thread overview]
Message-ID: <CAFyWVaZ1bgHwDd8z0PCsjLE7MsoJhWHZTW9Dp5-pbLjhcaobtQ@mail.gmail.com> (raw)
In-Reply-To: <1581502731-28327-1-git-send-email-nelson.chu@sifive.com>
On Wed, Feb 12, 2020 at 2:18 AM Nelson Chu <nelson.chu@sifive.com> wrote:
> * [PATCH v5 1/3] RISC-V: Support the ISA-dependent CSR checking.
> a. Add missing comments for each function.
> b. Add -march=rv32if option to the csr-dw-regnum test case.
> c. Report warning messages rather than error for the CSR cheking.
> d. Keep the consistent usage in gas/config/tc-riscv.c (from Andrew's suggestion)
> d-1. Change the 'typedef struct {...} riscv_csr_extra' to
> 'struct riscv_csr_extra {...}'.
> d-2. Use 'if (hash_error != NULL)' in init_opcode_hash and riscv_init_csr_hash, since
> hash_error is not a boolean.
>
> * [PATCH v5 2/3] RISC-V: Disable the CSR checking by default.
>
> * [PATCH v5 3/3] RISC-V: Support the read-only CSR checking.
This looks good. I fixed a comment typo in part 3, and rewrote the
ChangeLog entries a bit because you didn't mention all of the types,
variables, and functions modified by the patches. Andrew Burgess had
already approved the gdb parts, so I committed both the binutils and
gdb patches.
Jim
next prev parent reply other threads:[~2020-02-21 0:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 10:19 Nelson Chu
2020-02-12 10:19 ` [PATCH 1/3] RISC-V: Support the ISA-dependent CSR checking Nelson Chu
2020-02-12 10:19 ` [PATCH 3/3] RISC-V: Support the read-only " Nelson Chu
2020-02-12 10:19 ` [PATCH 2/3] RISC-V: Disable the CSR checking by default Nelson Chu
2020-02-21 0:55 ` Jim Wilson [this message]
2020-02-21 1:12 ` [PATCH v5 0/3] RISC-V: Support more rigorous check for CSR Nelson Chu
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=CAFyWVaZ1bgHwDd8z0PCsjLE7MsoJhWHZTW9Dp5-pbLjhcaobtQ@mail.gmail.com \
--to=jimw@sifive.com \
--cc=andrew.burgess@embecosm.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=nelson.chu@sifive.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).