From: Sven LUTHER <luther@dpt-info.u-strasbg.fr>
To: Xavier Leroy <Xavier.Leroy@inria.fr>
Cc: dsl@tepkom.ru, caml-list@inria.fr
Subject: Re: Byte-code specs.
Date: Fri, 14 Jan 2000 09:42:58 +0100 [thread overview]
Message-ID: <20000114094258.A11868@dpt-info.u-strasbg.fr> (raw)
In-Reply-To: <20000113104727.17845@pauillac.inria.fr>; from Xavier.Leroy@inria.fr on Thu, Jan 13, 2000 at 10:47:27AM +0100
On Thu, Jan 13, 2000 at 10:47:27AM +0100, Xavier Leroy wrote:
> > Are there any specs for CAML bytecode?
>
> Not much. There is an old technical report (1990!) that documents
> the Caml Light virtual machine in some details:
>
> http://pauillac.inria.fr/~xleroy/publi/ZINC.ps.gz
>
> The Objective Caml virtual machine is a second iteration of the Caml
> Light VM, with some complications removed (e.g. one stack instead of
> two). However, there is no paper spec for it.
And is there any document that gives some description of the execution costs
of different ocaml constructs ?
Friendly,
Sven LUTHER
next prev parent reply other threads:[~2000-01-14 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-04 13:36 Dmitri Lomov
2000-01-13 9:47 ` Xavier Leroy
2000-01-14 8:42 ` Sven LUTHER [this message]
2000-01-14 19:16 ` Pierre Weis
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=20000114094258.A11868@dpt-info.u-strasbg.fr \
--to=luther@dpt-info.u-strasbg.fr \
--cc=Xavier.Leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=dsl@tepkom.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