From: "Андрей Бергман" <vkni@yandex.ru>
To: caml-list@inria.fr
Subject: [Caml-list] How floats are handled in bytecode interpreter? And other questions.
Date: Sun, 22 Jan 2017 19:56:00 +0300 [thread overview]
Message-ID: <4653711485104160@web7j.yandex.ru> (raw)
Hello!
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?
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.
Thanks,
Andrey.
P.S.
For Hendrik Boom - a bit altered very old version of Caml Virtual Machine is used in MoscowML - implementation of SML language, based on CamlLight.
next reply other threads:[~2017-01-22 16:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-22 16:56 Андрей Бергман [this message]
2017-01-22 18:23 ` Evgeny Roubinchtein
[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=4653711485104160@web7j.yandex.ru \
--to=vkni@yandex.ru \
--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