From: Marc Glisse <marc.glisse@inria.fr>
To: Andrew Pinski <pinskia@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fold (a > 0 ? 1.0 : -1.0) into copysign (1.0, a) and a * copysign (1.0, a) into abs(a)
Date: Sun, 25 Jun 2017 08:28:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1706250909190.2070@stedding.saclay.inria.fr> (raw)
In-Reply-To: <CA+=Sn1m-pMkB1Vvoi3s_N0DSwLioB3T90778oSDQNOYME83txA@mail.gmail.com>
+(for cmp (gt ge lt le)
+ outp (convert convert negate negate)
+ outn (negate negate convert convert)
+ /* Transform (X > 0.0 ? 1.0 : -1.0) into copysign(1, X). */
+ /* Transform (X >= 0.0 ? 1.0 : -1.0) into copysign(1, X). */
+ /* Transform (X < 0.0 ? 1.0 : -1.0) into copysign(1,-X). */
+ /* Transform (X <= 0.0 ? 1.0 : -1.0) into copysign(1,-X). */
+ (simplify
+ (cond (cmp @0 real_zerop) real_onep real_minus_onep)
+ (if (!HONOR_NANS (type) && !HONOR_SIGNED_ZEROS (type)
+ && types_match (type, TREE_TYPE (@0)))
+ (switch
+ (if (types_match (type, float_type_node))
+ (BUILT_IN_COPYSIGNF { build_one_cst (type); } (outp @0)))
+ (if (types_match (type, double_type_node))
+ (BUILT_IN_COPYSIGN { build_one_cst (type); } (outp @0)))
+ (if (types_match (type, long_double_type_node))
+ (BUILT_IN_COPYSIGNL { build_one_cst (type); } (outp @0))))))
There is already a 1.0 of the right type in the input, it would be easier
to reuse it in the output than build a new one.
Non-generic builtins like copysign are such a pain... We also end up
missing the 128-bit case that way (pre-existing problem, not your patch).
We seem to have a corresponding internal function, but apparently it is
not used until expansion (well, maybe during vectorization).
+ /* Transform (X > 0.0 ? -1.0 : 1.0) into copysign(1,-X). */
+ /* Transform (X >= 0.0 ? -1.0 : 1.0) into copysign(1,-X). */
+ /* Transform (X < 0.0 ? -1.0 : 1.0) into copysign(1,X). */
+ /* Transform (X <= 0.0 ? -1.0 : 1.0) into copysign(1,X). */
+ (simplify
+ (cond (cmp @0 real_zerop) real_minus_onep real_onep)
+ (if (!HONOR_NANS (type) && !HONOR_SIGNED_ZEROS (type)
+ && types_match (type, TREE_TYPE (@0)))
+ (switch
+ (if (types_match (type, float_type_node))
+ (BUILT_IN_COPYSIGNF { build_one_cst (type); } (outn @0)))
+ (if (types_match (type, double_type_node))
+ (BUILT_IN_COPYSIGN { build_one_cst (type); } (outn @0)))
+ (if (types_match (type, long_double_type_node))
+ (BUILT_IN_COPYSIGNL { build_one_cst (type); } (outn @0)))))))
+
+/* Transform X * copysign (1.0, X) into abs(X). */
+(simplify
+ (mult:c @0 (COPYSIGN real_onep @0))
+ (if (!HONOR_NANS (type) && !HONOR_SIGNED_ZEROS (type))
+ (abs @0)))
I would have expected it do to the right thing for signed zero and qNaN.
Can you describe a case where it would give the wrong result, or are the
conditions just conservative?
+/* Transform X * copysign (1.0, -X) into -abs(X). */
+(simplify
+ (mult:c @0 (COPYSIGN real_onep (negate @0)))
+ (if (!HONOR_NANS (type) && !HONOR_SIGNED_ZEROS (type))
+ (negate (abs @0))))
+
+/* Transform copysign (-1.0, X) into copysign (1.0, X). */
+(simplify
+ (COPYSIGN real_minus_onep @0)
+ (COPYSIGN { build_one_cst (type); } @0))
(simplify
(COPYSIGN REAL_CST@0 @1)
(if (REAL_VALUE_NEGATIVE (TREE_REAL_CST (@0)))
(COPYSIGN (negate @0) @1)))
? Or does that create trouble with sNaN and only the 1.0 case is worth
the trouble?
--
Marc Glisse
next prev parent reply other threads:[~2017-06-25 8:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-24 21:56 Andrew Pinski
2017-06-25 8:28 ` Marc Glisse [this message]
2017-06-25 18:18 ` Andrew Pinski
2017-06-25 21:28 ` Andrew Pinski
2017-06-27 8:49 ` Richard Biener
2017-06-27 14:52 ` Tamar Christina
2017-06-27 14:57 ` Richard Biener
2017-06-27 17:52 ` Andrew Pinski
2017-06-28 7:37 ` Jakub Jelinek
2017-06-28 7:57 ` Uros Bizjak
2017-06-28 8:50 ` Christophe Lyon
2017-06-28 9:29 ` Richard Biener
2017-06-29 18:49 ` H.J. Lu
2017-06-26 8:45 ` Richard Sandiford
2017-06-26 15:22 ` Joseph Myers
2017-06-26 18:23 ` Richard Sandiford
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.DEB.2.20.1706250909190.2070@stedding.saclay.inria.fr \
--to=marc.glisse@inria.fr \
--cc=gcc-patches@gcc.gnu.org \
--cc=pinskia@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).