public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@rivosinc.com>
To: gdb-patches@sourceware.org
Cc: Palmer Dabbelt <palmer@rivosinc.com>
Subject: [PATCH] gdb/doc: The RISC-V vector registers didn't change
Date: Thu, 26 Jan 2023 15:12:00 -0800	[thread overview]
Message-ID: <20230126231200.5549-1-palmer@rivosinc.com> (raw)

When we merged the GDB vector register support we did it a bit early,
just eating the risk in the very unlikely case that the vector register
names changed.  They didn't, so we can now remove the caveat in the docs
that they might.
---
 gdb/doc/gdb.texinfo | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 9c0018ea5c1..10d94f5c8ad 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -47765,11 +47765,7 @@ other floating point hardware.
 
 The @samp{org.gnu.gdb.riscv.vector} feature is optional.  If present,
 it should contain registers @samp{v0} through @samp{v31}, all of which
-must be the same size.  These requirements are based on the v0.10
-draft vector extension, as the vector extension is not yet final.  In
-the event that the register set of the vector extension changes for
-the final specification, the requirements given here could change for
-future releases of @value{GDBN}.
+must be the same size.
 
 @node RX Features
 @subsection RX Features
-- 
2.39.1


             reply	other threads:[~2023-01-26 23:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-26 23:12 Palmer Dabbelt [this message]
2023-01-27  7:21 ` Eli Zaretskii
2023-02-23 21:52   ` Palmer Dabbelt

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=20230126231200.5549-1-palmer@rivosinc.com \
    --to=palmer@rivosinc.com \
    --cc=gdb-patches@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).