public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Robin Dapp <rdapp.gcc@gmail.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] internal-fn: Do not force vcond operand to reg.
Date: Fri, 10 May 2024 15:21:21 +0200	[thread overview]
Message-ID: <CAFiYyc3iX50j87=u9TBr7jVf6mi+hZ0P4vQZP61C_exG8nQFoA@mail.gmail.com> (raw)
In-Reply-To: <4ee89471-d998-4734-a7d3-1f947d0d9f22@gmail.com>

On Fri, May 10, 2024 at 3:18 PM Robin Dapp <rdapp.gcc@gmail.com> wrote:
>
> Hi,
>
> this only forces the first comparison operator into a register if it is
> not already suitable.
>
> Bootstrap and regtest is running on x86 and aarch64, successful on p10.
> Regtested on riscv.

How does this make a difference in the end?  I'd expect say forwprop to
fix things?

> gcc/ChangeLog:
>
>         PR middle-end/113474
>
>         * internal-fn.cc (expand_vec_cond_mask_optab_fn):  Only force
>         op1 to reg if necessary.
>
> gcc/testsuite/ChangeLog:
>
>         * gcc.target/riscv/rvv/autovec/pr113474.c: New test.
>
> Regards
>  Robin
>
> ---
>  gcc/internal-fn.cc                                  |  3 ++-
>  .../gcc.target/riscv/rvv/autovec/pr113474.c         | 13 +++++++++++++
>  2 files changed, 15 insertions(+), 1 deletion(-)
>  create mode 100644 gcc/testsuite/gcc.target/riscv/rvv/autovec/pr113474.c
>
> diff --git a/gcc/internal-fn.cc b/gcc/internal-fn.cc
> index 2c764441cde..72cc6b7a1f7 100644
> --- a/gcc/internal-fn.cc
> +++ b/gcc/internal-fn.cc
> @@ -3164,7 +3164,8 @@ expand_vec_cond_mask_optab_fn (internal_fn, gcall *stmt, convert_optab optab)
>    rtx_op2 = expand_normal (op2);
>
>    mask = force_reg (mask_mode, mask);
> -  rtx_op1 = force_reg (mode, rtx_op1);
> +  if (!insn_operand_matches (icode, 1, rtx_op1))
> +    rtx_op1 = force_reg (mode, rtx_op1);
>
>    rtx target = expand_expr (lhs, NULL_RTX, VOIDmode, EXPAND_WRITE);
>    create_output_operand (&ops[0], target, mode);
> diff --git a/gcc/testsuite/gcc.target/riscv/rvv/autovec/pr113474.c b/gcc/testsuite/gcc.target/riscv/rvv/autovec/pr113474.c
> new file mode 100644
> index 00000000000..0364bf9f5e3
> --- /dev/null
> +++ b/gcc/testsuite/gcc.target/riscv/rvv/autovec/pr113474.c
> @@ -0,0 +1,13 @@
> +/* { dg-do compile { target riscv_v } }  */
> +/* { dg-additional-options "-std=c99" }  */
> +
> +void
> +foo (int n, int **a)
> +{
> +  int b;
> +  for (b = 0; b < n; b++)
> +    for (long e = 8; e > 0; e--)
> +      a[b][e] = a[b][e] == 15;
> +}
> +
> +/* { dg-final { scan-assembler "vmerge.vim" } }  */
> --
> 2.45.0

  reply	other threads:[~2024-05-10 13:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-10 13:17 Robin Dapp
2024-05-10 13:21 ` Richard Biener [this message]
2024-05-13  6:18   ` Robin Dapp
2024-05-13  7:53     ` Richard Biener
2024-05-13 14:14       ` Robin Dapp
2024-05-13 14:19         ` Richard Biener
2024-05-17 10:35           ` Robin Dapp

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='CAFiYyc3iX50j87=u9TBr7jVf6mi+hZ0P4vQZP61C_exG8nQFoA@mail.gmail.com' \
    --to=richard.guenther@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rdapp.gcc@gmail.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).