From: will schmidt <will_schmidt@vnet.ibm.com>
To: Michael Meissner <meissner@linux.ibm.com>,
gcc-patches@gcc.gnu.org,
Segher Boessenkool <segher@kernel.crashing.org>,
"Kewen.Lin" <linkw@linux.ibm.com>,
David Edelsohn <dje.gcc@gmail.com>,
Peter Bergner <bergner@linux.ibm.com>
Subject: Re: [PATCH 3/3] Adjust MMA tests to account for no store vector pair.
Date: Tue, 07 Jun 2022 15:28:23 -0500 [thread overview]
Message-ID: <319dd1f6f5e973d180f5d9d92cef36e61bc084b6.camel@vnet.ibm.com> (raw)
In-Reply-To: <Yp6iT3yUibRemfXk@toto.the-meissners.org>
On Mon, 2022-06-06 at 20:56 -0400, Michael Meissner wrote:
> [PATCH 3/3] Adjust MMA tests to account for no store vector pair.
>
> In changing the default for generating the store vector pair instructions,
> I had to adjust several of the MMA tests to remove checking for these
> instructions. Mostly I just deleted the scan-assembler lines checking for
> stxvp. In two of the tests, I added the -mstore-vector-pair option since
> the point of the test was to check for specific cases with store vector
> pair instructions.
>
> I have built bootstrap compilers and run the regression tests on three
> different systems:
>
> 1) Little endian power10 using the --with-cpu=power10 option.
>
> 2) Little endian power9 using the --with-cpu=power9 option.
>
> 3) Big endian power8 using the --with-cpu=power8 option. On this system,
> both 64-bit and 32-bit code generation was tested.
>
> There were no regressions in the runs. Can I check this patch into the
> trunk? If there are no changes needed for the backports, can I check this
> code into the active branches after a burn-in period?
>
> 2022-06-06 Michael Meissner <meissner@linux.ibm.com>
>
> gcc/testsuite/
>
> * gcc.target/powerpc/mma-builtin-1.c: Eliminate checking for store
> vector pair instructions.
> * gcc.target/powerpc/mma-builtin-10-pair.c: Likewise.
> * gcc.target/powerpc/mma-builtin-10-quit.c: Likewise.
> * gcc.target/powerpc/mma-builtin-2.c: Likewise.
> * gcc.target/powerpc/mma-builtin-3.c: Likewise.
> * gcc.target/powerpc/mma-builtin-4.c: Likewise.
> * gcc.target/powerpc/mma-builtin-5.c: Likewise.
> * gcc.target/powerpc/mma-builtin-6.c: Likewise.
> * gcc.target/powerpc/mma-builtin-7.c: Likewise.
> * gcc.target/powerpc/mma-builtin-9.c: Likewise.
> * gcc.target/powerpc/mma-builtin-8.c: Add -mstore-vector-pair.
> * gcc.target/powerpc/pr102976.c: Likewise.
> ---
> gcc/testsuite/gcc.target/powerpc/mma-builtin-1.c | 1 -
> gcc/testsuite/gcc.target/powerpc/mma-builtin-10-pair.c | 2 --
> gcc/testsuite/gcc.target/powerpc/mma-builtin-10-quad.c | 2 --
> gcc/testsuite/gcc.target/powerpc/mma-builtin-2.c | 1 -
> gcc/testsuite/gcc.target/powerpc/mma-builtin-3.c | 1 -
> gcc/testsuite/gcc.target/powerpc/mma-builtin-4.c | 2 --
> gcc/testsuite/gcc.target/powerpc/mma-builtin-5.c | 2 --
> gcc/testsuite/gcc.target/powerpc/mma-builtin-6.c | 1 -
> gcc/testsuite/gcc.target/powerpc/mma-builtin-7.c | 2 --
> gcc/testsuite/gcc.target/powerpc/mma-builtin-8.c | 2 +-
> gcc/testsuite/gcc.target/powerpc/mma-builtin-9.c | 2 --
> gcc/testsuite/gcc.target/powerpc/pr102976.c | 6 +++++-
> 12 files changed, 6 insertions(+), 18 deletions(-)
>
> diff --git a/gcc/testsuite/gcc.target/powerpc/mma-builtin-1.c b/gcc/testsuite/gcc.target/powerpc/mma-builtin-1.c
> index 69ee826e1be..47b45b00403 100644
> --- a/gcc/testsuite/gcc.target/powerpc/mma-builtin-1.c
> +++ b/gcc/testsuite/gcc.target/powerpc/mma-builtin-1.c
> @@ -260,7 +260,6 @@ foo13b (__vector_quad *dst, __vector_quad *src, vec_t *vec)
>
> /* { dg-final { scan-assembler-times {\mlxv\M} 40 } } */
> /* { dg-final { scan-assembler-times {\mlxvp\M} 12 } } */
> -/* { dg-final { scan-assembler-times {\mstxvp\M} 40 } } */
> /* { dg-final { scan-assembler-times {\mxxmfacc\M} 20 } } */
> /* { dg-final { scan-assembler-times {\mxxmtacc\M} 6 } } */
> /* { dg-final { scan-assembler-times {\mxvbf16ger2\M} 1 } } */
<snip>
This all seems straightforward. LGTM, thanks.
-Will
prev parent reply other threads:[~2022-06-07 20:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 0:53 [PATCH, 0/3] Disable generating " Michael Meissner
2022-06-07 0:55 ` [PATCH 1/3] " Michael Meissner
2022-06-07 20:28 ` will schmidt
2022-06-07 21:17 ` Peter Bergner
2022-06-07 21:24 ` Segher Boessenkool
2022-06-08 0:59 ` Peter Bergner
2022-06-08 3:16 ` Michael Meissner
2022-06-08 14:49 ` will schmidt
2022-06-08 14:58 ` Peter Bergner
2022-06-07 23:20 ` Michael Meissner
2022-06-07 0:55 ` [PATCH 2/3] Disable generating load/store vector pairs for block copies Michael Meissner
2022-06-07 20:28 ` will schmidt
2022-06-07 0:56 ` [PATCH 3/3] Adjust MMA tests to account for no store vector pair Michael Meissner
2022-06-07 20:28 ` will schmidt [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=319dd1f6f5e973d180f5d9d92cef36e61bc084b6.camel@vnet.ibm.com \
--to=will_schmidt@vnet.ibm.com \
--cc=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=linkw@linux.ibm.com \
--cc=meissner@linux.ibm.com \
--cc=segher@kernel.crashing.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).