From: "Soegtrop, Michael" <michael.soegtrop@intel.com>
To: Peter Thiemann <thiemann@informatik.uni-freiburg.de>
Cc: "Daniel Bünzli" <daniel.buenzli@erratique.ch>,
"Viet Le" <vietlq85@gmail.com>,
"caml-list@inria.fr" <caml-list@inria.fr>
Subject: RE: [Caml-list] Float precision in OCaml
Date: Tue, 1 Aug 2017 17:12:49 +0000 [thread overview]
Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A175B282ACD@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <797F4C7C-A647-424D-8F1B-120B93A723F5@informatik.uni-freiburg.de>
Dear Peter,
> https://cseweb.ucsd.edu/~lerner/papers/fp-printing-popl16.pdf
A very interesting paper, but it handles only the print direction, not the scan direction and not the problem of:
forall (x : double): scan(print(x)) = x
Best regards,
Michael
> -----Original Message-----
> From: Peter Thiemann [mailto:thiemann@informatik.uni-freiburg.de]
> Sent: Tuesday, August 1, 2017 5:49 PM
> To: Soegtrop, Michael <michael.soegtrop@intel.com>
> Cc: Peter Thiemann <thiemann@informatik.uni-freiburg.de>; Daniel Bünzli
> <daniel.buenzli@erratique.ch>; Viet Le <vietlq85@gmail.com>; caml-
> list@inria.fr
> Subject: Re: [Caml-list] Float precision in OCaml
>
> BTW, there is some literature on this topic, the most recent of which is the
> paper “Printing Floating Point Numbers - A faster, always correct method”
> https://cseweb.ucsd.edu/~lerner/papers/fp-printing-popl16.pdf
>
> It cites all the previous efforts starting with Knuth’s TACP Vol II, seminumerical
> algorithms.
>
> -Peter
>
> > On 1. Aug 2017, at 15:57, Soegtrop, Michael <michael.soegtrop@intel.com>
> wrote:
> >
> > Said that, one can define a mapping from floating point numbers to usual
> decimal string representations and back such that each floating point number
> results in a unique string. It is just quite tricky to get it right without extended
> precision arithmetic, though.
> >
> > As far as I know the Lisp standard requires that certain floating point formats
> have this property (I need to check). One might be able to learn from them how
> to do this properly.
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2017-08-01 17:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 10:47 Viet Le
2017-08-01 11:18 ` Nicolás Ojeda Bär
2017-08-01 11:25 ` Frédéric Bour
2017-08-01 11:45 ` Viet Le
2017-08-01 11:40 ` François Bobot
2017-08-01 11:42 ` Viet Le
2017-08-01 11:48 ` François Bobot
2017-08-01 12:12 ` Daniel Bünzli
2017-08-01 12:56 ` Viet Le
[not found] ` <etPan.59807b8a.db32dee.123@AirmailxGenerated.am>
2017-08-01 13:17 ` Daniel Bünzli
2017-08-01 13:57 ` Soegtrop, Michael
2017-08-01 14:07 ` Soegtrop, Michael
2017-08-01 15:48 ` Peter Thiemann
2017-08-01 17:12 ` Soegtrop, Michael [this message]
2017-08-02 7:41 ` Peter Thiemann
[not found] ` <etPan.5980c173.1234cb4.123@AirmailxGenerated.am>
2017-08-01 18:05 ` Daniel Bünzli
2017-08-02 5:46 ` Viet Le
2017-08-02 8:22 ` Soegtrop, Michael
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=0F7D3B1B3C4B894D824F5B822E3E5A175B282ACD@IRSMSX102.ger.corp.intel.com \
--to=michael.soegtrop@intel.com \
--cc=caml-list@inria.fr \
--cc=daniel.buenzli@erratique.ch \
--cc=thiemann@informatik.uni-freiburg.de \
--cc=vietlq85@gmail.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