From: David McClain <dbm@refined-audiometrics.com>
To: caml-list@inria.fr
Subject: JIT & HLVM, LLVM
Date: Sun, 27 Sep 2009 10:18:51 -0700 [thread overview]
Message-ID: <4E6F3027-5745-462D-AF10-30C868285D28@refined-audiometrics.com> (raw)
Ahh, I see from doing a bit more research that JIT does *not* run
particularly faster than statically compiled code. But rather, it runs
faster than interpreted byte-code.
I remember many years ago speaking with David Robson, over lunch,
about the upcoming changes in Smalltalk, using a form of JIT to
improve performance of their method dispatch, and attempting to gain
multiple inheritance in that manner for Smalltalk. But there, again,
it is a case of attempting to improve on an interpreted byte-code, and
not a case of improving over statically compiled native code.
But with so many talented bodies working on LLVM, perhaps, in time, a
way will be found to gain improvement over static native code.
Dr. David McClain
dbm@refined-audiometrics.com
next reply other threads:[~2009-09-27 17:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-27 17:18 David McClain [this message]
2009-09-27 17:22 ` [Caml-list] " Vincent Aravantinos
2009-09-27 17:35 ` Edgar Friendly
2009-09-27 18:51 ` Jon Harrop
2009-09-27 19:07 ` Edgar Friendly
2009-09-27 19:23 ` kcheung
2009-09-27 19:33 ` Jon Harrop
2009-09-27 21:10 ` Jon Harrop
2009-09-27 21:45 ` Vincent Aravantinos
2009-09-30 1:08 ` Mikkel Fahnøe Jørgensen
2009-09-30 11:57 ` Stéphane Glondu
2009-09-30 12:54 ` Mikkel Fahnøe Jørgensen
2009-09-30 13:42 ` Stéphane Glondu
2009-09-30 19:11 ` Mikkel Fahnøe Jørgensen
2009-09-30 15:22 ` Jon Harrop
2009-09-30 19:35 ` Mikkel Fahnøe Jørgensen
2009-09-28 12:25 ` Gerd Stolpmann
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=4E6F3027-5745-462D-AF10-30C868285D28@refined-audiometrics.com \
--to=dbm@refined-audiometrics.com \
--cc=caml-list@inria.fr \
/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).