From: <Ezra.Sitorus@arm.com>
To: <gdb-patches@sourceware.org>
Cc: <luis.machado.foss@gmail.com>, <thiago.bauermann@linaro.org>,
Ezra Sitorus <ezra.sitorus@arm.com>
Subject: [PATCH 3/4] gdb/aarch64: record/replay support for RPRFM and PRFM (reg)
Date: Mon, 20 Apr 2026 22:52:31 +0100 [thread overview]
Message-ID: <20260420215232.68675-4-Ezra.Sitorus@arm.com> (raw)
In-Reply-To: <20260420215232.68675-1-Ezra.Sitorus@arm.com>
From: Ezra Sitorus <ezra.sitorus@arm.com>
The PRFM (register) instruction variant was unsupported. This is added
along with RPRFM.
No testcase has been added as these are hint instructions which don't
modify registers/memory. I'm happy to add them in if you think these are
required.
The full testsuite was done on aarch64-none-linux-gnu without RPRFM.
The gdb.arch and gdb.reverse tests were run on Shrinkwrap with RPRFM
support. I've observed unrelated regressions that appear to be due to
Shrinkwrap rather than my patch.
---
gdb/aarch64-tdep.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/gdb/aarch64-tdep.c b/gdb/aarch64-tdep.c
index 81d4f160f8f..61c462979b3 100644
--- a/gdb/aarch64-tdep.c
+++ b/gdb/aarch64-tdep.c
@@ -5914,6 +5914,11 @@ aarch64_record_load_store (aarch64_insn_decode_record *aarch64_insn_r)
else
if (size_bits != 0x03)
ld_flag = 0x01;
+ else if (size_bits == 0x3 && vector_flag == 0x0 && opc == 0x2)
+ {
+ /* PRFM (register) or RPRFM */
+ return AARCH64_RECORD_SUCCESS;
+ }
else
return AARCH64_RECORD_UNKNOWN;
--
2.43.0
next prev parent reply other threads:[~2026-04-20 21:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 21:52 [PATCH 0/4] gdb/aarch64: record/replay support for AArch64 Ezra.Sitorus
2026-04-20 21:52 ` [PATCH 1/4] gdb/aarch64: record/replay support for LRCPC3 Ezra.Sitorus
2026-04-24 7:00 ` Luis
2026-04-24 15:09 ` Guinevere Larsen
2026-04-25 5:08 ` Thiago Jung Bauermann
2026-04-25 7:21 ` Thiago Jung Bauermann
2026-04-20 21:52 ` [PATCH 2/4] gdb/aarch64: Test record/replay support for CSSC Ezra.Sitorus
2026-04-24 7:07 ` Luis
2026-04-24 16:53 ` Guinevere Larsen
2026-04-25 6:10 ` Thiago Jung Bauermann
2026-04-25 7:28 ` Thiago Jung Bauermann
2026-04-20 21:52 ` Ezra.Sitorus [this message]
2026-04-24 7:08 ` [PATCH 3/4] gdb/aarch64: record/replay support for RPRFM and PRFM (reg) Luis
2026-04-24 16:56 ` Guinevere Larsen
2026-04-25 8:12 ` Thiago Jung Bauermann
2026-04-20 21:52 ` [PATCH 4/4] gdb/aarch64: record/replay support for LSE128 Ezra.Sitorus
2026-04-24 7:11 ` Luis
2026-04-24 17:12 ` Guinevere Larsen
2026-04-25 8:38 ` Thiago Jung Bauermann
2026-04-23 17:31 ` [PATCH 0/4] gdb/aarch64: record/replay support for AArch64 Guinevere Larsen
2026-04-23 22:20 ` Ezra Sitorus
2026-04-24 5:33 ` Thiago Jung Bauermann
2026-04-24 7:16 ` 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=20260420215232.68675-4-Ezra.Sitorus@arm.com \
--to=ezra.sitorus@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