public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
To: Andrew Carlotti <andrew.carlotti@arm.com>,
	Matthieu Longo <matthieu.longo@arm.com>
Cc: binutils@sourceware.org, 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:34:12 +0100	[thread overview]
Message-ID: <e65a0117-2d1d-454f-a05d-757448f26717@arm.com> (raw)
In-Reply-To: <9070737f-e2fa-e9c7-fba2-951d53287204@e124511.cambridge.arm.com>



On 04/03/2024 14:43, Andrew Carlotti wrote:
> Indeed - this is just my preference at the moment, and I don't think it should
> prevent this patch being merged (particularly since you're just homogenizing
> existing macro usage).  Plenty of other people have used the macros before you,
> and must therefore have considered them to be beneficial.

I see two main purposes of all these tests.  The first is to allow some 
cross validation with other toolchains - manually staring at individual 
opcodes is a good way to frazzle your brain.  The second is to ensure 
that we don't break things going forwards (introducing regressions).

My main concern would be if the macros make it harder to do cross 
validation.  If so, then that would be an argument against them, but as 
you say, we've already used them in multiple other tests.

R.

  reply	other threads:[~2024-05-10 10:34 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) [this message]
2024-05-10 10:42   ` Richard Earnshaw (lists)
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=e65a0117-2d1d-454f-a05d-757448f26717@arm.com \
    --to=richard.earnshaw@arm.com \
    --cc=andrew.carlotti@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).