From: Eli Zaretskii <eliz@gnu.org>
To: Alan Hayward <Alan.Hayward@arm.com>
Cc: gdb-patches@sourceware.org, nd@arm.com
Subject: Re: [PATCH] Move [PAC] into a new MI field addr_flags
Date: Tue, 13 Aug 2019 14:28:00 -0000 [thread overview]
Message-ID: <83pnl9rvgd.fsf@gnu.org> (raw)
In-Reply-To: <13AF2ADD-7322-420D-A889-FB5BA19CFF99@arm.com> (message from Alan Hayward on Tue, 13 Aug 2019 09:19:26 +0000)
> From: Alan Hayward <Alan.Hayward@arm.com>
> CC: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>, nd <nd@arm.com>
> Date: Tue, 13 Aug 2019 09:19:26 +0000
> How about this:
>
>
> * Other MI changes
>
> ** Backtraces and frames include a new optional field addr_flags which is
> given after the addr field. On AArch64 this contains PAC if the address
> has been masked in the frame. On all other targets the field is not
> present.
LGTM.
> >> +@item addr_flags
> >> +Optional field containing any flags related to the address. If there
> >> +are any flags defined for the current target then they are documented in
> >> +the @xref{Architectures} section.
> >
> > I suggest to reword:
> >
> > These flags are architecture-dependent; see @ref{Architectures} for
> > their meaning for a particular CPU.
>
> Maybe keep the first sentence? Giving:
>
> Optional field containing any flags related to the address. These flags are
> architecture-dependent; see @ref{Architectures} for their meaning for a
> particular CPU.
Yes, I definitely meant to keep the first sentence.
Thanks.
next prev parent reply other threads:[~2019-08-13 14:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 15:14 Alan Hayward
2019-08-12 15:37 ` Eli Zaretskii
2019-08-13 9:19 ` Alan Hayward
2019-08-13 14:28 ` Eli Zaretskii [this message]
2019-08-15 17:39 ` Pedro Alves
2019-08-16 9:21 ` Alan Hayward
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=83pnl9rvgd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Alan.Hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@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