From: Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCHv2] gdb/riscv: add support for vector registers in target descriptions
Date: Mon, 21 Jun 2021 14:41:16 +0300 [thread overview]
Message-ID: <83wnqntpgj.fsf@gnu.org> (raw)
In-Reply-To: <20210621110420.GB2568@embecosm.com> (message from Andrew Burgess on Mon, 21 Jun 2021 12:04:20 +0100)
> Date: Mon, 21 Jun 2021 12:04:20 +0100
> From: Andrew Burgess <andrew.burgess@embecosm.com>
> Cc: palmer@dabbelt.com, nelson.chu@sifive.com, jimw@sifive.com,
> jhb@freebsd.org, Eli Zaretskii <eliz@gnu.org>
>
> Thanks for feedback on v1.
>
> I agree that there is a very small risk that the vector register set
> could change for the final version of the spec, but like you both seem
> to say, this seems unlikely.
>
> And even if it did change I don't think changing the requirements of
> the feature for a later release of GDB would be that bad.
>
> So, I'm proposing that once this has had a doc review, I'll get this
> merged, hopefully in time for the next release (of GDB).
>
> In v2:
>
> - Fixed the f-register/v-register typo that Jim pointed out,
> - Added documentation of the new feature to the manual,
> - Added a NEWS entry,
> - Updated the commit message to mention that the vector extension is
> still in draft.
Thanks, the documentation parts are okay.
prev parent reply other threads:[~2021-06-21 11:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 9:46 [PATCH] " Andrew Burgess
2021-05-05 21:05 ` Jim Wilson
2021-05-06 7:26 ` Palmer Dabbelt
2021-06-21 11:04 ` [PATCHv2] " Andrew Burgess
2021-06-21 11:41 ` Eli Zaretskii via Gdb-patches [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=83wnqntpgj.fsf@gnu.org \
--to=gdb-patches@sourceware.org \
--cc=andrew.burgess@embecosm.com \
--cc=eliz@gnu.org \
/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