From: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
To: Matthieu Longo <matthieu.longo@arm.com>, binutils@sourceware.org
Cc: Nick Clifton <nickc@redhat.com>
Subject: Re: [PATCH v1 4/4] aarch64: testsuite: share test utils macros and use them
Date: Fri, 10 May 2024 11:42:30 +0100 [thread overview]
Message-ID: <c3822f9d-0372-4cc3-8605-2cb031215beb@arm.com> (raw)
In-Reply-To: <20240227105917.295899-5-matthieu.longo@arm.com>
On 27/02/2024 10:59, Matthieu Longo wrote:
>
> This patch rewrites assembly tests to use utils macros declared in
> sysreg-test-utils.inc. Some tests were adapted to use the new macro
> rw_sys_reg.
> ---
> .../aarch64/sysreg/armv8_9-a-sysregs-bad.d | 2 +-
> .../aarch64/sysreg/armv8_9-a-sysregs-bad.l | 90 ++++-
> .../gas/aarch64/sysreg/armv8_9-a-sysregs.d | 3 +-
> .../gas/aarch64/sysreg/armv8_9-a-sysregs.s | 139 +++----
> .../gas/aarch64/sysreg/illegal-sysreg-3.d | 2 +-
> .../gas/aarch64/sysreg/illegal-sysreg-4.d | 2 +-
> gas/testsuite/gas/aarch64/sysreg/sysreg-1.d | 2 +
> gas/testsuite/gas/aarch64/sysreg/sysreg-1.s | 223 ++++++------
> gas/testsuite/gas/aarch64/sysreg/sysreg-2.d | 3 +-
> gas/testsuite/gas/aarch64/sysreg/sysreg-2.s | 47 ++-
> gas/testsuite/gas/aarch64/sysreg/sysreg-3.d | 3 +-
> gas/testsuite/gas/aarch64/sysreg/sysreg-3.s | 25 +-
> gas/testsuite/gas/aarch64/sysreg/sysreg-6.d | 2 +
> gas/testsuite/gas/aarch64/sysreg/sysreg-6.s | 7 +-
> gas/testsuite/gas/aarch64/sysreg/sysreg-7.d | 2 +
> gas/testsuite/gas/aarch64/sysreg/sysreg-7.s | 32 +-
> gas/testsuite/gas/aarch64/sysreg/sysreg-8.d | 2 +
> gas/testsuite/gas/aarch64/sysreg/sysreg-8.s | 339 +++++++++---------
> .../gas/aarch64/sysreg/sysreg-test-utils.inc | 32 ++
> gas/testsuite/gas/aarch64/sysreg/sysreg.d | 6 +-
> gas/testsuite/gas/aarch64/sysreg/sysreg.s | 63 ++--
> gas/testsuite/gas/aarch64/sysreg/sysreg128.d | 42 +--
> gas/testsuite/gas/aarch64/sysreg/sysreg128.s | 27 +-
> 23 files changed, 576 insertions(+), 519 deletions(-)
> create mode 100644 gas/testsuite/gas/aarch64/sysreg/sysreg-test-utils.inc
>
OK.
R.
next prev parent reply other threads:[~2024-05-10 10:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 10:59 [PATCH v1 0/4][Binutils] aarch64: testsuite: refactoring of some tests to share test macros Matthieu Longo
2024-02-27 10:59 ` [PATCH v1 1/4] aarch64: testsuite: replace instruction addresses by regex Matthieu Longo
2024-05-10 10:34 ` Richard Earnshaw (lists)
2024-02-27 10:59 ` [PATCH v1 2/4] aarch64: testsuite: use same regs for read and write tests Matthieu Longo
2024-05-10 10:37 ` Richard Earnshaw (lists)
2024-02-27 10:59 ` [PATCH v1 3/4] aarch64: testsuite: reorder write and read to match macro order Matthieu Longo
2024-05-10 10:40 ` Richard Earnshaw (lists)
2024-02-27 10:59 ` [PATCH v1 4/4] aarch64: testsuite: share test utils macros and use them Matthieu Longo
2024-02-27 16:31 ` Andrew Carlotti
2024-03-01 10:10 ` Matthieu Longo
2024-03-04 14:43 ` Andrew Carlotti
2024-05-10 10:34 ` Richard Earnshaw (lists)
2024-05-10 10:42 ` Richard Earnshaw (lists) [this message]
2024-04-24 10:48 ` [PATCH v1 0/4][Binutils] aarch64: testsuite: refactoring of some tests to share test macros Matthieu Longo
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=c3822f9d-0372-4cc3-8605-2cb031215beb@arm.com \
--to=richard.earnshaw@arm.com \
--cc=binutils@sourceware.org \
--cc=matthieu.longo@arm.com \
--cc=nickc@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).