Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
* [PATCH] gdb/doc: The RISC-V vector registers didn't change
@ 2023-01-26 23:12 Palmer Dabbelt
  2023-01-27  7:21 ` Eli Zaretskii via Gdb-patches
  0 siblings, 1 reply; 3+ messages in thread
From: Palmer Dabbelt @ 2023-01-26 23:12 UTC (permalink / raw)
  To: gdb-patches; +Cc: Palmer Dabbelt

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] gdb/doc: The RISC-V vector registers didn't change
  2023-01-26 23:12 [PATCH] gdb/doc: The RISC-V vector registers didn't change Palmer Dabbelt
@ 2023-01-27  7:21 ` Eli Zaretskii via Gdb-patches
  2023-02-23 21:52   ` Palmer Dabbelt
  0 siblings, 1 reply; 3+ messages in thread
From: Eli Zaretskii via Gdb-patches @ 2023-01-27  7:21 UTC (permalink / raw)
  To: Palmer Dabbelt; +Cc: gdb-patches

> Date: Thu, 26 Jan 2023 15:12:00 -0800
> Cc: Palmer Dabbelt <palmer@rivosinc.com>
> From: Palmer Dabbelt <palmer@rivosinc.com>
> 
> 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(-)

This is OK, thanks.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] gdb/doc: The RISC-V vector registers didn't change
  2023-01-27  7:21 ` Eli Zaretskii via Gdb-patches
@ 2023-02-23 21:52   ` Palmer Dabbelt
  0 siblings, 0 replies; 3+ messages in thread
From: Palmer Dabbelt @ 2023-02-23 21:52 UTC (permalink / raw)
  To: eliz; +Cc: gdb-patches

On Thu, 26 Jan 2023 23:21:09 PST (-0800), eliz@gnu.org wrote:
>> Date: Thu, 26 Jan 2023 15:12:00 -0800
>> Cc: Palmer Dabbelt <palmer@rivosinc.com>
>> From: Palmer Dabbelt <palmer@rivosinc.com>
>>
>> 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(-)
>
> This is OK, thanks.

Committed, thanks!

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2023-02-23 21:52 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-01-26 23:12 [PATCH] gdb/doc: The RISC-V vector registers didn't change Palmer Dabbelt
2023-01-27  7:21 ` Eli Zaretskii via Gdb-patches
2023-02-23 21:52   ` Palmer Dabbelt

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox