public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dale Johannesen <dalej@apple.com>
To: Robert Dewar <dewar@gnat.com>
Cc: "gcc@gcc.gnu.org list" <gcc@gcc.gnu.org>,
	Dale Johannesen <dalej@apple.com>
Subject: Re: -ffast-math and floating point reordering
Date: Sat, 27 Mar 2004 02:39:00 -0000	[thread overview]
Message-ID: <77168DC2-7F88-11D8-8C7F-000A95D7CD40@apple.com> (raw)
In-Reply-To: <4064CDD6.5030106@gnat.com>

On Mar 26, 2004, at 4:41 PM, Robert Dewar wrote:
> Dale Johannesen wrote:
>> One point I haven't seen yet:
>> A couple of strict-constructionists have asserted that people
>> who want reassociation done in a nonstandard way can easily rewrite 
>> their
>> code to achieve this.  This is not really true, because such 
>> expressions
>> often arise as a result of other optimizations, in a way that isn't 
>> obvious
>> from the source.  Offhand, inlining, unrolling, and constant/copy 
>> propagation
>> can all do it, and there are probably more.
>
> Well in the absence of the (very annoying) extra precision phenomenon,
> none of these optimizations should have observable effects.

Untrue.  If two of a+b+c are constant, for example, you want to add the
constants at compile time (assuming your requirements for accuracy
are satisfied).  This is exactly the sort of thing that's exposed by 
other
optimiziations.

  reply	other threads:[~2004-03-27  0:48 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-25  6:03 Joe Buck
2004-03-25  6:05 ` Ian Lance Taylor
2004-03-25 11:27   ` Robert Dewar
2004-03-25 11:31     ` Ian Lance Taylor
2004-03-25 11:55       ` Ben Elliston
2004-03-25 12:37       ` Robert Dewar
2004-03-25 10:22 ` Robert Dewar
2004-03-25 18:28   ` Joe Buck
2004-03-25 18:38     ` Dave Korn
2004-03-26 20:06     ` Robert Dewar
2004-03-26 20:18       ` Joe Buck
2004-03-25 16:12 ` Paul Koning
2004-03-25 18:46   ` Dale Johannesen
2004-03-25 20:11     ` Geert Bosch
2004-03-27  1:51     ` Robert Dewar
2004-03-27  2:39       ` Dale Johannesen [this message]
2004-03-26 18:18 ` law
2004-03-26 18:37   ` Joe Buck
2004-03-26 18:46     ` Diego Novillo
2004-03-26 19:03       ` Richard Guenther
2004-03-26 19:54         ` Fariborz Jahanian
2004-03-26 20:19         ` law
2004-03-26 22:08           ` Joe Buck
2004-03-27  0:42             ` Richard Henderson
2004-03-26 22:12     ` Joseph S. Myers
2004-03-26 21:48   ` Laurent GUERBY
2004-03-26 11:20 Bradley Lucier
2004-03-26 18:33 Robert Dewar
2004-03-26 22:22 Chris Lattner
2004-03-26 22:27 ` Chris Lattner

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=77168DC2-7F88-11D8-8C7F-000A95D7CD40@apple.com \
    --to=dalej@apple.com \
    --cc=dewar@gnat.com \
    --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).