public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <rguenther@suse.de>
To: Robin Dapp <rdapp.gcc@gmail.com>
Cc: Andrew Pinski <pinskia@gmail.com>,
	 "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
	 gcc-patches <gcc-patches@gcc.gnu.org>,
	"pan2.li" <pan2.li@intel.com>,
	 Richard Biener <richard.guenther@gmail.com>,
	richard.sandiford@arm.com
Subject: Re: [PATCH] fold-const: Handle AND, IOR, XOR with stepped vectors [PR112971].
Date: Tue, 16 Jan 2024 08:17:59 +0100 (CET)	[thread overview]
Message-ID: <n549nq20-r343-673p-s8nq-0523s822sr1s@fhfr.qr> (raw)
In-Reply-To: <7b8d117c-c01a-49d4-9f50-c7e2bfa34ba1@gmail.com>

On Mon, 15 Jan 2024, Robin Dapp wrote:

> I gave it another shot now by introducing a separate function as
> Richard suggested.  It's probably not at the location he intended.
> 
> The way I read the discussion there hasn't been any consensus
> on how (or rather where) to properly tackle the problem.  Any
> other ideas still?

I'm happy enough with the patch, esp. at this stage.  OK if
Richard S. doesn't disagree.

Thanks,
Richard.

> Regards
>  Robin
> 
> 
> Found in PR112971 this patch adds folding support for bitwise operations
> of const duplicate zero/one vectors with stepped vectors.
> On riscv we have the situation that a folding would perpetually continue
> without simplifying because e.g. {0, 0, 0, ...} & {7, 6, 5, ...} would
> not be folded to {0, 0, 0, ...}.
> 
> gcc/ChangeLog:
> 
> 	PR middle-end/112971
> 
> 	* fold-const.cc (simplify_const_binop): New function for binop
> 	simplification of two constant vectors when element-wise
> 	handling is not necessary.
> 	(const_binop): Call new function.
> 
> gcc/testsuite/ChangeLog:
> 
> 	* gcc.target/riscv/rvv/autovec/pr112971.c: New test.
> ---
>  gcc/fold-const.cc                             | 31 +++++++++++++++++++
>  .../gcc.target/riscv/rvv/autovec/pr112971.c   | 18 +++++++++++
>  2 files changed, 49 insertions(+)
>  create mode 100644 gcc/testsuite/gcc.target/riscv/rvv/autovec/pr112971.c
> 
> diff --git a/gcc/fold-const.cc b/gcc/fold-const.cc
> index 385e4a69ab3..2ef425aec0f 100644
> --- a/gcc/fold-const.cc
> +++ b/gcc/fold-const.cc
> @@ -1343,6 +1343,29 @@ distributes_over_addition_p (tree_code op, int opno)
>      }
>  }
>  
> +/* OP is the INDEXth operand to CODE (counting from zero) and OTHER_OP
> +   is the other operand.  Try to use the value of OP to simplify the
> +   operation in one step, without having to process individual elements.  */
> +static tree
> +simplify_const_binop (tree_code code, tree op, tree other_op,
> +		      int index ATTRIBUTE_UNUSED)
> +{
> +  /* AND, IOR as well as XOR with a zerop can be simplified directly.  */
> +  if (TREE_CODE (op) == VECTOR_CST && TREE_CODE (other_op) == VECTOR_CST)
> +    {
> +      if (integer_zerop (other_op))
> +	{
> +	  if (code == BIT_IOR_EXPR || code == BIT_XOR_EXPR)
> +	    return op;
> +	  else if (code == BIT_AND_EXPR)
> +	    return other_op;
> +	}
> +    }
> +
> +  return NULL_TREE;
> +}
> +
> +
>  /* Combine two constants ARG1 and ARG2 under operation CODE to produce a new
>     constant.  We assume ARG1 and ARG2 have the same data type, or at least
>     are the same kind of constant and the same machine mode.  Return zero if
> @@ -1646,6 +1669,14 @@ const_binop (enum tree_code code, tree arg1, tree arg2)
>  	return build_complex (type, real, imag);
>      }
>  
> +  tree simplified;
> +  if ((simplified = simplify_const_binop (code, arg1, arg2, 0)))
> +    return simplified;
> +
> +  if (commutative_tree_code (code)
> +      && (simplified = simplify_const_binop (code, arg2, arg1, 1)))
> +    return simplified;
> +
>    if (TREE_CODE (arg1) == VECTOR_CST
>        && TREE_CODE (arg2) == VECTOR_CST
>        && known_eq (TYPE_VECTOR_SUBPARTS (TREE_TYPE (arg1)),
> diff --git a/gcc/testsuite/gcc.target/riscv/rvv/autovec/pr112971.c b/gcc/testsuite/gcc.target/riscv/rvv/autovec/pr112971.c
> new file mode 100644
> index 00000000000..816ebd3c493
> --- /dev/null
> +++ b/gcc/testsuite/gcc.target/riscv/rvv/autovec/pr112971.c
> @@ -0,0 +1,18 @@
> +/* { dg-do compile }  */
> +/* { dg-options "-march=rv64gcv_zvl256b -mabi=lp64d -O3 -fno-vect-cost-model" }  */
> +
> +int a;
> +short b[9];
> +char c, d;
> +void e() {
> +  d = 0;
> +  for (;; d++) {
> +    if (b[d])
> +      break;
> +    a = 8;
> +    for (; a >= 0; a--) {
> +      char *f = &c;
> +      *f &= d == (a & d);
> +    }
> +  }
> +}
> 

-- 
Richard Biener <rguenther@suse.de>
SUSE Software Solutions Germany GmbH,
Frankenstrasse 146, 90461 Nuernberg, Germany;
GF: Ivo Totev, Andrew McDonald, Werner Knoblich; (HRB 36809, AG Nuernberg)

  reply	other threads:[~2024-01-16  7:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-18 19:50 Robin Dapp
2023-12-18 22:49 ` 钟居哲
2023-12-19  8:15   ` Richard Biener
2023-12-19  8:54     ` juzhe.zhong
2023-12-19  9:12       ` Richard Biener
2023-12-19  9:35         ` juzhe.zhong
2023-12-19  9:45           ` Jakub Jelinek
2023-12-19  9:49             ` juzhe.zhong
2023-12-19  9:55               ` Jakub Jelinek
2023-12-19 10:11           ` Richard Biener
2023-12-19 10:40             ` Richard Sandiford
2023-12-19 10:58               ` juzhe.zhong
2023-12-20  2:04               ` Andrew Pinski
2023-12-20  2:07                 ` juzhe.zhong
2023-12-20  7:25                 ` Richard Biener
2023-12-20  9:33                   ` Richard Sandiford
2023-12-20 10:06                     ` Richard Biener
2024-01-15 15:23                 ` Robin Dapp
2024-01-16  7:17                   ` Richard Biener [this message]
2024-01-24 11:29                     ` Richard Sandiford

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=n549nq20-r343-673p-s8nq-0523s822sr1s@fhfr.qr \
    --to=rguenther@suse.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=juzhe.zhong@rivai.ai \
    --cc=pan2.li@intel.com \
    --cc=pinskia@gmail.com \
    --cc=rdapp.gcc@gmail.com \
    --cc=richard.guenther@gmail.com \
    --cc=richard.sandiford@arm.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).