From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] llvm?
Date: Thu, 11 Feb 2010 01:33:33 +0000 [thread overview]
Message-ID: <201002110133.33731.jon@ffconsultancy.com> (raw)
In-Reply-To: <91a2ba3e1002101451g7c81e938waf5e2612bf450f32@mail.gmail.com>
On Wednesday 10 February 2010 22:51:33 Raoul Duke wrote:
> hi,
>
> any news about / anybody working on ocaml-on-llvm?
I don't believe anyone is working on porting OCaml to LLVM.
The nearest work is probably my own HLVM project which reached a major
milestone recently and is now capable of high-performance parallel
programming:
http://flyingfrogblog.blogspot.com/2010/01/naive-parallelism-with-hlvm.html
From the point of view of an OCaml programmer, HLVM is a DSL that drops
various features from OCaml (e.g. polymorphic recursion) in order to provide
easily-obtained, predictable and high performance.
--
Dr Jon Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/?e
prev parent reply other threads:[~2010-02-11 0:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 22:51 llvm? Raoul Duke
2010-02-11 1:33 ` Jon Harrop [this message]
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=201002110133.33731.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