From: Jon Harrop <jonathandeanharrop@googlemail.com>
To: "'Eray Ozkural'" <examachine@gmail.com>,
"'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:37:05 +0100 [thread overview]
Message-ID: <006a01cb5515$c9c42420$5d4c6c60$@com> (raw)
In-Reply-To: <AANLkTikCVkjQ7n0MX2AkabggXCMEC5924Jooo3RJMsNA@mail.gmail.com>
> 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.
Would be interesting to try. I suspect the C compiler would then optimize
the sequences of operations on the data as well. For example, something like
vector addition.
> 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.
Can you elaborate?
Cheers,
Jon.
next prev parent reply other threads:[~2010-09-15 20:37 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
2010-09-15 20:37 ` Jon Harrop [this message]
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='006a01cb5515$c9c42420$5d4c6c60$@com' \
--to=jonathandeanharrop@googlemail.com \
--cc=basile@starynkevitch.net \
--cc=caml-list@yquem.inria.fr \
--cc=examachine@gmail.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).