Re: [PATCH,v3 17/17] [gdb/docs] sme: Document SME registers and features

[Luis Machado <luis.machado@arm.com>]

[-- Attachment #1: Type: text/plain, Size: 1291 bytes --]

On 4/26/23 17:10, Eli Zaretskii wrote:
>> Date: Wed, 26 Apr 2023 16:00:44 +0100
>> Cc: gdb-patches@sourceware.org
>> From: Luis Machado <luis.machado@arm.com>
>>
>>>> +@item
>>>> +@samp{za} is a register represented by a vector of @code{SVL} x @code{SVL}
>>>                                                         ^^^^^^^^^^^^^^^^^^^^^^^
>>> This should use @var, not @code.  Also, I'd remove the whitespace
>>> around "x".
>>
>> Fixed. But I used spaces between "x" and the two @var entries because it gets rendered as a single
>> block of characters like svlxsvl.
> 
> That doesn't seem possible, since @var produces a different typeface:
> slanted in the printed version and CAPS in the Info versions.  Where
> did you see svlxsvl?

In the PDF. I mean, it is slanted with the use of @var{}, but not that noticeable.

See the attached pdf. I also attached the info file.

I noticed the info file capitalizes @var{}, which might not be ideal?

For instance, look at this paragraph (from the pdf):

"The za register is a 2-dimensional square svlxsvl matrix of bytes. To simplify the rep-
resentation and access to the za register in gdb, it is defined as a vector of svlxsvl bytes."

The first "svlxsvl" is using @var{}x@var{}. The second one is wrapped in @code{}, so @code{@var{}x@var{}}.

[-- Attachment #2: gdb.pdf --]
[-- Type: application/pdf, Size: 3013820 bytes --]

[-- Attachment #3: gdb.info --]
[-- Type: application/x-info, Size: 2706947 bytes --]