caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Erick Tryzelaar <erickt@dslextreme.com>
To: skaller <skaller@users.sourceforge.net>
Cc: Taras Glek <taras.judge@shaw.ca>, Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] JIT VM in OCaml: Impossible?
Date: Thu, 16 Aug 2007 20:09:41 -0700	[thread overview]
Message-ID: <46C51175.6000208@dslextreme.com> (raw)
In-Reply-To: <1187319000.29691.24.camel@rosella.wigram>

skaller wrote:
> Don't forget: a program has to be compiled one way or the other.
> Even Python is compiled to bytecode.  The tool above (Felix)
> is better than a JIT because it does whole program optimisation,
> generates machine binaries.
>
> So I don't buy 'slow' as an argument: the technique is much
> FASTER than any JIT system in all aspects, in fact it IS
> a JIT compiler -- it just compiles the whole program all the
> way from source with disk based caching which persists over
> invocations.
>   

For loose definitions of JIT :) It doesn't do runtime optimization of 
the code, of course.

And to be fair, since whole program optimization needs to start roughly 
from scratch every time, you can have some ugly compile times.


  reply	other threads:[~2007-08-17  3:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-16 14:10 Joel Reymont
2007-08-16 14:37 ` Sylvain Le Gall
2007-08-16 15:32   ` [Caml-list] " Oliver Bandel
2007-08-16 15:56     ` Joel Reymont
2007-08-16 16:15   ` Jon Harrop
2007-08-16 15:11 ` [Caml-list] " Oliver Bandel
2007-08-16 16:24 ` Gordon Henriksen
2007-08-16 17:37   ` skaller
2007-08-16 18:05     ` Taras Glek
2007-08-17  2:50       ` skaller
2007-08-17  3:09         ` Erick Tryzelaar [this message]
2007-08-17  5:42           ` skaller
2007-08-17  7:52             ` Joel Reymont
2007-08-17  8:36               ` Jon Harrop
2007-08-17  9:20                 ` Joel Reymont
2007-08-17  8:39         ` Jon Harrop
2007-08-16 18:49   ` 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=46C51175.6000208@dslextreme.com \
    --to=erickt@dslextreme.com \
    --cc=caml-list@inria.fr \
    --cc=skaller@users.sourceforge.net \
    --cc=taras.judge@shaw.ca \
    /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).