From: Basile Starynkevitch <basile.starynkevitch@inria.fr>
To: caml-list@inria.fr
Subject: [Caml-list] [ANN] ocamljitrun initial release
Date: Mon, 19 Apr 2004 17:21:08 +0200 [thread overview]
Message-ID: <20040419152108.GA11095@bourg.inria.fr> (raw)
Dear All,
I coded and released ocamljitrun, a just in time translator of Ocaml
bytecode into machine code (on x86, and perhaps sparcv9 & PowerPC in
32 bits mode).
You need the latest Ocaml from CVS (ocaml 3.07 won't work).
You need the latest GNU lightning (from its CVS).
You can get it from the bazar-ocaml directory under CVS. In a couple
of hours, you should be able to get it there or at:
http://camlcvs.inria.fr/cgi-bin/cvsweb.cgi/bazar-ocaml/ocamljitrun/
In particular, read the README file there.
(you need jitinterp.c cvs id $Id: jitinterp.c,v 1.6 2004/04/19
14:55:01 starynke Exp $)
It runs ocamlc & ocaml apparently ok, and many other tests. I feel it
is mature enough to be tried by others on x86 platform.
I didn't tested it on Sparcv9 or PowerPC (in 32 bits mode only), but
it might run on these, since GNU Lightning is portable on
x86+Sparc+PPC (in 32 bits mode).
Ocamlrunjit won't run on an AMD64 (i.e. an Opteron) in 64 bits mode.
It should be the case that ocamljitrun may be a plug-in replacement of
ocamlrun
Regards.
--
Basile STARYNKEVITCH -- basile dot starynkevitch at inria dot fr
Project cristal.inria.fr - INRIA Rocquencourt
http://cristal.inria.fr/~starynke --- all opinions are only mine
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
reply other threads:[~2004-04-19 15:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040419152108.GA11095@bourg.inria.fr \
--to=basile.starynkevitch@inria.fr \
--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;
as well as URLs for NNTP newsgroup(s).