From: Nelson Chu <nelson.chu@sifive.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org, Jim Wilson <jimw@sifive.com>
Subject: Re: [PATCH 0/2] RISCV CSR register groups and aliases
Date: Fri, 27 Nov 2020 07:29:47 +0800 [thread overview]
Message-ID: <CAJYME4FrC8idTk_TVpeh-V69f6qZjPQ0i44cC4RFzRTFTJt5mA@mail.gmail.com> (raw)
In-Reply-To: <cover.1606392278.git.andrew.burgess@embecosm.com>
Hi Andrew,
Thank you very much for notifying us about these changes.
Nelson
On Thu, Nov 26, 2020 at 9:09 PM Andrew Burgess
<andrew.burgess@embecosm.com> wrote:
>
> Some changes to how register groups and aliases are managed for RISC-V
> CSRs.
>
> ---
>
> Andrew Burgess (2):
> gdb/riscv: place unknown csrs into the correct register groups
> gdb/riscv: remove csr aliases created with DECLARE_CSR_ALIAS
>
> gdb/ChangeLog | 12 ++++++
> gdb/riscv-tdep.c | 44 +++++++++++++--------
> gdb/testsuite/ChangeLog | 9 +++++
> gdb/testsuite/gdb.arch/riscv-tdesc-regs.exp | 41 +++++++++++++------
> 4 files changed, 77 insertions(+), 29 deletions(-)
>
> --
> 2.25.4
>
prev parent reply other threads:[~2020-11-26 23:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 13:09 Andrew Burgess
2020-11-26 13:09 ` [PATCH 1/2] gdb/riscv: place unknown csrs into the correct register groups Andrew Burgess
2020-11-27 22:38 ` Jim Wilson
2020-12-02 17:46 ` Andrew Burgess
2020-11-26 13:09 ` [PATCH 2/2] gdb/riscv: remove csr aliases created with DECLARE_CSR_ALIAS Andrew Burgess
2020-11-26 15:34 ` [PATCH 0/2] RISCV CSR register groups and aliases Luis Machado
2020-11-26 23:29 ` Nelson Chu [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=CAJYME4FrC8idTk_TVpeh-V69f6qZjPQ0i44cC4RFzRTFTJt5mA@mail.gmail.com \
--to=nelson.chu@sifive.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@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).