Re: [PATCH] docs: Clarify gdb remote protocol AArch64 SVE and SME handling

[Eli Zaretskii <eliz@gnu.org>]

> From: Peter Maydell <peter.maydell@linaro.org>
> Cc: Thiago Jung Bauermann <thiago.bauermann@linaro.org>,
>  Luis <luis.machado.foss@gmail.com>,
>  Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
> Date: Thu, 29 Jan 2026 18:11:21 +0000
> 
> The documentation of the AArch64 target features for the gdb remote
> protocol has some areas where it is unclear about SVE and SME:
> 
>  * it doesn't say what to do if the target has only SME
> 
>  * it isn't clear about what the org.gnu.gdb.aarch64.sve vector
>    register size should be when both SME and SVE are present
> 
> Clarify/correct the documentation:
> 
>  * org.gnu.gdb.aarch64.sve is effectively "the feature for the z
>    vector registers", and must be provided even when the target only
>    implements SME (because the z registers exist in an SME only CPU)
> 
>  * the z register size and the 'vg' pseudoregister in
>    org.gnu.gdb.aarch64.sve follow the architectural "effective SVE
>    vector length", which might be either the non-streaming SVE vector
>    length or the streaming SVE vector length
> 
> Reviewed-by: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
> ---
>  gdb/doc/gdb.texinfo | 18 +++++++++++++++++-
>  1 file changed, 17 insertions(+), 1 deletion(-)

Thanks.

> +@samp{vg} represents the size of the @samp{z} registers, and is what
> +the Arm architecture defines as the ``Effective SVE vector length''. That

I suggest to put the terminology you mention in @dfn instead of
quoting it.  It will be formatted as a quoted string in Info, but will
look much prettier in HTML and PDF formats.

Also, please leave two spaces between sentences, here and elsewhere in
the patch.

Reviewed-By: Eli Zaretskii <eliz@gnu.org>