caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Joel Reymont <joelr1@gmail.com>
To: Jon Harrop <jon@ffconsultancy.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] High-performance bytecode interpreter in OCaml
Date: Wed, 15 Aug 2007 14:20:34 +0100	[thread overview]
Message-ID: <EC4C88C0-681B-4691-B7A0-BDF52B78895D@gmail.com> (raw)
In-Reply-To: <200708151401.41091.jon@ffconsultancy.com>

I have an existing bytecode file that I need to execute. The bytecode  
is produced by some other compiler. Does this change anything?

I'm not sure if a term-level interpreter or rewriter applies in this  
scenario.

As for CPS, what I meant is implementing each bytecode instruction as  
a function that takes a continuation (next instruction?).

	Thanks, Joel

On Aug 15, 2007, at 2:01 PM, Jon Harrop wrote:

> The performance of interpreters is heavily dependent upon what  
> exactly you're
> evaluating (both language and program properties). If you start  
> with a naive
> term-level interpreter or rewriter then you can get an order of  
> magnitude in
> performance by optimizing the interpreter without leaving OCaml or  
> moving to
> (real) bytecode compilation.

--
http://wagerlabs.com






  reply	other threads:[~2007-08-15 13:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-15 11:49 Joel Reymont
2007-08-15 13:01 ` [Caml-list] " Jon Harrop
2007-08-15 13:20   ` Joel Reymont [this message]
2007-08-15 15:18     ` Jon Harrop
2007-08-15 23:26       ` Joel Reymont
2007-08-16  3:58         ` Jon Harrop
2007-08-15 23:31     ` Grant Olson
2007-08-16 15:55       ` Jon Harrop

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=EC4C88C0-681B-4691-B7A0-BDF52B78895D@gmail.com \
    --to=joelr1@gmail.com \
    --cc=caml-list@yquem.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).