Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Evgeny Roubinchtein <zhenya1007@gmail.com>
To: "Андрей Бергман" <vkni@yandex.ru>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] How floats are handled in bytecode interpreter? And other questions.
Date: Sun, 22 Jan 2017 13:23:10 -0500	[thread overview]
Message-ID: <CAGYXaSZ13JQMHf+OYBxH_ySz2ocz9FLMmqhc-TVtVoyCy2okVg@mail.gmail.com> (raw)
In-Reply-To: <4653711485104160@web7j.yandex.ru>

[-- Attachment #1: Type: text/plain, Size: 986 bytes --]

> 1. Is "Caml Virtual Machine — Instruction set, v1.4" by Xavier Clerc -
> http://cadmium.x9c.fr/distrib/caml-instructions.pdf up to date? He
> describes virtual machine of 3.12, while current version is 4.04. According
> to GitHub logs there were some changes in the VM. Did they touch
> instruction set?
>

The definitive list of byte codes understood by the "vanila" CAML virtual
machine is in byterun/caml/instruct.h, so one could, in theory compare the
two lists side-by-side, if that is what you are asking.


> 2. How are handled operations on floats in bytecode? In MosML, which uses
> bytecode machine of CamlLight, they added set of instructions FLOATOFINT,
> SMLNEGFLOAT, SMLADDFLOAT, SMLSUBFLOAT, SMLMULFLOAT, SMLDIVFLOAT, INTOFFLOAT
> and etc.
>

They are not handled in the byte code.   They are handled by C code in the
run time.  Look around line 340 of bytecomp/bytegen.ml on Github to see how
those calls are translated.

-- 
Best,
Женя

[-- Attachment #2: Type: text/html, Size: 1630 bytes --]

  reply	other threads:[~2017-01-22 18:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-22 16:56 Андрей Бергман
2017-01-22 18:23 ` Evgeny Roubinchtein [this message]
     [not found]   ` <4669031485116895@web19m.yandex.ru>
2017-01-22 20:43     ` Evgeny Roubinchtein

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=CAGYXaSZ13JQMHf+OYBxH_ySz2ocz9FLMmqhc-TVtVoyCy2okVg@mail.gmail.com \
    --to=zhenya1007@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=vkni@yandex.ru \
    /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