public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tamar Christina <Tamar.Christina@arm.com>
To: Jeff Law <jeffreyalaw@gmail.com>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: nd <nd@arm.com>, "rguenther@suse.de" <rguenther@suse.de>,
	"jlaw@ventanamicro.com" <jlaw@ventanamicro.com>
Subject: RE: [PATCH]middle-end match.pd: optimize fneg (fabs (x)) to x | (1 << signbit(x)) [PR109154]
Date: Thu, 5 Oct 2023 18:09:50 +0000	[thread overview]
Message-ID: <VI1PR08MB5325B21B06D84B5E1B1D2FDFFFCAA@VI1PR08MB5325.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <5535287f-43af-4c04-bd3d-47f2075f61ed@gmail.com>

> > b17e1136600a 100644
> > --- a/gcc/match.pd
> > +++ b/gcc/match.pd
> > @@ -9476,3 +9476,57 @@ and,
> >         }
> >         (if (full_perm_p)
> >   	(vec_perm (op@3 @0 @1) @3 @2))))))
> > +
> > +/* Transform fneg (fabs (X)) -> X | 1 << signbit (X).  */
> > +
> > +(simplify
> > + (negate (abs @0))
> > + (if (FLOAT_TYPE_P (type)
> > +      /* We have to delay this rewriting till after forward prop because
> otherwise
> > +	 it's harder to do trigonometry optimizations. e.g. cos(-fabs(x)) is not
> > +	 matched in one go.  Instead cos (-x) is matched first followed by
> cos(|x|).
> > +	 The bottom op approach makes this rule match first and it's not untill
> > +	 fwdprop that we match top down.  There are manu such
> simplications
> > +so we
> Multiple typos this line.  fwdprop->fwprop manu->many
> simplications->simplifications.
> 
> OK with the typos fixed.

Ah I think you missed the previous emails from Richi whom wanted this canonicalized to
copysign instead. I've just finished doing so and will send the updated patch 😊

> 
> Thanks.  I meant to say hi at the Cauldron, but never seemed to get away long
> enough to find you..

Hehehe Indeed, I think I only saw you once and then *poof* like a ninja you were gone!

Next time 😊

Cheers,
Tamar

> 
> jeff


      reply	other threads:[~2023-10-05 18:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-27  0:50 Tamar Christina
2023-09-27  1:17 ` Andrew Pinski
2023-09-27  2:31   ` Tamar Christina
2023-09-27  7:11     ` Richard Biener
2023-09-27  7:56       ` Tamar Christina
2023-09-27  9:35         ` Tamar Christina
2023-09-27  9:39           ` Richard Biener
2023-10-05 18:11             ` Tamar Christina
2023-10-06  6:24               ` Richard Biener
2023-10-07  9:22                 ` Richard Sandiford
2023-10-07 10:34                   ` Richard Biener
2023-10-07 11:34                     ` Richard Sandiford
2023-10-09  7:20                       ` Richard Biener
2023-10-09  7:36                         ` Andrew Pinski
2023-10-09  9:06                           ` Richard Biener
2023-09-29 15:00 ` Jeff Law
2023-10-05 18:09   ` Tamar Christina [this message]

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=VI1PR08MB5325B21B06D84B5E1B1D2FDFFFCAA@VI1PR08MB5325.eurprd08.prod.outlook.com \
    --to=tamar.christina@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=jlaw@ventanamicro.com \
    --cc=nd@arm.com \
    --cc=rguenther@suse.de \
    /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).