public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Geert Bosch <bosch@gnat.com>
To: kenner@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: ada/8606: GNAT floating point optimization bug
Date: Tue, 13 May 2003 17:56:00 -0000	[thread overview]
Message-ID: <20030513175601.21792.qmail@sources.redhat.com> (raw)

The following reply was made to PR ada/8606; it has been noted by GNATS.

From: Geert Bosch <bosch@gnat.com>
To: gcc-prs@gcc.gnu.org, 166255@bugs.debian.org,
	kalmquist1@hotmail.com, kenner@gcc.gnu.org, gcc-bugs@gcc.gnu.org,
	gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: ada/8606: GNAT floating point optimization bug
Date: Tue, 13 May 2003 13:46:51 -0400

 Indeed the issue here is the standard one of double rounding for
 64-bit floating point types. There is nothing Ada-specific about
 this and these problems are identical in C. The -ffloat-store
 option may improve repeatability, but has two undesired effects:
 it degrades performance and it always causes double rounding,
 which can degrade accuracy.
 
 For numerical code that requires exact rounding, only use 32-bit
 or 80-bit floating point types. When you need an expression to
 be computed to exactly 32 bits without any excess precision,
 store it to a volatile variable.
 
 If you really need 64-bit types with exact rounding, you'll have
 to set the rounding mode accordingly, but this will need changes
 in the Ada run time to prevent it from using 80-bit types.
 
    -Geert
 


             reply	other threads:[~2003-05-13 17:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-13 17:56 Geert Bosch [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-13  6:10 ebotcazou
2002-11-22  8:19 Matthias Klose

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=20030513175601.21792.qmail@sources.redhat.com \
    --to=bosch@gnat.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=kenner@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).