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

[Eli Zaretskii <eliz@gnu.org>]

> Date: Wed, 15 Jul 2020 16:45:11 -0300
> From: Luis Machado via Gdb-patches <gdb-patches@sourceware.org>
> Cc: catalin.marinas@arm.com, david.spickett@linaro.org
> 
> +If the architecture supports memory tagging, the @code{print} command will
> +display pointer/memory tag mismatches if what is being printed is a pointer
> +or reference type.

Please add here a cross reference to the "Memory Tagging" subsection.

> +If the architecture supports memory tagging, the tags can be displayed by
> +using @samp{m}.

Ditto.

> +Due to the way @value{GDBN} prints information with the @code{x} command (not
> +aligned to a particular boundary), the tag information will refer to the
> +initial address displayed on a particular line.  If a memory tag boundary
> +is crossed in the middle of a line displayed by the @code{x} command, it
> +will be displayed in the next line.
                     ^^^^^^^^^^^^^^^^
"on the next line"

> +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.

> +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.