From: Alan Modra <amodra@gmail.com>
To: Andrew Burgess <aburgess@redhat.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] gas/ppc: Additional tests for DFP instructions
Date: Tue, 31 Jan 2023 17:11:51 +1030 [thread overview]
Message-ID: <Y9i4L7WNBPEEBpIq@squeak.grove.modra.org> (raw)
In-Reply-To: <95d700d49f5cdd2239c44ec17dadd11652f7be93.1675091147.git.aburgess@redhat.com>
On Mon, Jan 30, 2023 at 03:11:41PM +0000, Andrew Burgess via Binutils wrote:
> I noticed that some of the Power6 DFP instructions were not covered by
> the assembler tests. I've added a new test file which I believe
> covers all the DFP Power6 instructions.
>
> The existing gas/testsuite/gas/ppc/power6.d test is called:
>
> POWER6 tests (includes DFP and Altivec)
>
> And does cover some of the DFP instructions. But, given the number of
> additional instructions I'm adding I opted to add a whole new test
> file. I've left the original power6.d unchanged, so there is now some
> overlap, but I don't think that should hurt much.
Thanks for doing this. Please apply.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2023-01-31 6:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 15:11 Andrew Burgess
2023-01-31 6:41 ` Alan Modra [this message]
2023-01-31 9:34 ` Andrew Burgess
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=Y9i4L7WNBPEEBpIq@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=aburgess@redhat.com \
--cc=binutils@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).