public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mikael Morin <morin-mikael@orange.fr>
To: Andrew Pinski <apinski@marvell.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 6/7] MATCH: Factor out code that for min max detection with constants
Date: Tue, 25 Apr 2023 12:45:26 +0200	[thread overview]
Message-ID: <d3449c49-3173-6a2f-efe0-7e4884fd7695@orange.fr> (raw)
In-Reply-To: <20230424213011.528181-7-apinski@marvell.com>

Hello,

> diff --git a/gcc/fold-const.cc b/gcc/fold-const.cc
> index 3b397ae2941..b8add24f874 100644
> --- a/gcc/fold-const.cc
> +++ b/gcc/fold-const.cc
> @@ -150,6 +150,49 @@ static tree fold_convert_const (enum tree_code, tree, tree);
>   static tree fold_view_convert_expr (tree, tree);
>   static tree fold_negate_expr (location_t, tree);
>   
> +/* This is a helper function to detect min/max for some operands of COND_EXPR.
> +   The form is "(EXP0 CMP EXP1) ? EXP2 : EXP3". */
> +tree_code
> +minmax_from_comparison (tree_code cmp, tree exp0, tree exp1, tree exp2, tree exp3)
> +{
> +  enum tree_code code = ERROR_MARK;
> +
> +  if (HONOR_NANS (exp0) || HONOR_SIGNED_ZEROS (exp0))
> +    return ERROR_MARK;
> +
> +  if (!operand_equal_p (exp0, exp2))
> +    return ERROR_MARK;
> +
> +  if (TREE_CODE (exp1) == INTEGER_CST && TREE_CODE (exp1) == INTEGER_CST

one of these conditions should probably be TREE_CODE (exp3) == INTEGER_CST?

> +      && wi::to_widest (exp1) == (wi::to_widest (exp3) - 1))
> +    {
> +      /* X <= Y - 1 equals to X < Y.  */
> +      if (cmp == LE_EXPR)
> +	code = LT_EXPR;
> +      /* X > Y - 1 equals to X >= Y.  */
> +      if (cmp == GT_EXPR)
> +	code = GE_EXPR;
> +    }
> +  if (TREE_CODE (exp3) == INTEGER_CST && TREE_CODE (exp1) == INTEGER_CST
> +      && wi::to_widest (exp1) == (wi::to_widest (exp3) + 1))
> +    {
> +     /* X < Y + 1 equals to X <= Y.  */
> +     if (cmp == LT_EXPR)
> +	code = LE_EXPR;
> +    /* X >= Y + 1 equals to X > Y.  */
> +    if (cmp == GE_EXPR)
> +	code = GT_EXPR;
> +    }


Mikael


  reply	other threads:[~2023-04-25 10:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-24 21:30 [PATCH 0/7] Some more phiopt cleanups and double minmax to match Andrew Pinski
2023-04-24 21:30 ` [PATCH 1/7] PHIOPT: Split out store elimination from phiopt Andrew Pinski
2023-04-27 10:50   ` Richard Biener
2023-04-24 21:30 ` [PATCH 2/7] PHIOPT: Rename tree_ssa_phiopt_worker to pass_phiopt::execute Andrew Pinski
2023-04-27 10:58   ` Richard Biener
2023-04-24 21:30 ` [PATCH 3/7] PHIOPT: Move store_elim_worker into pass_cselim::execute Andrew Pinski
2023-04-27 10:50   ` Richard Biener
2023-04-24 21:30 ` [PATCH 4/7] MIN/MAX should be treated similar as comparisons for trapping Andrew Pinski
2023-04-27 10:49   ` Richard Biener
2023-04-24 21:30 ` [PATCH 5/7] PHIOPT: Allow MIN/MAX to have up to 2 MIN/MAX expressions for early phiopt Andrew Pinski
2023-04-27 10:51   ` Richard Biener
2023-04-24 21:30 ` [PATCH 6/7] MATCH: Factor out code that for min max detection with constants Andrew Pinski
2023-04-25 10:45   ` Mikael Morin [this message]
2023-04-24 21:30 ` [PATCH 7/7] MATCH: Add patterns from phiopt's minmax_replacement Andrew Pinski
2023-04-27 10:58   ` Richard Biener

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=d3449c49-3173-6a2f-efe0-7e4884fd7695@orange.fr \
    --to=morin-mikael@orange.fr \
    --cc=apinski@marvell.com \
    --cc=gcc-patches@gcc.gnu.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).