From: David McClain <dbm@refined-audiometrics.com>
To: caml-list@inria.fr
Subject: HLVM
Date: Sat, 26 Sep 2009 10:21:21 -0700 [thread overview]
Message-ID: <CFBC5B10-F95A-4B9F-823D-BB5C5C844156@refined-audiometrics.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 548 bytes --]
Yes, I saw those references already. Still not enough information...
What, in particular, sets HLVM apart. Surely not just the native
machine types?
Are you handling array references in some unusually efficient manner?
Are you avoiding unnecessary copy-on-writes of large arrays by some
form of whole-program analysis? I still don't have a handle on HLVM...
>
> http://www.ffconsultancy.com/ocaml/hlvm/
> http://flyingfrogblog.blogspot.com/2009/03/performance-ocaml-vs-hlvm-beta-04.html
Dr. David McClain
dbm@refined-audiometrics.com
[-- Attachment #2: Type: text/html, Size: 1790 bytes --]
next reply other threads:[~2009-09-26 17:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-26 17:21 David McClain [this message]
2009-09-26 21:41 ` [Caml-list] HLVM Jon Harrop
2009-09-27 16:57 HLVM David McClain
2009-09-27 18:06 HLVM David McClain
2009-09-27 22:09 HLVM David McClain
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=CFBC5B10-F95A-4B9F-823D-BB5C5C844156@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).