From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <weis@pauillac.inria.fr>
Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39])
	by yquem.inria.fr (Postfix) with ESMTP id 10B1DBCAC
	for <caml-list@yquem.inria.fr>; Tue, 24 May 2005 19:38:29 +0200 (CEST)
Received: from pauillac.inria.fr (pauillac.inria.fr [128.93.11.35])
	by concorde.inria.fr (8.13.0/8.13.0) with ESMTP id j4OHcSgG025637
	for <caml-list@yquem.inria.fr>; Tue, 24 May 2005 19:38:28 +0200
Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id TAA09337 for <caml-list@pauillac.inria.fr>; Tue, 24 May 2005 19:38:28 +0200 (MET DST)
Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.203])
	by nez-perce.inria.fr (8.13.0/8.13.0) with ESMTP id j4OHcR4m004009
	for <caml-list@inria.fr>; Tue, 24 May 2005 19:38:27 +0200
Received: by zproxy.gmail.com with SMTP id 8so1987989nzo
        for <caml-list@inria.fr>; Tue, 24 May 2005 10:38:26 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=YzH6J2vo80nZpgC9l/LZSrl+NJFhJCJUOJYqrsziefec5zRd7H+I7R30FQCMVc/iTHphYETuTjDcVLDxbs0CnwICgGNnZ1sIMpFd+oC3lkX6PQ6oKBMwBY09EusxQpQ/NJgfP7nsXMN0hjZ97Aw4vD7muF16/reqKGYSICMAA+Y=
Received: by 10.36.19.12 with SMTP id 12mr1967856nzs;
        Tue, 24 May 2005 10:38:26 -0700 (PDT)
Received: by 10.36.55.18 with HTTP; Tue, 24 May 2005 10:38:26 -0700 (PDT)
Message-ID: <6b8a91420505241038a10b812@mail.gmail.com>
Date: Tue, 24 May 2005 19:38:26 +0200
From: Remi Vanicat <remi.vanicat@gmail.com>
Reply-To: Remi Vanicat <remi.vanicat@gmail.com>
To: Christopher Alexander Stein <stein@eecs.harvard.edu>
Subject: Re: [Caml-list] JIT ?
Cc: caml-list@inria.fr
In-Reply-To: <20050524131153.P45033@bowser.eecs.harvard.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <20050524141102.GA32331@furbychan.cocan.org>
	 <20050524131153.P45033@bowser.eecs.harvard.edu>
X-Miltered: at concorde with ID 42936694.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)!
X-Miltered: at nez-perce with ID 42936693.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)!
X-Spam: no; 0.00; caml-list:01 ocamlrun:01 bytecode:01 compilation:01 ocamlopt:01 ocamlc:01 ocamlrun:01 ocaml:01 ocamlopt:01 cristal:01 eecs:01 remi:01 remi:01 vanicat:01 vanicat:01 
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on yquem.inria.fr
X-Spam-Status: No, score=0.0 required=5.0 tests=RCVD_BY_IP autolearn=disabled 
	version=3.0.2
X-Spam-Level: 

2005/5/24, Christopher Alexander Stein <stein@eecs.harvard.edu>:
>=20
> Can the ocamlrun bytecode interpreter do just-in-time compilation
> or is ocamlopt the way to go for performance instead of ocamlc?

Ocamlrun is a pure interpreter (but a relatively fast one). There is
(was ?) a JIT interpreter for ocaml (at least in my memory i have
heard something about it) but the common way to go for performance is
indeed ocamlopt.

See http://cristal.inria.fr/~starynke/ocamljit.html for ocamljitrun.