Re: [PATCH 21/23] Document new "x" and "print" memory tagging extensions

[Eli Zaretskii <eliz@gnu.org>]

> From: Luis Machado <luis.machado@linaro.org>
> Cc: gdb-patches@sourceware.org, Alan.Hayward@arm.com,
>  catalin.marinas@arm.com, david.spickett@linaro.org
> Date: Fri, 17 Jul 2020 11:20:33 -0300
> 
> >> +The @code{print} and @code{x} commands will display tag information when
> > 
> > And here please add a cross-reference to the nodes that describe the
> > 'print' and 'x' commands.
> > 
> 
> I added "@cindex Data" (for print) and "@cindex Memory" (for x) locally.

Not @cindex, @xref.

> >> +The @code{print} command will automatically attempt to validate the logical
> >> +tag against the allocation tag for pointers and addresses, and will display
> >> +a message in case of failure.
> >> +
> >> +The @code{x} command has a @code{m} modifier.  When present, this modifier
> >> +will make the @code{x} command output allocation tag information for a given
> >> +memory region that is being examined.
> > 
> > These should be in the sections that describe these commands, not
> > here.  The idea is to have everything about each command in a single
> > place, and then point there via cross-references from related places.
> > 
> > Thanks.
> > 
> 
> That makes sense. I wanted to make it obvious that memory tagging 
> provided some extra functionality to "print" and "x".
> 
> I suppose I'll just remove these two blocks since their content is 
> already described in both commands, although with slightly different text.

OK.