Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: "Alexander Usov" <a.s.usov@gmail.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml with long double
Date: Mon, 6 Nov 2006 13:07:10 +0100	[thread overview]
Message-ID: <83a12d7e0611060407m3fe3be1fkdf4d36f7e018f833@mail.gmail.com> (raw)
In-Reply-To: <454F1A37.2000604@univ-savoie.fr>

On 11/6/06, Christophe Raffalli <christophe.raffalli@univ-savoie.fr> wrote:
>
> Hi,
>
> Has anyone tried to patch OCaml to use long double (128 bits on intel/gcc) instead of double (64
> bits on intel gcc) ?

In reality they are not 128 bits, but just 80 bits long. The rest is
just to improve memory alignment.

I am not very authoritative to talk about patching ocaml, but judging
from the amount
of internal optimizations for handling of unboxed floating-point
numbers, changing it will be quite difficult.

--
Best regards,
 Alexander.


      reply	other threads:[~2006-11-06 12:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-06 11:19 Christophe Raffalli
2006-11-06 12:07 ` Alexander Usov [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=83a12d7e0611060407m3fe3be1fkdf4d36f7e018f833@mail.gmail.com \
    --to=a.s.usov@gmail.com \
    --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