gdb/doc: The RISC-V vector registers didn't change
Commit Message
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(-)
Comments
> 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.
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!
@@ -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