From: Roger Sayle <roger@eyesopen.com>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: <gcc@gcc.gnu.org>
Subject: Re: gcc bootstrap broken on i686-linux-gnu
Date: Tue, 30 Jul 2002 03:30:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0207291129150.23690-100000@www.eyesopen.com> (raw)
In-Reply-To: <200207291708.g6TH8ivR016713@hiauly1.hia.nrc.ca>
Hi Dave,
> > Certainly. Sorry for any inconvenience. The two possible
> > changes in behaviour are that -1.0*x is now tranformed into
> > -x by default (this previously only happened with -ffast-math),
>
> This transformation is going to cause a problem on hppa1* machines
> because prior to PA2.0 the HP IEEE implementation didn't have a
> fneg instruction. So, to get correct behavior we convert -x to
> -1.0*x (see for example negsf2 pattern in pa.md) except when
> flag_unsafe_math_optimizations is set where we use fsub.
Fortunately, the -1.0*x into x transformation is being applied in
fold-const.c, so works on the tree representation of the expression.
This should be completely safe, and allows things like
"x = (y<0)? -1.0*y : y" to be recognized as "x = fabs(y)".
If the "-y" survives until RTL generation time, the PA backend will
convert it back into the multiplication.
I agree there could be an issue if this transformation were to be
added to the RTL optimizers.
Roger
--
next prev parent reply other threads:[~2002-07-29 17:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-29 21:30 John David Anglin
2002-07-30 3:30 ` Roger Sayle [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-29 10:42 Andreas Jaeger
2002-07-29 16:46 ` Roger Sayle
2002-07-29 20:45 ` Andreas Jaeger
2002-07-30 2:09 ` Graham Stott
2002-07-30 3:31 ` Roger Sayle
2002-08-01 7:54 ` Andreas Jaeger
2002-08-01 9:04 ` Roger Sayle
2002-07-30 3:23 ` Roger Sayle
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.33.0207291129150.23690-100000@www.eyesopen.com \
--to=roger@eyesopen.com \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=gcc@gcc.gnu.org \
/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).