From: Eli Zaretskii <eliz@gnu.org>
To: Luis Machado <luis.machado@arm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/doc] aarch64: Expand documentation of XML features
Date: Thu, 23 Feb 2023 13:04:00 +0200 [thread overview]
Message-ID: <837cw8r6cf.fsf@gnu.org> (raw)
In-Reply-To: <20230223095244.1813332-1-luis.machado@arm.com> (message from Luis Machado on Thu, 23 Feb 2023 09:52:44 +0000)
> From: Luis Machado <luis.machado@arm.com>
> CC: <eliz@gnu.org>
> Date: Thu, 23 Feb 2023 09:52:44 +0000
>
> Similar to the arm target documentation situation, the documentation of the
> XML features for AArch64 targets is rather brief. I have received the same
> feedback that what gdb carries in the documentation is quite unclear from the
> perspective of what debugging servers should define in the XML features, how and
> what the outcome is in gdb.
>
> This patch attempts to clarify a bit more what all the possible features are.
Thanks.
> The @samp{org.gnu.gdb.aarch64.core} feature is required for AArch64
> -targets. It should contain registers @samp{x0} through @samp{x30},
> -@samp{sp}, @samp{pc}, and @samp{cpsr}.
> +targets. It must contain the following:
> +
> +@itemize @minus
> +@item
> +@samp{x0} through @samp{x30}, with size of 64-bit. Register @samp{x30} is
This doesn't say these are registers, please add that.
> +also known as the link register @samp{lr}.
The "link register" part should probably be in @dfn, and "@samp{lr}"
should probably be ", or @samp{lr}", as it's an alternative name AFAIU.
> +@item
> +@samp{pc}, the program counter register. It is 64-bit in size and has a type
> +of @samp{code_ptr}. ^^
Two spaces there, please.
> +The @samp{cpsr} flags type gets updated based on new architectural
> +features.
"flags type gets updated" sounds awkward and confusing. What did you
mean by that? what is updated?
> +@item
> +@samp{v0} through @samp{v31}, the vector registers with size of 128-bit. The
^^^^^^^
The dash is redundant there and should be dropped.
> +@samp{z0} through @samp{z31}, the scalable vector registers. Their sizes are
> +variable and a multiple of 128-bit up to a maximum of 2048-bit. Their type is
Same here.
> +@samp{p0} through @samp{p15}, the predicate registers. Their sizes are
> +variable, based on the current vector length, and a multiple of 16-bit. Their
And here.
> +@item
> +@samp{ffr}, the First Fault register. It has a variable size based on the
> +current vector length and is a multiple of 16-bit. The type is the same as
And here. Also, "and is" is ambiguous: you mean the size is a
multiple, but the text can be interpreted as alluding to the register,
not its size.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
next prev parent reply other threads:[~2023-02-23 11:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 9:52 Luis Machado
2023-02-23 11:04 ` Eli Zaretskii [this message]
2023-02-23 13:33 ` Luis Machado
2023-02-23 15:06 ` Eli Zaretskii
2023-02-24 18:41 ` [PATCH, v2] " Luis Machado
2023-02-24 19:25 ` Eli Zaretskii
2023-03-13 11:32 ` Luis Machado
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=837cw8r6cf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).