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 17:06:47 +0200 [thread overview]
Message-ID: <83ttzcpgjc.fsf@gnu.org> (raw)
In-Reply-To: <e1684a0e-d426-19d6-ddb7-3386811f3261@arm.com> (message from Luis Machado on Thu, 23 Feb 2023 13:33:08 +0000)
> Date: Thu, 23 Feb 2023 13:33:08 +0000
> Cc: gdb-patches@sourceware.org
> From: Luis Machado <luis.machado@arm.com>
>
> On 2/23/23 11:04, Eli Zaretskii wrote:
> >
> >> +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?
> >
>
> Some flags/fields are reserved to be used in future extensions of the architecture.
>
> For example, suppose bit 26 in 32-bit register is undefined, but then gets defined for a new
> architecture extension. We need to update the XML to reflect that.
Then I suggest something like
The semantics of the individual flags in @samp{cpsr} can change as
new architectural features are added.
next prev parent reply other threads:[~2023-02-23 15:06 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
2023-02-23 13:33 ` Luis Machado
2023-02-23 15:06 ` Eli Zaretskii [this message]
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=83ttzcpgjc.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).