From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: Ezra.Sitorus@arm.com, gdb-patches@sourceware.org
Cc: luis.machado.foss@gmail.com, Guinevere Larsen <guinevere@redhat.com>
Subject: Re: [PATCH v3] gdb/aarch64: record/replay support for LRCPC3
Date: Mon, 01 Jun 2026 22:10:52 +0000 [thread overview]
Message-ID: <87pl29oqs3.fsf@linaro.org> (raw)
In-Reply-To: <8d8de19a-4fa0-4f07-aefd-feaf41a7af62@redhat.com> (Guinevere Larsen's message of "Mon, 1 Jun 2026 10:21:37 -0300")
Guinevere Larsen <guinevere@redhat.com> writes:
> On 5/29/26 8:01 PM, Ezra.Sitorus@arm.com wrote:
>> From: Ezra Sitorus <ezra.sitorus@arm.com>
>>
>> FEAT_LRCPC3 introduces various load/store instructions with release
>> consistency for cases where ordering is required. This patch teaches GDB
>> to decode these instructions for recording and reversing.
>>
>> The gdb.reverse/aarch64-lrcpc3.exp testcase verifies that the
>> instructions are recorded and correctly reversed. In particular, there
>> are some interesting cases to note:
>> * ldapur/stlur are SIMD instructions, but are not decoded in the simd
>> function.
>> * There are writeback cases to cover too. These were taken from the
>> binutils testcases: gas/testsuite/gas/aarch64/rcpc3.s.
>>
>> The full testsuite was done on aarch64-none-linux-gnu without LRCPC3.
>> The gdb.arch and gdb.reverse tests were run on Shrinkwrap with LRCPC3
>> support.
>>
>> Please note:
>> 1) There is no support for LRCPC and LRCPC2 instructions
>> 2) LRCPC3 is gated with +rcpc3 in GCC/binutils and LLVM.
>>
>> ---
>
> This looks ready to go in from the record-full side. Feel free to add my tag
>
> Approved-By: Guinevere Larsen <guinevere@redhat.com> (record-full)
>
> You should wait for Luis's or Thiago's approval for the aarch64 parts before pushing it,
> though, as I only approved the test parts and ack the changes to the recording part
Thank you Guinevere for the review, and thank you Ezra for v3.
This version looks good to me.
Approved-by: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
--
Thiago
(he/him)
next prev parent reply other threads:[~2026-06-01 22:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 23:01 Ezra.Sitorus
2026-06-01 13:21 ` Guinevere Larsen
2026-06-01 22:10 ` Thiago Jung Bauermann [this message]
2026-06-01 22:40 ` Ezra Sitorus
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=87pl29oqs3.fsf@linaro.org \
--to=thiago.bauermann@linaro.org \
--cc=Ezra.Sitorus@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=guinevere@redhat.com \
--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