From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: Luis <luis.machado.foss@gmail.com>
Cc: Ezra.Sitorus@arm.com, gdb-patches@sourceware.org
Subject: Re: [RFC PATCH 1/5] gdb/aarch64: Enable FPMR for AArch64 in gdb on Linux
Date: Wed, 10 Sep 2025 20:56:05 -0300 [thread overview]
Message-ID: <87cy7x50bu.fsf@linaro.org> (raw)
In-Reply-To: <606b962c-d505-4e68-9090-20c003a9c6ed@gmail.com> (Luis's message of "Sun, 7 Sep 2025 23:55:29 +0100")
Luis <luis.machado.foss@gmail.com> writes:
> On 05/09/2025 14:17, Ezra.Sitorus@arm.com wrote:
>> index 679d845df74..731d4680248 100644
>> --- a/gdb/arch/aarch64.h
>> +++ b/gdb/arch/aarch64.h
>> @@ -34,6 +34,7 @@ struct aarch64_features
>> uint64_t vq = 0;
>> bool pauth = false;
>> bool mte = false;
>> + bool fpmr = false;
>> /* A positive TLS value indicates the number of TLS registers available. */
>> uint8_t tls = 0;
>> @@ -68,7 +69,8 @@ inline bool operator==(const aarch64_features &lhs, const
> aarch64_features &rhs)
>> && lhs.svq == rhs.svq
>> && lhs.sme2 == rhs.sme2
>> && lhs.gcs == rhs.gcs
>> - && lhs.gcs_linux == rhs.gcs_linux;
>> + && lhs.gcs_linux == rhs.gcs_linux
>> + && lhs.fpmr == rhs.fpmr;
>> }
>
> Do you also need to update the operator() to account for fpmr? It computes the hash of the
> feature based on what features are present.
>
> Unrelated, but looking at the code, it may be the case we missed adding gcs and gcs_linux
> to this operator.
You're right, I missed that one. I'll submit a patch fixing this.
--
Thiago
next prev parent reply other threads:[~2025-09-10 23:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 13:17 [RFC PATCH 0/5] gdb/aarch64: Support for FPMR Ezra.Sitorus
2025-09-05 13:17 ` [RFC PATCH 1/5] gdb/aarch64: Enable FPMR for AArch64 in gdb on Linux Ezra.Sitorus
2025-09-07 22:55 ` Luis
2025-09-10 23:56 ` Thiago Jung Bauermann [this message]
2025-09-10 23:45 ` Thiago Jung Bauermann
2025-09-05 13:17 ` [RFC PATCH 2/5] gdbserver/aarch64: Enable FPMR for AArch64 in gdbserver " Ezra.Sitorus
2025-09-07 22:55 ` Luis
2025-09-10 23:46 ` Thiago Jung Bauermann
2025-09-05 13:17 ` [RFC PATCH 3/5] gdb/aarch64: signal frame support for fpmr Ezra.Sitorus
2025-09-07 22:56 ` Luis
2025-09-11 0:03 ` Thiago Jung Bauermann
2025-09-10 23:47 ` Thiago Jung Bauermann
2025-09-05 13:17 ` [RFC PATCH 4/5] gdb/aarch64: core file support for FPMR Ezra.Sitorus
2025-09-07 22:56 ` Luis
2025-09-10 23:48 ` Thiago Jung Bauermann
2025-09-05 13:17 ` [RFC PATCH 5/5] gdb/aarch64: Tests for fpmr Ezra.Sitorus
2025-09-07 22:56 ` Luis
2025-09-16 11:09 ` Ezra Sitorus
2025-09-16 23:50 ` Luis
2025-09-10 23:53 ` Thiago Jung Bauermann
2025-09-10 23:39 ` [RFC PATCH 0/5] gdb/aarch64: Support for FPMR Thiago Jung Bauermann
2025-09-11 15:52 ` Ezra Sitorus
2025-09-12 3:17 ` Thiago Jung Bauermann
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=87cy7x50bu.fsf@linaro.org \
--to=thiago.bauermann@linaro.org \
--cc=Ezra.Sitorus@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado.foss@gmail.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