Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis <luis.machado.foss@gmail.com>
To: Ezra.Sitorus@arm.com, gdb-patches@sourceware.org
Cc: thiago.bauermann@linaro.org
Subject: Re: [PATCH 0/4] gdb/aarch64: record/replay support for AArch64
Date: Fri, 24 Apr 2026 08:16:21 +0100	[thread overview]
Message-ID: <e8fbe8bc-bd2a-4fea-9c0f-2af06aaa64c0@gmail.com> (raw)
In-Reply-To: <20260420215232.68675-1-Ezra.Sitorus@arm.com>

On 20/04/2026 22:52, Ezra.Sitorus@arm.com wrote:
> From: Ezra Sitorus <ezra.sitorus@arm.com>
> 
> This patch series enables record/replay for the following AArch64
> features:
> * FEAT_LRCPC3 (+rcpc3)
> * FEAT_CSSC (+cssc)
> * FEAT_RPRFM (+rprfm)
> * FEAT_LSE128 (+lse128)
> 
> These were tested either with QEMU or Shrinkwrap. In both cases, I seem
> to have test failures that are not related to my patches (gdb.threads,
> gdb.mi tests for example). In these cases, is it fair to ignore these?
> Or is there some underlying issue I've missed?

That's common. You'll also spot hardware watchpoint behavior differences 
between QEMU and hardware/FM.

As long as things don´t regress overall, it should be fine to ignore the 
flaky tests. You just need to know what they are, so that takes a bit of 
time to get familiar.

> 
> In addition, whenever I used QEMU, I disabled gcs because it seems to
> cause test failures - address/memory accesses seem to always cause a
> fault. Am I doing something wrong?

I wouldn´t expect that to happen, so there might be issues there.

Out of curiosity, as people use more and more LLVM, have you tried with 
tests against LLVM to make sure they pass?

> 
> Ezra
> 
> Ezra Sitorus (4):
>    gdb/aarch64: record/replay support for LRCPC3
>    gdb/aarch64: Test record/replay support for CSSC
>    gdb/aarch64: record/replay support for RPRFM and PRFM (reg)
>    gdb/aarch64: record/replay support for LSE128
> 
>   gdb/aarch64-tdep.c                           | 105 ++++++
>   gdb/testsuite/gdb.reverse/aarch64-cssc.c     | 113 +++++++
>   gdb/testsuite/gdb.reverse/aarch64-cssc.exp   | 141 ++++++++
>   gdb/testsuite/gdb.reverse/aarch64-lrcpc3.c   | 319 +++++++++++++++++++
>   gdb/testsuite/gdb.reverse/aarch64-lrcpc3.exp | 203 ++++++++++++
>   gdb/testsuite/gdb.reverse/aarch64-lse128.c   | 139 ++++++++
>   gdb/testsuite/gdb.reverse/aarch64-lse128.exp | 138 ++++++++
>   gdb/testsuite/lib/gdb.exp                    | 171 ++++++++++
>   8 files changed, 1329 insertions(+)
>   create mode 100644 gdb/testsuite/gdb.reverse/aarch64-cssc.c
>   create mode 100644 gdb/testsuite/gdb.reverse/aarch64-cssc.exp
>   create mode 100644 gdb/testsuite/gdb.reverse/aarch64-lrcpc3.c
>   create mode 100644 gdb/testsuite/gdb.reverse/aarch64-lrcpc3.exp
>   create mode 100644 gdb/testsuite/gdb.reverse/aarch64-lse128.c
>   create mode 100644 gdb/testsuite/gdb.reverse/aarch64-lse128.exp
> 


      parent reply	other threads:[~2026-04-24  7:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-20 21:52 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 ` [PATCH 3/4] gdb/aarch64: record/replay support for RPRFM and PRFM (reg) Ezra.Sitorus
2026-04-24  7:08   ` 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 [this message]

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=e8fbe8bc-bd2a-4fea-9c0f-2af06aaa64c0@gmail.com \
    --to=luis.machado.foss@gmail.com \
    --cc=Ezra.Sitorus@arm.com \
    --cc=gdb-patches@sourceware.org \
    --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