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] RISC-V: Update CSR to privileged spec 1.11.
Date: Mon, 30 Mar 2020 13:09:02 -0700 [thread overview]
Message-ID: <CAFyWVaZmJwDPvHO9Xootd0TfRCxNsgbAJ-OkKGi1xtkcpD-BLA@mail.gmail.com> (raw)
In-Reply-To: <1584006519-29776-2-git-send-email-nelson.chu@sifive.com>
On Thu, Mar 12, 2020 at 2:48 AM Nelson Chu <nelson.chu@sifive.com> wrote:
> gas/
> * testsuite/gas/riscv/alias-csr.d: Move this to priv-reg-pseudo.
> * testsuite/gas/riscv/alias-csr.s: Likewise.
> * testsuite/gas/riscv/no-aliases-csr.d: Move this
> to priv-reg-pseudo-noalias.
> * testsuite/gas/riscv/bad-csr.d: Rename to priv-reg-fail-nonexistent.
> * testsuite/gas/riscv/bad-csr.l: Likewise.
> * testsuite/gas/riscv/bad-csr.s: Likewise.
> * testsuite/gas/riscv/satp.d: Removed. Already included in priv-reg.
> * testsuite/gas/riscv/satp.s: Likewise.
> * testsuite/gas/riscv/priv-reg-pseudo.d: New testcase for all pseudo
> csr instruction, including alias-csr testcase.
> * testsuite/gas/riscv/priv-reg-pseudo.s: Likewise.
> * testsuite/gas/riscv/priv-reg-pseudo-noalias.d: New testcase for all
> pseudo instruction with objdump -Mno-aliases.
> * testsuite/gas/riscv/priv-reg-fail-nonexistent.d: New testcase.
> * testsuite/gas/riscv/priv-reg-fail-nonexistent.l: Likewise.
> * testsuite/gas/riscv/priv-reg-fail-nonexistent.s: Likewise.
> * testsuite/gas/riscv/priv-reg.d: Update CSR to 1.11.
> * testsuite/gas/riscv/priv-reg.s: Likewise.
> * testsuite/gas/riscv/priv-reg-fail-rv32-only.l: Likewise.
> * testsuite/gas/riscv/csr-dw-regnums.d: Likewise.
> * testsuite/gas/riscv/csr-dw-regnums.s: Likewise.
>
> include/
> * opcode/riscv-opc.h: Update CSR to 1.11.
>
> gdb/
> * features/riscv/32bit-csr.xml: Regenerated.
> * features/riscv/64bit-csr.xml: Regenerated.
Committed and pushed. I approved the binutils parts and Andrew
Burgess approved the gdb parts.
Jim
next parent reply other threads:[~2020-03-30 20:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1584006519-29776-1-git-send-email-nelson.chu@sifive.com>
[not found] ` <1584006519-29776-2-git-send-email-nelson.chu@sifive.com>
2020-03-30 20:09 ` Jim Wilson [this message]
2020-03-31 1:01 ` Nelson Chu
2020-03-12 10:00 [0/1] RISC-V: Update CSR to priv 1.11 Nelson Chu
2020-03-12 10:00 ` [PATCH] RISC-V: Update CSR to privileged spec 1.11 Nelson Chu
2020-03-24 8:51 ` Andrew Burgess
2020-03-24 9:11 ` 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=CAFyWVaZmJwDPvHO9Xootd0TfRCxNsgbAJ-OkKGi1xtkcpD-BLA@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).