public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Xi Ruoyao <xry111@xry111.site>
Cc: gcc-patches@gcc.gnu.org, chenglulu <chenglulu@loongson.cn>,
	i@xen0n.name,  xuchenghua@loongson.cn,
	Tamar Christina <Tamar.Christina@arm.com>,
	tschwinge@gcc.gnu.org,  Roger Sayle <roger@nextmovesoftware.com>,
	Andrew Pinski <pinskia@gmail.com>
Subject: Re: [PATCH] Only allow (copysign x, NEG_CONST) -> (fneg (fabs x)) simplification for constant folding [PR112483]
Date: Tue, 14 Nov 2023 11:44:50 +0100	[thread overview]
Message-ID: <CAFiYyc2BWEubDMzg7Fcqt9DFLwjcdzigkz6CEEYRwS2uw19vwQ@mail.gmail.com> (raw)
In-Reply-To: <20231114100320.47373-1-xry111@xry111.site>

On Tue, Nov 14, 2023 at 11:04 AM Xi Ruoyao <xry111@xry111.site> wrote:
>
> From: Andrew Pinski <pinskia@gmail.com>
>
> On targets with native copysign instructions, (copysign x, -1) is
> usually more efficient than (fneg (fabs x)).  Since r14-5284, in the
> middle end we always optimize (fneg (fabs x)) to (copysign x, -1), not
> vice versa.  If the target does not support native fcopysign,
> expand_COPYSIGN will expand it as (fneg (fabs x)) anyway.
>
> gcc/ChangeLog:
>
>         PR rtl-optimization/112483
>         * simplify-rtx.cc (simplify_binary_operation_1) <case COPYSIGN>:
>         Call simplify_unary_operation for NEG instead of
>         simplify_gen_unary.
> ---
>
> [xry111]:
>
> Following Andrew's suggestion, I bootstrapped and regtested this
> patch on loongarch64-linux-gnu.  Now with
>
>         float t(float x)
>         {
>           return __builtin_copysignf(x, -0.1234);
>         }
>
> It correctly generates
>
>         pcalau12i       $r12,%pc_hi20(.LC0)
>         fld.s   $f1,$r12,%pc_lo12(.LC0)
>         fcopysign.s     $f0,$f0,$f1
>         jr      $r1
>
> instead of the de-optimized fabs.s and fneg.s
>
> Ok for trunk?
>
>  gcc/simplify-rtx.cc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gcc/simplify-rtx.cc b/gcc/simplify-rtx.cc
> index 2d2e5a3c1ca..f3745d86aea 100644
> --- a/gcc/simplify-rtx.cc
> +++ b/gcc/simplify-rtx.cc
> @@ -4392,7 +4392,7 @@ simplify_ashift:
>           real_convert (&f1, mode, CONST_DOUBLE_REAL_VALUE (trueop1));
>           rtx tmp = simplify_gen_unary (ABS, mode, op0, mode);
>           if (REAL_VALUE_NEGATIVE (f1))
> -           tmp = simplify_gen_unary (NEG, mode, tmp, mode);
> +           tmp = simplify_unary_operation (NEG, mode, tmp, mode);

shouldn't that be when either the ABS or the NEG simplify?  And I wonder
when that happens - I suppose when op0 is CONST_DOUBLE only?

>           return tmp;
>         }
>        if (GET_CODE (op0) == NEG || GET_CODE (op0) == ABS)
> --
> 2.42.1
>

  reply	other threads:[~2023-11-14 10:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14  9:59 Xi Ruoyao
2023-11-14 10:44 ` Richard Biener [this message]
2023-11-14 21:14   ` Xi Ruoyao
2023-11-15 11:41     ` 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=CAFiYyc2BWEubDMzg7Fcqt9DFLwjcdzigkz6CEEYRwS2uw19vwQ@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=Tamar.Christina@arm.com \
    --cc=chenglulu@loongson.cn \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=i@xen0n.name \
    --cc=pinskia@gmail.com \
    --cc=roger@nextmovesoftware.com \
    --cc=tschwinge@gcc.gnu.org \
    --cc=xry111@xry111.site \
    --cc=xuchenghua@loongson.cn \
    /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).