public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Roger Sayle <roger@eyesopen.com>
To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: Question on valid transformations for cbrt
Date: Sun, 07 Mar 2004 15:11:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0403070640560.29012-100000@www.eyesopen.com> (raw)
In-Reply-To: <200403061854.i26Isn2m018933@caip.rutgers.edu>


On Sat, 6 Mar 2004, Kaveh R. Ghazi wrote:
> I'm in the process of writing some transformations for builtin cbrt.
> However it occurs to me that certain combinations might be invalid
> when converting to pow, because pow doesn't like negative values with
> non-integral powers.  E.g.:
>
> 	cbrt(sqrt(x)) -> pow(x, 1/6)
>
> can be considered "safe" with -ffast-math IMO because if x was
> negative the original sqrt would have choked anyway.  However here:
>
> 	cbrt(pow(x,y)) -> pow(x,y/3)
>
> if x is negative and y is say 5, the first form would succeed but the
> second would get an error EDOM because 5/3 is non-integral.  So I
> don't think the latter is a valid transformation even with
> -ffast-math.
>
> (Perhaps the latter is okay if x passes tree_expr_nonnegative_p, but
> that might not be worth it.)
>
> Thoughts?

I think you're right, and we can't in general simplify cbrt(pow(x,y))
even with -ffast-math.  I've had to give some thought to GCC's existing
sqrt(pow(x,y)) to see whether we need to disable that.  However I've
conviced myself that its safe with -ffast-math.  If x is negative,
y must be an integer to satisfy pow, and then must be an even integer
to satisfy sqrt.  Hence our existing transform is safe.

The problem with cbrt, unlike sqrt, is that its is more expressive than
pow.  i.e. cbrt(-29.7) = -3.1 but pow(-29.7,1.0/3.0) => EDOM.  Hence
we can't normalize cbrt(x) as pow(x,1.0/3.0), but we can safely go the
other way pow(x,1.0/3.0) => cbrt(x).

Roger
--

  reply	other threads:[~2004-03-07 15:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-06 18:54 Kaveh R. Ghazi
2004-03-07 15:11 ` Roger Sayle [this message]
2004-03-10 15:32   ` Segher Boessenkool
2004-03-10 16:06     ` Robert Dewar
2004-04-02  0:22   ` Geoff Keating

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=Pine.LNX.4.44.0403070640560.29012-100000@www.eyesopen.com \
    --to=roger@eyesopen.com \
    --cc=gcc@gcc.gnu.org \
    --cc=ghazi@caip.rutgers.edu \
    /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).