public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Nelson Chu <nelson.chu@sifive.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org, Jim Wilson <jimw@sifive.com>,
	 Tom Tromey <tom@tromey.com>, Palmer Dabbelt <palmer@dabbelt.com>
Subject: Re: [PATCH 0/8] RISC-V target description and register handling fixes
Date: Wed, 17 Jun 2020 09:31:19 +0800	[thread overview]
Message-ID: <CAJYME4G2zrd_6w27Sw9h89aSfdSS5tKEUa65=QsviwfG7AxSLg@mail.gmail.com> (raw)
In-Reply-To: <cover.1592327296.git.andrew.burgess@embecosm.com>

Hi Andrew,

These are great!  Thank you, Jim and Tom very much.  You make the CSR
support more sense now.  The code seems to be changed dramatically.  I
will spend time to figure them out, and then see what needs to be
modified in binutils, including my recent patch to support the missing
debug CSR.

Thanks
Nelson

On Wed, Jun 17, 2020 at 1:14 AM Andrew Burgess
<andrew.burgess@embecosm.com> wrote:
>
> This series includes a mixed bag of changes around RISC-V's target
> description and general register handling.  This includes a fix for an
> issue Tom reported here:
>
>   https://sourceware.org/pipermail/gdb-patches/2020-June/169323.html
>
> Though most of the changes are RISC-V only, patch #6 does make a
> change to the generic target description handling code so is probably
> worth additional review.
>
> Feedback welcome,
>
> Thanks,
> Andrew
>
> ---
>
> Andrew Burgess (8):
>   gdb/riscv: Improved register alias name creation
>   gdb/riscv: Fix whitespace error
>   gdb/riscv: Take CSR names from target description
>   gdb/riscv: Remove CSR feature file
>   gdb/riscv: Improve support for matching against target descriptions
>   gdb: Extend target description processing of unknown registers
>   gdb/riscv: Record information about unknown tdesc registers
>   gdb/riscv: Loop over all registers for 'info all-registers'

  parent reply	other threads:[~2020-06-17  1:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-16 17:14 Andrew Burgess
2020-06-16 17:14 ` [PATCH 1/8] gdb/riscv: Improved register alias name creation Andrew Burgess
2020-06-18 20:36   ` Tom Tromey
2020-06-16 17:14 ` [PATCH 2/8] gdb/riscv: Fix whitespace error Andrew Burgess
2020-06-16 17:14 ` [PATCH 3/8] gdb/riscv: Take CSR names from target description Andrew Burgess
2020-06-16 17:14 ` [PATCH 4/8] gdb/riscv: Remove CSR feature file Andrew Burgess
2020-06-16 17:14 ` [PATCH 5/8] gdb/riscv: Improve support for matching against target descriptions Andrew Burgess
2020-06-16 17:14 ` [PATCH 6/8] gdb: Extend target description processing of unknown registers Andrew Burgess
2020-06-16 17:14 ` [PATCH 7/8] gdb/riscv: Record information about unknown tdesc registers Andrew Burgess
2020-06-16 17:14 ` [PATCH 8/8] gdb/riscv: Loop over all registers for 'info all-registers' Andrew Burgess
2020-06-17  1:31 ` Nelson Chu [this message]
2020-06-18 20:45 ` [PATCH 0/8] RISC-V target description and register handling fixes Tom Tromey
2020-06-18 20:54   ` Andrew Burgess

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='CAJYME4G2zrd_6w27Sw9h89aSfdSS5tKEUa65=QsviwfG7AxSLg@mail.gmail.com' \
    --to=nelson.chu@sifive.com \
    --cc=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jimw@sifive.com \
    --cc=palmer@dabbelt.com \
    --cc=tom@tromey.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).