public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tamar Christina <Tamar.Christina@arm.com>
To: Richard Biener <rguenther@suse.de>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, nd <nd@arm.com>,
	"law@redhat.com"	<law@redhat.com>, "ian@airs.com" <ian@airs.com>,
	"rdsandiford@googlemail.com"	<rdsandiford@googlemail.com>
Subject: RE: [GCC][PATCH][mid-end] Optimize x * copysign (1.0, y) [Patch (1/2)]
Date: Tue, 13 Jun 2017 10:17:00 -0000	[thread overview]
Message-ID: <VI1PR0801MB203199FB1CBA03E84324F225FFC20@VI1PR0801MB2031.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <alpine.LSU.2.20.1706121053440.7349@zhemvz.fhfr.qr>

Hi Richard,

Thanks for the feedback, I'll update the patch accordingly.

> What does
> 
> >       (copysigns @0 (negate @1)): Likewise.
> 
> do?
> 

Sorry this slipped through my clean-up. The patch doesn't actually contain this definition anymore.

> Third, new IL that is present throughout the compilation always poses the
> risk that while passes may be able to handle copysign they do not handle
> xorsign (vectorization?).  In this case it looks like the matching is simply to
> enhance RTL expansion which means it should ideally be done close to RTL
> expansion only.  If you write
> 
> (match (xorsign_p @0 @1)
>  (mult:c (copysign real_onep @0) @1))
> 
> you can call gimple_xorsign_p (you need to declare it, see the generated
> gimple-match.c file for the definition) from, say,
> pass_optimize_widening_mul, which despite its name is used as a kitchen-
> sink for late GIMPLE pattern-matching stuff to enhance RTL expansion /
> instruction selection.
> 
> Thanks,
> Richard.
> 
> >
> > gcc/
> > 2017-06-07  Tamar Christina  <tamar.christina@arm.com>
> >
> > 	* builtins.def (BUILT_IN_XORSIGN, BUILT_IN_XORSIGNF): New.
> > 	(BUILT_IN_XORSIGNL, BUILT_IN_XORSIGN_FLOAT_NX): Likewise.
> > 	* match.pd (mult (COPYSIGN:s real_onep @0) @1): New simplifier.
> > 	(mult (COPYSIGN:s real_mus_onep @0) @1): Likewise.
> > 	(copysigns @0 (negate @1)): Likewise.
> > 	* builtins.c (expand_builtin_copysign): Promoted local to argument.
> > 	(expand_builtin): Added CASE_FLT_FN_FLOATN_NX
> (BUILT_IN_XORSIGN) and
> > 	CASE_FLT_FN (BUILT_IN_XORSIGN).
> > 	(BUILT_IN_COPYSIGN): Updated function call.
> > 	* optabs.h (expand_copysign): New bool.
> > 	(expand_xorsign): New.
> > 	* optabs.def (xorsign_optab): New.
> > 	* optabs.c (expand_copysign): New parameter.
> > 	* fortran/f95-lang.c (xorsignl, xorsign, xorsignf): New.
> > 	* fortran/mathbuiltins.def (XORSIGN): New.
> >
> > gcc/testsuite/
> > 2017-06-07  Tamar Christina  <tamar.christina@arm.com>
> >
> > 	* gcc.dg/tree-ssa/xorsign.c: New.
> > 	* gcc.dg/xorsign_exec.c: New.
> > 	* gcc.dg/vec-xorsign_exec.c: New.
> > 	* gcc.dg/tree-ssa/reassoc-39.c (f2, f3): Updated constant to 2.
> 
> --
> Richard Biener <rguenther@suse.de>
> SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, Graham Norton,
> HRB 21284 (AG Nuernberg)

  parent reply	other threads:[~2017-06-13 10:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-12  7:56 Tamar Christina
2017-06-12  9:10 ` Richard Biener
2017-06-12 16:27   ` Richard Sandiford
2017-06-13 10:22     ` Tamar Christina
2017-06-13 10:17   ` Tamar Christina [this message]
2017-06-12 16:52 ` Joseph Myers
2017-06-12 19:50 ` Michael Meissner
2017-06-13 10:14   ` Tamar Christina
2017-06-24 23:53 ` Andrew Pinski
2017-06-26  2:09   ` Andrew Pinski
2017-06-26  8:46     ` Tamar Christina
2017-06-26  7:26   ` Richard Biener
2017-07-09 23:21 ` Andrew Pinski
2017-07-10 15:47   ` Tamar Christina
2017-07-18  8:05     ` Tamar Christina
2017-07-18  8:38     ` Richard Biener
2017-07-18  9:22       ` Tamar Christina
2017-07-18 10:19         ` Richard Biener
2017-07-18 11:00           ` Tamar Christina
2017-07-18 11:19             ` Richard Biener
2017-07-18 11:24               ` Tamar Christina

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=VI1PR0801MB203199FB1CBA03E84324F225FFC20@VI1PR0801MB2031.eurprd08.prod.outlook.com \
    --to=tamar.christina@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ian@airs.com \
    --cc=law@redhat.com \
    --cc=nd@arm.com \
    --cc=rdsandiford@googlemail.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).