From: Ezra Sitorus <ezra.sitorus@arm.com>
To: Richard Earnshaw <Richard.Earnshaw@arm.com>
Cc: Luis <luis.machado.foss@gmail.com>, <gdb-patches@sourceware.org>,
<thiago.bauermann@linaro.org>
Subject: Re: [PATCH v2 2/5] gdbserver/aarch64: Enable FPMR for AArch64 in gdbserver on Linux
Date: Mon, 13 Oct 2025 15:53:07 +0100 [thread overview]
Message-ID: <aO0SUya_-i46CwFD@D2G2X7XGD1> (raw)
In-Reply-To: <1db3bf19-02e4-40bb-adf7-6355b176e0f2@arm.com>
On Mon, Oct 13, 2025 at 02:40:07PM +0100, Richard Earnshaw wrote:
> On 11/10/2025 12:50, Luis wrote:
> > On 07/10/2025 13:31, Ezra.Sitorus@arm.com wrote:
> > > From: Ezra Sitorus <ezra.sitorus@arm.com>
> > >
> > > Support FPMR in gdbserver.
> >
> > Nit. Make it "Add support for FPMR register set in gdbserver."
> >
> > It is a bit more descriptive.
>
> But grammatically wrong, since FPMR is short for Floating Point Mode
> Register. So then you'd have:
>
> Add support for the floating point mode register register set in
> gdbserver!!!!
>
> R.
>
> >
I agree with Richard that it should just be FPMR but I think FPMR register
set makes sense too. Linux kernel has REGSET_FPMR, as well as REGSET_GPR
and REGSET_FPR. Maybe you're meant to think something along the lines of a
'register set called FPMR, which only has the FPMR'?
Which means something like this:
> > > +/* Fill BUF with the FPMR register from the regcache.� */
> > > +
> > > +static void
> > > +aarch64_fill_fpmr_regset (struct regcache *regcache, void *buf)
should just be:
Fill BUF with the FPMR from the regcache.
but this works too:
Fill BUF with the FPMR register set from the regcache.
Ezra
next prev parent reply other threads:[~2025-10-13 14:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 12:31 [PATCH v2 0/5] gdb/aarch64: Support for FPMR Ezra.Sitorus
2025-10-07 12:31 ` [PATCH v2 1/5] gdb/aarch64: Enable FPMR for AArch64 in gdb on Linux Ezra.Sitorus
2025-10-11 11:35 ` Luis
2025-10-07 12:31 ` [PATCH v2 2/5] gdbserver/aarch64: Enable FPMR for AArch64 in gdbserver " Ezra.Sitorus
2025-10-11 11:50 ` Luis
2025-10-13 13:40 ` Richard Earnshaw
2025-10-13 14:53 ` Ezra Sitorus [this message]
2025-10-16 22:01 ` Luis
2025-10-07 12:31 ` [PATCH v2 3/5] gdb/aarch64: signal frame support for fpmr Ezra.Sitorus
2025-10-11 11:57 ` Luis
2025-10-11 12:15 ` Luis
2025-10-07 12:31 ` [PATCH v2 4/5] gdb/aarch64: core file support for FPMR Ezra.Sitorus
2025-10-11 12:03 ` Luis
2025-10-07 12:31 ` [PATCH v2 5/5] gdb/aarch64: Tests for fpmr Ezra.Sitorus
2025-10-11 12:53 ` Luis
2025-10-11 12:05 ` [PATCH v2 0/5] gdb/aarch64: Support for FPMR Luis
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=aO0SUya_-i46CwFD@D2G2X7XGD1 \
--to=ezra.sitorus@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado.foss@gmail.com \
--cc=thiago.bauermann@linaro.org \
/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