From: Nelson Chu <nelson.chu@sifive.com>
To: binutils@sourceware.org, jimw@sifive.com, andrew.burgess@embecosm.com
Subject: [PATCH v5 0/3] RISC-V: Support more rigorous check for CSR
Date: Wed, 12 Feb 2020 10:19:00 -0000 [thread overview]
Message-ID: <1581502731-28327-1-git-send-email-nelson.chu@sifive.com> (raw)
Hi binutils,
I get some feedbacks from Andrew Burgess of gdb side. Therefroe I update the
series of patches. There are some differences between v5 version and v3 version
that Jim reviewed, shown as follows:
1. Implement the draft of CSR spec is inadvisable, so I remove the first patch
of v3 version.
2. Reorder the patches. Move the patch "RISC-V: Disable the CSR checking by
default" to the second patch.
The detailed of patches:
* [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.
Thanks
Nelson
next reply other threads:[~2020-02-12 10:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 10:19 Nelson Chu [this message]
2020-02-12 10:19 ` [PATCH 1/3] RISC-V: Support the ISA-dependent CSR checking Nelson Chu
2020-02-12 10:19 ` [PATCH 2/3] RISC-V: Disable the CSR checking by default Nelson Chu
2020-02-12 10:19 ` [PATCH 3/3] RISC-V: Support the read-only CSR checking Nelson Chu
2020-02-21 0:55 ` [PATCH v5 0/3] RISC-V: Support more rigorous check for CSR Jim Wilson
2020-02-21 1:12 ` 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=1581502731-28327-1-git-send-email-nelson.chu@sifive.com \
--to=nelson.chu@sifive.com \
--cc=andrew.burgess@embecosm.com \
--cc=binutils@sourceware.org \
--cc=jimw@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).