caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Eray Ozkural <examachine@gmail.com>
To: Jon Harrop <jonathandeanharrop@googlemail.com>
Cc: Basile Starynkevitch <basile@starynkevitch.net>,
	Vincent Gripon <vincent.gripon@telecom-bretagne.eu>,
	caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Compiling Ocaml sources to c sources
Date: Wed, 15 Sep 2010 21:17:14 +0300	[thread overview]
Message-ID: <AANLkTikCVkjQ7n0MX2AkabggXCMEC5924Jooo3RJMsNA@mail.gmail.com> (raw)
In-Reply-To: <004b01cb54fc$9c435020$d4c9f060$@com>

[-- Attachment #1: Type: text/plain, Size: 1234 bytes --]

On Wed, Sep 15, 2010 at 8:36 PM, Jon Harrop <
jonathandeanharrop@googlemail.com> wrote:

> >   * Hacking a C generator inside Ocaml is non-trivial, because of the
> >     garbage collector, currified function calls, and tail recursion
> >     etc.
>
> BTW, I was always surprised nobody had converted the bytecode interpreter
> into a via-C compiler by unwinding the C code the interpreter goes through
> to execute a specific OCaml bytecode program. You could even use this with
> something like Clang to get JIT compilation to native code. Not very
> efficient but surely much faster than interpreted bytecode...
>

Hmm, this would only optimize the bytecode fetch/decode step of the ocaml
execution cycle. I am not sure that it will result in much real-world
speedup.

In fact, that seems to be the main problem with many of these so-called JIT
interpreters, which in my opinion, do not seem to have learnt from the HAL
architectures of IBM OS's etc. Was probably also the problem with Transmeta;
cheap compilation entails cheap performance.

Best,

-- 
Eray Ozkural, PhD candidate.  Comp. Sci. Dept., Bilkent University, Ankara
http://groups.yahoo.com/group/ai-philosophy
http://myspace.com/arizanesil http://myspace.com/malfunct

[-- Attachment #2: Type: text/html, Size: 1781 bytes --]

  reply	other threads:[~2010-09-15 18:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-14 12:09 Vincent Gripon
2010-09-14 12:16 ` [Caml-list] Compiling Ocaml sources to c sources [NC] Rabih CHAAR
2010-09-14 12:35 ` [Caml-list] Compiling Ocaml sources to c sources David MENTRE
2010-09-15 13:18   ` Vincent Gripon
2010-09-15 19:59     ` Basile Starynkevitch
2010-09-15 22:16       ` Vincent Gripon
2010-09-14 12:43 ` Basile Starynkevitch
2010-09-15 12:59   ` Vincent Gripon
2010-09-15 17:36   ` Jon Harrop
2010-09-15 18:17     ` Eray Ozkural [this message]
2010-09-15 20:37       ` Jon Harrop
2010-09-16  0:38         ` Eray Ozkural
2010-09-16  9:05           ` Fabrice Le Fessant
2010-09-16 10:46             ` Eray Ozkural
2010-09-16 11:11               ` Fabrice Le Fessant
2010-09-14 12:47 ` Thomas Gazagnaire
2010-09-14 12:48   ` Grant Rettke
2010-09-15 13:04   ` Vincent Gripon
2010-09-15 19:57     ` Basile Starynkevitch

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=AANLkTikCVkjQ7n0MX2AkabggXCMEC5924Jooo3RJMsNA@mail.gmail.com \
    --to=examachine@gmail.com \
    --cc=basile@starynkevitch.net \
    --cc=caml-list@yquem.inria.fr \
    --cc=jonathandeanharrop@googlemail.com \
    --cc=vincent.gripon@telecom-bretagne.eu \
    /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).