public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Craig Burley <burley@gnu.org>
To: jbuck@Synopsys.COM
Cc: burley@gnu.org
Subject: Re: FWD: FLOATING-POINT CONSISTENCY, -FFLOAT-STORE, AND X86
Date: Mon, 14 Dec 1998 22:54:00 -0000	[thread overview]
Message-ID: <199812150654.BAA01399@melange.gnu.org> (raw)
In-Reply-To: <199812150119.RAA03420@yamato.synopsys.com>

>> A little thought, planning, and lack of -O flags, and you can get huge
>> benefits from the 80-bit cells.
>
>It would seem that if we did 80-bit spills, then the -O flags would not
>affect the results (assuming that the original code uses parentheses
>to constrain the order of evaluation of FP expressions and that the
>optimizer avoids transformations that can change numerical results,
>such as pre-evaluating expressions with 64-bit that would otherwise
>be evaluated using 80-bit precision at runtime).

I wouldn't want us to say that, even assuming my proposal was adopted,
until we'd done at least a minimal audit of the compiler to reassure
ourselves that it was true.  Certainly I don't have enough confidence
or expertise to say it.

But it'd probably be nice if it was true, or could at least be made true
using an option or two!

        tq vm, (burley)

  parent reply	other threads:[~1998-12-14 22:54 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-13 18:23 Stephen L Moshier
1998-12-14  1:52 ` Harvey J. Stein
1998-12-14 14:56   ` Edward Jason Riedy
1998-12-14 17:20     ` Joe Buck
1998-12-14 18:51       ` Edward Jason Riedy
1998-12-14 21:54         ` Craig Burley
1998-12-15 14:31           ` Edward Jason Riedy
1998-12-15 17:11         ` Jamie Lokier
1998-12-16  0:26           ` Harvey J. Stein
1998-12-16  9:33             ` Craig Burley
1998-12-16 12:18               ` Harvey J. Stein
1998-12-16  9:38           ` Craig Burley
1998-12-16 12:25           ` Marc Lehmann
1998-12-16 12:50             ` Tim Hollebeek
1998-12-16 13:04               ` Harvey J. Stein
1998-12-16 14:01               ` Marc Lehmann
1998-12-17 11:26                 ` Dave Love
1998-12-17 15:06                   ` Marc Lehmann
1998-12-18 12:50                     ` Dave Love
1998-12-19 14:09                       ` Marc Lehmann
1998-12-20 11:28                         ` Dave Love
1998-12-20 11:24               ` Dave Love
1998-12-16 23:11           ` Joern Rennecke
1998-12-17  6:07             ` Jamie Lokier
1998-12-14 22:54       ` Craig Burley [this message]
1998-12-15  1:45 Geert Bosch
1998-12-15  3:34 ` Harvey J. Stein
1998-12-16 10:36   ` Craig Burley
1998-12-16 12:47     ` Harvey J. Stein
1998-12-17 10:22       ` Craig Burley
1998-12-17 14:54         ` Marc Lehmann
1998-12-19  0:27           ` Craig Burley
1998-12-19  5:06             ` Stephen L Moshier
1998-12-15  6:43 ` Stephen L Moshier
1998-12-16 10:14   ` Craig Burley
1998-12-15  9:29 ` Joe Buck
1998-12-15 10:14   ` Jeffrey A Law
1998-12-16  8:32     ` Sylvain Pion
1998-12-16  9:20       ` Craig Burley
1998-12-15 12:10 Geert Bosch
1998-12-15 13:09 ` Jeffrey A Law
1998-12-15 12:24 Toon Moene
1998-12-15 12:55 ` Joe Buck
1998-12-15 15:05 ` Edward Jason Riedy
1998-12-16 10:05 ` Craig Burley
1998-12-16 13:52 Toon Moene
1998-12-17 10:06 ` Craig Burley
1998-12-17 12:16   ` Harvey J. Stein
1998-12-19  0:29     ` Craig Burley
1998-12-17 11:20 ` Dave Love
1998-12-17 11:27 Brad Lucier
1998-12-17 14:51 ` Marc Lehmann
1998-12-19  0:17   ` Craig Burley
1998-12-19  6:42     ` Emil Hallin
1998-12-19 14:26       ` Dave Love
1998-12-17 14:37 tprince
1998-12-17 15:15 ` Stephen L Moshier
1998-12-17 14:38 Toon Moene
1998-12-17 15:30 ` Harvey J. Stein
1998-12-18  1:54   ` Toon Moene
1998-12-18  3:05     ` Harvey J. Stein
1998-12-18  9:01       ` Toon Moene
1998-12-18 15:59       ` Richard Henderson
1998-12-18 13:26   ` Marc Lehmann
1998-12-18 12:50 ` Dave Love

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=199812150654.BAA01399@melange.gnu.org \
    --to=burley@gnu.org \
    --cc=jbuck@Synopsys.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).