From: Alexander Monakov <amonakov@ispras.ru>
To: Cesar Philippidis <cesar@codesourcery.com>
Cc: Nathan Sidwell <nathan@acm.org>,
Andrew Pinski <pinskia@gmail.com>,
Richard Biener <richard.guenther@gmail.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: inhibit the sincos optimization when the target has sin and cos instructions
Date: Thu, 19 May 2016 11:29:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.20.1605191420350.2650@monopod.intra.ispras.ru> (raw)
In-Reply-To: <573D3642.8080203@codesourcery.com>
On Wed, 18 May 2016, Cesar Philippidis wrote:
> >> +(define_expand "sincossf3"
> >> + [(set (match_operand:SF 0 "nvptx_register_operand" "=R")
> >> + (unspec:SF [(match_operand:SF 2 "nvptx_register_operand" "R")]
> >> + UNSPEC_COS))
> >> + (set (match_operand:SF 1 "nvptx_register_operand" "=R")
> >> + (unspec:SF [(match_dup 2)] UNSPEC_SIN))]
> >> + "flag_unsafe_math_optimizations"
> >> +{
> >> + emit_insn (gen_sinsf2 (operands[1], operands[2]));
> >> + emit_insn (gen_cossf2 (operands[0], operands[2]));
> >> +
> >> + DONE;
> >> +})
> >
> > Why the emit_insn code? that seems to be replicating the RTL
> > representation -- you're saying the same thing twice.
> >
> > Doesn't operands[2] need (conditionally) copying to a new register --
> > what if it aliases operands[1]?
>
> This patch does that now.
Note that the documentation suggests using 'make_safe_from' to concisely
express conflict resolution:
> diff --git a/gcc/config/nvptx/nvptx.md b/gcc/config/nvptx/nvptx.md
> index 33a4862..69bbb22 100644
> --- a/gcc/config/nvptx/nvptx.md
> +++ b/gcc/config/nvptx/nvptx.md
> @@ -794,6 +794,24 @@
> ""
> "%.\\tsqrt%#%t0\\t%0, %1;")
>
> +(define_expand "sincossf3"
> + [(set (match_operand:SF 0 "nvptx_register_operand" "=R")
> + (unspec:SF [(match_operand:SF 2 "nvptx_register_operand" "R")]
> + UNSPEC_COS))
> + (set (match_operand:SF 1 "nvptx_register_operand" "=R")
> + (unspec:SF [(match_dup 2)] UNSPEC_SIN))]
> + "flag_unsafe_math_optimizations"
... here instead of special-casing the conflict case in curly braces you can
just write:
"operands[2] = make_safe_from (operands[2], operands[0]);"
> +{
> + if (REGNO (operands[0]) == REGNO (operands[2]))
> + {
> + rtx tmp = gen_reg_rtx (GET_MODE (operands[2]));
> + emit_insn (gen_rtx_SET (tmp, operands[2]));
> + emit_insn (gen_sinsf2 (operands[1], tmp));
> + emit_insn (gen_cossf2 (operands[0], tmp));
> + DONE;
> + }
> +})
Alexander
next prev parent reply other threads:[~2016-05-19 11:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 19:19 Cesar Philippidis
2016-05-13 19:58 ` Richard Biener
2016-05-13 20:13 ` Andrew Pinski
2016-05-17 21:10 ` Cesar Philippidis
2016-05-17 21:23 ` Andrew Pinski
2016-05-17 21:30 ` Cesar Philippidis
2016-05-18 12:29 ` Nathan Sidwell
2016-05-19 3:43 ` Cesar Philippidis
2016-05-19 11:29 ` Alexander Monakov [this message]
2016-05-19 18:42 ` Cesar Philippidis
2016-05-19 23:30 ` Nathan Sidwell
2016-05-19 23:12 ` Nathan Sidwell
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=alpine.LNX.2.20.1605191420350.2650@monopod.intra.ispras.ru \
--to=amonakov@ispras.ru \
--cc=cesar@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nathan@acm.org \
--cc=pinskia@gmail.com \
--cc=richard.guenther@gmail.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).