caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@inria.fr
Subject: Compiling to OCaml bytecode
Date: Fri, 9 Sep 2005 06:22:57 +0100	[thread overview]
Message-ID: <200509090622.58156.jon@ffconsultancy.com> (raw)


I am interested in improving the performance of a simple term-level 
interpreter. As OCaml's bytecode is so fast, I'd like to replace the 
interpreter with a JIT compiler that compiles to OCaml bytecode and then uses 
OCaml's bytecode interpreter to execute the generated code efficiently and 
handle the results.

Does the OCaml distribution expose everything needed to do this? I assume the 
Dynlink module is where I should be looking. I've never used it before but it 
looks as though it only loads from file (the "loadfile" function), so I'd 
have to compile to a .cmo file and load that. What is the easiest way to 
recover the result? If the necessary functionality is not already exposed, 
could it and/or what are the odds that it will be added?

Also, is a bytecode-compiled JIT bytecode compiler likely to outperform a 
native-code-compiled term-level interpreter? I assume the JIT compiler would 
itself need to be compiled to bytecode in order to provide the bytecode 
interpreter for the generated code.

-- 
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
Objective CAML for Scientists
http://www.ffconsultancy.com/products/ocaml_for_scientists


             reply	other threads:[~2005-09-09 12:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-09  5:22 Jon Harrop [this message]
2005-09-09 15:01 ` [Caml-list] " Paul Snively
2005-09-13  0:48   ` Jon Harrop
2005-09-13  6:19     ` Mackenzie Straight
2005-09-13  6:54       ` Jon Harrop
2005-09-13  7:17         ` skaller

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=200509090622.58156.jon@ffconsultancy.com \
    --to=jon@ffconsultancy.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;
as well as URLs for NNTP newsgroup(s).