From: Paul Snively <psnively@mac.com>
To: Jon Harrop <jon@ffconsultancy.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Compiling to OCaml bytecode
Date: Fri, 9 Sep 2005 08:01:01 -0700 [thread overview]
Message-ID: <626610B4-6781-4FE9-B1A9-A8B37CB5391A@mac.com> (raw)
In-Reply-To: <200509090622.58156.jon@ffconsultancy.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Jon!
First: I love the book. :-)
On Sep 8, 2005, at 10:22 PM, Jon Harrop wrote:
>
> 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.
>
Sounds like <http://oops.tercom.ru/dml> to me, or maybe even <http://
www.metaocaml.org>.
> Does the OCaml distribution expose everything needed to do this?
No.
> 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?
>
I really do think either Dynamic Caml or MetaOCaml will be what you
want.
> 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.
>
"What happens when you try it?" ;-)
> --
> Dr Jon D Harrop, Flying Frog Consultancy Ltd.
> Objective CAML for Scientists
> http://www.ffconsultancy.com/products/ocaml_for_scientists
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
Best regards,
Paul
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
iEYEARECAAYFAkMho78ACgkQO3fYpochAqIdUACgxu7XGJfX8IkS32rSc1FlUPQQ
NacAn1D9+RGTJbfwxT/J2Fh8h51/YOw3
=3VZS
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-09-09 15:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 5:22 Jon Harrop
2005-09-09 15:01 ` Paul Snively [this message]
2005-09-13 0:48 ` [Caml-list] " 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=626610B4-6781-4FE9-B1A9-A8B37CB5391A@mac.com \
--to=psnively@mac.com \
--cc=caml-list@inria.fr \
--cc=jon@ffconsultancy.com \
/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).