public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: Robert Dewar <dewar@gnat.com>
Cc: aph@redhat.com, gcc@gcc.gnu.org
Subject: Re: real.c implementation
Date: Tue, 22 Oct 2002 11:56:00 -0000	[thread overview]
Message-ID: <20021022180028.GH16329@redhat.com> (raw)
In-Reply-To: <20021022105831.B7E89F2D65@nile.gnat.com>

On Tue, Oct 22, 2002 at 06:58:31AM -0400, Robert Dewar wrote:
> Well if you define "The Right Thing" to be what Java needs, fine, but then
> this would be wrong for Ada, since Ada requires that float literals be
> rounded away from infinity (0.5 always rounds up).

Easy enough to handle with an argument to the real_from_string
function.

> What about the handling of denormals?

What about them?  They should work as advertized.

The main reason for the recent real.c rewrite was to fix this
very issue for double-extended and quad ieee formats, so if
you remember problems with denormals in the past, they are in
theory fixed now.  You should definitely re-test.

> Also, the issue of what should be done on non-IEEE machines is not clear.
> For example, on the Alpha, you probably do not want to generate denormal
> literals by default.

We do now.  We did have code in the compiler to prevent this
(unconditionally, mind!) until recently; I considered this a
bug and removed it.  If you don't want to trap on denormals,
then don't write denormal constants.  Simple as that.

As for truely non-ieee machines, well, we do the best we can.



r~

  reply	other threads:[~2002-10-22 18:00 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-22  9:43 Robert Dewar
2002-10-22 11:56 ` Richard Henderson [this message]
     [not found] <200210281429.g9SETTeS020750@mururoa.inria.fr>
2002-10-28 11:38 ` Brigitte Verdonk
  -- strict thread matches above, loose matches on Subject: below --
2002-10-28  8:34 Stephen L Moshier
2002-10-28  4:43 Stephen L Moshier
2002-10-26  8:43 Robert Dewar
2002-10-26  8:42 Stephen L Moshier
2002-10-26  9:05 ` Brad Lucier
2002-10-26  4:10 Stephen L Moshier
2002-10-23  0:33 Robert Dewar
2002-10-22 23:58 Robert Dewar
2002-10-23  0:03 ` Eric Christopher
2002-10-22 13:22 Robert Dewar
2002-10-22 12:15 Robert Dewar
2002-10-22 12:32 ` Richard Henderson
2002-10-22 11:04 Robert Dewar
2002-10-22  9:45 Robert Dewar
2002-10-22 14:35 ` Neil Booth
2002-10-22  9:05 Robert Dewar
2002-10-22  9:19 ` Andrew Haley
2002-10-22  8:49 Robert Dewar
2002-10-22  8:50 ` Andrew Haley
2002-10-22 11:35 ` Zack Weinberg
2002-10-22 11:49 ` Richard Henderson
2002-10-22 12:34   ` Andreas Schwab
2002-10-22 17:26     ` Richard Henderson
2002-10-23  9:10       ` Andreas Schwab
2002-10-22  7:23 Robert Dewar
2002-10-22  7:41 ` Andrew Haley
2002-10-22  3:14 Robert Dewar
2002-10-22  3:36 ` Richard Henderson
2002-10-22  7:23   ` Andrew Haley
2002-10-22 11:00     ` Matt Thomas
2002-10-22 11:06       ` Andrew Haley
2002-10-22 11:11         ` Andrew Haley
2002-10-19  2:16 Roger Sayle
2002-10-18 17:02 Brad Lucier
2002-10-18 20:28 ` Richard Henderson
2002-10-17 14:16 Brad Lucier
2002-10-18 15:21 ` Richard Henderson
2002-10-19  1:07   ` Brad Lucier
2002-10-21  7:37   ` Brad Lucier
2002-10-21 17:34     ` Richard Henderson
2002-10-22  1:53       ` Fergus Henderson
2002-10-21 20:41     ` Richard Henderson

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=20021022180028.GH16329@redhat.com \
    --to=rth@redhat.com \
    --cc=aph@redhat.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).