From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] The Bytecode Interpreter...
Date: Sat, 22 Oct 2005 01:32:42 +0100 [thread overview]
Message-ID: <200510220132.43276.jon@ffconsultancy.com> (raw)
In-Reply-To: <ad8cfe7e0510211524n7e9e944eleaf4d2be99e5a56c@mail.gmail.com>
On Friday 21 October 2005 23:24, Jonathan Roewen wrote:
> I've noted on the computer language shootout that ocaml bytecode is
> slow compared to Java. I'm curious, are there any plans to optimise
> the shit out of the bytecode interpreter? I know it has been a goal to
> not be much more than 1.3x slower than C -- but this only covers
> ocamlopt/native code. Don't you think bytecode should have some
> endeavour to match or better some other language too (Java seems best
> case to me in this scenario).
You may be interested in Basile's ocamljit.
> About the only thing the shootout proves is that ocaml bytecode has
> very good memory use compared to Java.
and brevity.
--
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
Objective CAML for Scientists
http://www.ffconsultancy.com/products/ocaml_for_scientists
next prev parent reply other threads:[~2005-10-22 0:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-21 10:01 Jonathan Roewen
2005-10-21 11:27 ` David MENTRE
2005-10-21 22:24 ` Jonathan Roewen
2005-10-21 23:49 ` Oliver Bandel
2005-10-22 21:33 ` Jonathan Roewen
2005-10-22 0:32 ` Jon Harrop [this message]
2005-10-22 0:39 ` Jacques Garrigue
2005-10-23 1:03 ` Jonathan Roewen
2005-10-23 10:21 ` Gerd Stolpmann
2005-10-24 5:38 ` Jonathan Roewen
2005-10-24 6:13 ` Jacques Garrigue
2005-10-24 6:48 ` Jonathan Roewen
2005-10-22 0:39 ` Jonathan Roewen
2005-10-26 0:33 ` Jonathan Roewen
2005-10-26 9:56 ` Jonathan Roewen
2005-10-26 10:20 ` Jonathan Roewen
2005-10-27 14:12 ` Damien Doligez
2005-10-28 21:41 ` Jonathan Roewen
2005-10-29 11:29 ` Gerd Stolpmann
2005-10-29 15:22 ` skaller
2005-10-30 0:41 ` Jonathan Roewen
2005-11-10 10:26 ` Damien Doligez
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=200510220132.43276.jon@ffconsultancy.com \
--to=jon@ffconsultancy.com \
--cc=caml-list@yquem.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).