Re: [PATCH v3 6/6] gdb/doc: Document AArch64 FPMR support

[Ezra Sitorus <ezra.sitorus@arm.com>]

Hi Eli,

On Tue, Oct 21, 2025 at 11:35:51AM -0400, Eli Zaretskii wrote:
> > --- a/gdb/doc/gdb.texinfo
> > +++ b/gdb/doc/gdb.texinfo
> > @@ -27080,6 +27080,26 @@ Program received signal SIGSEGV, Segmentation fault
> >  Guarded Control Stack error.
> >  @end smallexample
> >  
> > +@subsubsection AArch64 Floating Point Mode Register
> > +@cindex Floating Point Mode Register, AArch64
> > +@cindex FPMR, AArch64
> 
> Index entries should preferably not us upper-case letters, so that
> their sorting does not depend on locale-specific rules.  So please use
> upper-case letters only in acronyms.
> 

I don't mind changing it to lowercase, but the other AArch64 entries use upper case
as well, e.g.

@subsubsection AArch64 Memory Tagging Extension
@cindex Memory Tagging Extension, AArch64
@cindex MTE, AArch64

> > +When @value{GDBN} is debugging the AArch64 architecture and the Floating Point
> > +Mode Register (FPMR) is available, then @value{GDBN} will make the @code{fpmr}
> > +available. This register determines the behaviour of FP8 instructions.
>             ^^
> Our conventions are to leave two spaces between sentences (it looks
> better in print).
> 

Yep, forgot about this one! I'll wait for comments on the other patches before sending
the fix for this.

> > @itemize @minus
> > @item
> > @samp{fpmr}, the tag control register.  It is represented as if it were a 64-bit
> > register with a custom flags type.
> > @end itemize

I've also noticed that there is an error here from copy-and-paste. It should be floating
mode register.

Ezra