From: Bill Schmidt <wschmidt@linux.ibm.com>
To: Peter Bergner <bergner@linux.ibm.com>,
Segher Boessenkool <segher@kernel.crashing.org>,
David Edelsohn <dje.gcc@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] rs6000: Disable optimizing multiple xxsetaccz instructions into one xxsetaccz
Date: Sun, 12 Sep 2021 10:32:47 -0500 [thread overview]
Message-ID: <76dc14a6-3702-d391-f97e-df9bd72c9ef2@linux.ibm.com> (raw)
In-Reply-To: <8393a33f-50ab-6720-0017-3f012803b990@linux.ibm.com>
Hi Peter,
This patch looks fine to me. The approach to avoiding incorrect
optimization is reasonable. Maintainers?
Thanks for the patch!
Bill
On 8/27/21 2:58 PM, Peter Bergner via Gcc-patches wrote:
> Fwprop will happily optimize two xxsetaccz instructions into one xxsetaccz
> by propagating the results of the first to the uses of the second.
> We really don't want that to happen given the late priming/depriming of
> accumulators. I fixed this by making the xxsetaccz source operand an
> unspec volatile. I also removed the mma_xxsetaccz define_expand and
> define_insn_and_split and replaced it with a simple define_insn.
> The expand and splitter patterns were leftovers from the pre opaque mode
> code when the xxsetaccz code was part of the movpxi pattern, and we don't
> need them now.
>
> Rather than a new test case, I was able to just modify the current test case
> to add another __builtin_mma_xxsetaccz call which shows the bad code gen
> with unpatched compilers.
>
> This passed bootstrap on powerpc64le-linux with no regressions.
> Ok for trunk? We'll need this for sure in GCC11. Ok there too after
> some trunk burn in time?
>
> GCC10 suffers from the same issue, but since the code is different, I'll
> have to determine a different solution which I'll post as a separate
> patch.
>
> Peter
>
>
> gcc/
> * config/rs6000/mma.md (unspec): Delete UNSPEC_MMA_XXSETACCZ.
> (unspecv): Add UNSPECV_MMA_XXSETACCZ.
> (*mma_xxsetaccz): Delete.
> (mma_xxsetaccz): Change to define_insn. Remove match_operand.
> Use UNSPECV_MMA_XXSETACCZ.
> * config/rs6000/rs6000.c (rs6000_rtx_costs): Use UNSPECV_MMA_XXSETACCZ.
>
> gcc/testsuite/
> * gcc.target/powerpc/mma-builtin-6.c: Add second call to xxsetacc
> built-in. Update instruction counts.
>
> diff --git a/gcc/config/rs6000/mma.md b/gcc/config/rs6000/mma.md
> index 1f6fc03d2ac..b26ae7a5d04 100644
> --- a/gcc/config/rs6000/mma.md
> +++ b/gcc/config/rs6000/mma.md
> @@ -91,7 +91,10 @@ (define_c_enum "unspec"
> UNSPEC_MMA_XVI8GER4SPP
> UNSPEC_MMA_XXMFACC
> UNSPEC_MMA_XXMTACC
> - UNSPEC_MMA_XXSETACCZ
> + ])
> +
> +(define_c_enum "unspecv"
> + [UNSPECV_MMA_XXSETACCZ
> ])
>
> ;; MMA instructions with 1 accumulator argument
> @@ -469,26 +472,12 @@ (define_insn "mma_<acc>"
>
> ;; We can't have integer constants in XOmode so we wrap this in an UNSPEC.
>
> -(define_expand "mma_xxsetaccz"
> - [(set (match_operand:XO 0 "fpr_reg_operand")
> - (const_int 0))]
> - "TARGET_MMA"
> -{
> - rtx xo0 = gen_rtx_UNSPEC (XOmode, gen_rtvec (1, const0_rtx),
> - UNSPEC_MMA_XXSETACCZ);
> - emit_insn (gen_rtx_SET (operands[0], xo0));
> - DONE;
> -})
> -
> -(define_insn_and_split "*mma_xxsetaccz"
> +(define_insn "mma_xxsetaccz"
> [(set (match_operand:XO 0 "fpr_reg_operand" "=d")
> - (unspec:XO [(match_operand 1 "const_0_to_1_operand" "O")]
> - UNSPEC_MMA_XXSETACCZ))]
> + (unspec_volatile:XO [(const_int 0)]
> + UNSPECV_MMA_XXSETACCZ))]
> "TARGET_MMA"
> "xxsetaccz %A0"
> - "&& reload_completed"
> - [(set (match_dup 0) (unspec:XO [(match_dup 1)] UNSPEC_MMA_XXSETACCZ))]
> - ""
> [(set_attr "type" "mma")
> (set_attr "length" "4")])
>
> diff --git a/gcc/config/rs6000/rs6000.c b/gcc/config/rs6000/rs6000.c
> index e073b26b430..40dc71c8171 100644
> --- a/gcc/config/rs6000/rs6000.c
> +++ b/gcc/config/rs6000/rs6000.c
> @@ -21919,7 +21919,7 @@ rs6000_rtx_costs (rtx x, machine_mode mode, int outer_code,
> break;
>
> case UNSPEC:
> - if (XINT (x, 1) == UNSPEC_MMA_XXSETACCZ)
> + if (XINT (x, 1) == UNSPECV_MMA_XXSETACCZ)
> {
> *total = 0;
> return true;
> diff --git a/gcc/testsuite/gcc.target/powerpc/mma-builtin-6.c b/gcc/testsuite/gcc.target/powerpc/mma-builtin-6.c
> index 0c6517211e3..715b28138e9 100644
> --- a/gcc/testsuite/gcc.target/powerpc/mma-builtin-6.c
> +++ b/gcc/testsuite/gcc.target/powerpc/mma-builtin-6.c
> @@ -5,14 +5,16 @@
> void
> foo (__vector_quad *dst)
> {
> - __vector_quad acc;
> - __builtin_mma_xxsetaccz (&acc);
> - *dst = acc;
> + __vector_quad acc0, acc1;
> + __builtin_mma_xxsetaccz (&acc0);
> + __builtin_mma_xxsetaccz (&acc1);
> + dst[0] = acc0;
> + dst[1] = acc1;
> }
>
> /* { dg-final { scan-assembler-not {\mlxv\M} } } */
> /* { dg-final { scan-assembler-not {\mlxvp\M} } } */
> /* { dg-final { scan-assembler-not {\mxxmtacc\M} } } */
> -/* { dg-final { scan-assembler-times {\mxxsetaccz\M} 1 } } */
> -/* { dg-final { scan-assembler-times {\mxxmfacc\M} 1 } } */
> -/* { dg-final { scan-assembler-times {\mstxvp\M} 2 } } */
> +/* { dg-final { scan-assembler-times {\mxxsetaccz\M} 2 } } */
> +/* { dg-final { scan-assembler-times {\mxxmfacc\M} 2 } } */
> +/* { dg-final { scan-assembler-times {\mstxvp\M} 4 } } */
next prev parent reply other threads:[~2021-09-12 15:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 19:58 Peter Bergner
2021-09-12 15:32 ` Bill Schmidt [this message]
2021-09-12 19:26 ` Segher Boessenkool
2021-09-13 22:10 ` Peter Bergner
2021-09-14 0:17 ` Segher Boessenkool
2021-09-14 15:58 ` Peter Bergner
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=76dc14a6-3702-d391-f97e-df9bd72c9ef2@linux.ibm.com \
--to=wschmidt@linux.ibm.com \
--cc=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--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).