caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Andreas Rossberg <rossberg@mpi-sws.org>
To: Xavier Leroy <Xavier.Leroy@inria.fr>
Cc: Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] NaN reresentations
Date: Wed, 2 Sep 2015 22:56:17 +0200	[thread overview]
Message-ID: <05537591-83A6-4D2E-B8FE-915379FCB12C@mpi-sws.org> (raw)
In-Reply-To: <CAH=h3gGAuCFfP0ZmD02ZiJknb6ETT=Hv2Fu09oWAJpiWe2n5OQ@mail.gmail.com>


On Sep 2, 2015, at 21:14 , Xavier Leroy <Xavier.Leroy@inria.fr> wrote:

> 2015-09-02 10:56 GMT-07:00 Andreas Rossberg <rossberg@mpi-sws.org>:
> > Does the Ocaml implementation make guarantees about the stable representation of floats? In particular, if I use Int64.float_of_bits to create a particular NaN representation, am I guaranteed that its bit pattern is maintained no matter where the value is stored or passed?
> 
> It depends on the underlying hardware.  For instance, with x86-32 bits, some FP moves go through the x87 FP stack, undergoing a double -> extended -> double conversion.   These conversions turn signaling NaNs into quiet NaNs, and I'm not sure they preserve the other bits of the NaN payload.
> 
> On other platforms, esp. x86-64 bits, I'm pretty confident that NaN bits are preserved by copying and parameter passing.

I see. Okay, in that case it seems safer not to rely on it, for the sake of portability.

> > We are currently in the process of implementing a reference interpreter for a little low-level language, and that tries to be as accurate as possible about float representations.
> 
> One possibility would be to represent your floats as int64 values (= their bit-level representation), and convert only when you operate over them, e.g.
> 
> let fp_add x y = Int64.bits_of_float (Int64.float_of_bits x +. Int64.float_of_bits y)

Right, that is the approach we are currently discussing. but I was wondering whether it is necessary.

Thanks!

/Andreas


      reply	other threads:[~2015-09-02 20:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-02 17:56 Andreas Rossberg
2015-09-02 18:35 ` Daniel Bünzli
2015-09-02 19:14 ` Xavier Leroy
2015-09-02 20:56   ` Andreas Rossberg [this message]

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=05537591-83A6-4D2E-B8FE-915379FCB12C@mpi-sws.org \
    --to=rossberg@mpi-sws.org \
    --cc=Xavier.Leroy@inria.fr \
    --cc=caml-list@inria.fr \
    /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 NNTP newsgroup(s).