From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] HLVM?
Date: Sat, 26 Sep 2009 18:26:12 +0100 [thread overview]
Message-ID: <200909261826.12639.jon@ffconsultancy.com> (raw)
In-Reply-To: <AC146F3A-0AC2-445B-A635-C2F22411AA8B@refined-audiometrics.com>
On Saturday 26 September 2009 17:33:41 David McClain wrote:
> Hello Jon,
>
> I searched around for information on HLVM, and what, in particular,
> makes it so well suited for scientific computing. I also have a long-
> standing interest in scientific computing and OCaml, dating back to
> 1999 when I created my NML system.
>
> However, wherever I found a reference to the HLVM architecture, all I
> really found was a short blurb telling me to subscribe to your OCaml
> Journal.
The motivation behind the HLVM project is described here:
http://www.ffconsultancy.com/ocaml/hlvm/
> Can you provide some gratis information about what makes HLVM so well
> suited to scientific computing?
HLVM is specifically designed with scientific computing in mind and, in
particular, aims to provide a performance profile better suited to scientific
computing. Some sacrifices have been made (e.g. polymorphic recursion) but
the preliminary results are encouraging. For example, HLVM already thrashes
OCaml on most numerical benchmarks:
http://flyingfrogblog.blogspot.com/2009/03/performance-ocaml-vs-hlvm-beta-04.html
HLVM also provides native code performance directly from the REPL
out-of-the-box and offers some useful features that OCaml lacks such as
generic printing. Other numerical types (byte, sbyte, int8, uint8, int16,
uint16, int32, uint32, int64, uint64, float32, complex32, complex64) are also
easy to add and will be vastly more efficient than OCaml's.
However, HLVM is currently missing some core features. Most notably,
polymorphism and a parallel GC. I intend to implement polymorphism by adding
a monomorphization stage before JIT compilation and implement a parallel GC
along the lines of the oc4mc project's.
In essence, improvements in code generation and run-time data representation
will make HLVM several times faster than OCaml for technical computing and
improvements in parallelism will make it several times faster again. So I
expect to get at least an order of magnitude performance improvement over
OCaml in the end.
> Something that might prompt one to actually subscribe to your journal?
The OCaml Journal articles about HLVM describe the decisions that underpin
HLVM's current design and the details of how those were implemented in OCaml
using LLVM. In particular, the current OCaml Journal articles do *not*
describe how HLVM can be used for scientific computing because it is still an
experimental project and is likely to undergo major revisions (when I get to
work on it again!). In other words, the articles are aimed at language
implementors and not end users.
--
Dr Jon Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/?e
next prev parent reply other threads:[~2009-09-26 17:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-26 16:33 HLVM? David McClain
2009-09-26 17:26 ` Jon Harrop [this message]
2009-09-26 20:23 ` HLVM? Sylvain Le Gall
2009-09-26 21:59 ` [Caml-list] HLVM? Jon Harrop
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=200909261826.12639.jon@ffconsultancy.com \
--to=jon@ffconsultancy.com \
--cc=caml-list@yquem.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