From: <Ezra.Sitorus@arm.com>
To: <gdb-patches@sourceware.org>
Cc: <luis.machado.foss@gmail.com>, <thiago.bauermann@linaro.org>,
<guinevere@redhat.com>, Ezra Sitorus <ezra.sitorus@arm.com>
Subject: [PATCH v2 3/4] gdb/aarch64: record/replay support for RPRFM, PRFM (reg), PRFUM
Date: Wed, 13 May 2026 00:17:06 +0100 [thread overview]
Message-ID: <20260512231707.18123-4-Ezra.Sitorus@arm.com> (raw)
In-Reply-To: <20260512231707.18123-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 and PRFUM.
No testcase has been added as these are hint instructions which don't
modify registers/memory.
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.
---
gdb/aarch64-tdep.c | 13 +++++++++++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/gdb/aarch64-tdep.c b/gdb/aarch64-tdep.c
index b10bba67..5c1f8af5 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;
@@ -5944,7 +5949,7 @@ aarch64_record_load_store (aarch64_insn_decode_record *aarch64_insn_r)
aarch64_insn_r->reg_rec_count = 1;
}
}
- /* Load/store register (immediate and unprivileged) instructions. */
+ /* Load/store register (immediate and unprivileged) instructions and PRFUM. */
else if ((insn_bits24_27 & 0x0b) == 0x08 && insn_bits28_29 == 0x03
&& !insn_bit21)
{
@@ -5963,7 +5968,11 @@ aarch64_record_load_store (aarch64_insn_decode_record *aarch64_insn_r)
if (size_bits != 0x03)
ld_flag = 0x01;
else
- return AARCH64_RECORD_UNKNOWN;
+ if (insn_bits10_11 == 0)
+ /* PRFUM instruction. */
+ return AARCH64_RECORD_SUCCESS;
+ else
+ return AARCH64_RECORD_UNKNOWN;
if (!ld_flag)
{
--
2.53.0
next prev parent reply other threads:[~2026-05-12 23:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 23:17 [PATCH v2 0/4] gdb/aarch64: record/replay support for AArch64 Ezra.Sitorus
2026-05-12 23:17 ` [PATCH v2 1/4] gdb/aarch64: record/replay support for LRCPC3 Ezra.Sitorus
2026-05-15 3:50 ` Thiago Jung Bauermann
2026-05-15 11:45 ` Ezra Sitorus
2026-05-15 23:03 ` Thiago Jung Bauermann
2026-05-26 14:30 ` Guinevere Larsen
2026-05-26 23:36 ` Ezra Sitorus
2026-05-27 0:05 ` Thiago Jung Bauermann
2026-05-12 23:17 ` [PATCH v2 2/4] gdb/aarch64: Test record/replay support for CSSC Ezra.Sitorus
2026-05-15 3:50 ` Thiago Jung Bauermann
2026-05-26 19:40 ` Guinevere Larsen
2026-05-26 16:40 ` Guinevere Larsen
2026-05-12 23:17 ` Ezra.Sitorus [this message]
2026-05-15 3:56 ` [PATCH v2 3/4] gdb/aarch64: record/replay support for RPRFM, PRFM (reg), PRFUM Thiago Jung Bauermann
2026-05-12 23:17 ` [PATCH v2 4/4] gdb/aarch64: record/replay support for LSE128 Ezra.Sitorus
2026-05-15 3:58 ` Thiago Jung Bauermann
2026-05-26 19:40 ` Guinevere Larsen
2026-05-15 3:59 ` [PATCH v2 0/4] gdb/aarch64: record/replay support for AArch64 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=20260512231707.18123-4-Ezra.Sitorus@arm.com \
--to=ezra.sitorus@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=guinevere@redhat.com \
--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