From: Jon Harrop <jonathandeanharrop@googlemail.com>
To: "'Yoann Padioleau'" <padator@wanadoo.fr>,
"'bluestorm'" <bluestorm.dylc@gmail.com>
Cc: <caml-list@yquem.inria.fr>
Subject: RE: [Caml-list] OCamlJIT2 vs. OCamlJIT
Date: Tue, 30 Nov 2010 22:06:33 -0000 [thread overview]
Message-ID: <0a8b01cb90da$da5e6240$8f1b26c0$@com> (raw)
In-Reply-To: <B8C055A1-2A67-4C7E-BF67-4A639619C4EB@wanadoo.fr>
Yoann wrote:
> Yes, and it has to stop. I don't understand why there is so much hype
around LLVM. Why
> would you think something written in C++ would be far better than the
ocaml code we have
> in the ocamlopt compiler?
Because benchmarks like my HLVM ones have proven that LLVM can generate
*much* faster code than ocamlopt does.
For example, Fibonacci function over floats in HLVM with optimization passes
disabled and compilation time included in the measurement:
# let rec fib (x: float) : float =
if x < 1.5 then x else fib(x - 1.0) + fib(x - 2.0);;
# fib 40.0;;
- : `Float = 1.02334e+08
Live: 0
2.48074s total; 0s suspend; 0s mark; 0s sweep
And ocamlopt without compilation time:
$ cat >fib.ml
let rec fib x = if x < 1.5 then x else fib(x -. 1.0) +. fib(x -. 2.0);;
fib 40.0;;
$ ocamlopt fib.ml -o fib
$ time ./fib
real 0m7.811s
user 0m7.808s
sys 0m0.000s
Note that HLVM's *REPL* is over 3x faster than ocamlopt-compiled OCaml.
I have microbenchmarks where LLVM generates code over 10x faster than
ocamlopt (specifically, floating point code on x86) and larger numerical
programs that also wipe the floor with OCaml.
LLVM is also much better documented than ocamlopt's internals.
Cheers,
Jon.
next prev parent reply other threads:[~2010-11-30 22:06 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 8:36 Benedikt Meurer
2010-11-30 10:48 ` [Caml-list] " Török Edwin
2010-11-30 10:55 ` Benedikt Meurer
2010-11-30 17:01 ` bluestorm
2010-11-30 17:26 ` Török Edwin
2010-11-30 18:27 ` Basile Starynkevitch
2010-11-30 17:29 ` Benedikt Meurer
2010-11-30 17:32 ` Yoann Padioleau
2010-11-30 22:06 ` Jon Harrop [this message]
2010-11-30 22:48 ` Benedikt Meurer
2010-12-01 14:11 ` Jon Harrop
2010-12-01 15:00 ` Benedikt Meurer
2010-12-01 22:03 ` Jon Harrop
2010-12-02 1:17 ` Eray Ozkural
2010-12-03 10:03 ` ocamlopt LLVM support (Was: [Caml-list] OCamlJIT2 vs. OCamlJIT) Benedikt Meurer
2010-12-03 13:34 ` Till Varoquaux
2010-12-03 13:41 ` Eray Ozkural
2010-12-03 14:06 ` Török Edwin
2010-12-03 21:16 ` Jon Harrop
2010-12-05 16:44 ` Benedikt Meurer
2010-12-03 14:32 ` Philippe Strauss
2010-12-03 21:22 ` Jon Harrop
2010-12-03 21:45 ` Philippe Strauss
2010-12-03 15:32 ` Michael Ekstrand
2010-12-03 21:34 ` Jon Harrop
2010-12-03 20:07 ` Jon Harrop
2010-12-05 16:37 ` Benedikt Meurer
2010-12-05 16:57 ` Török Edwin
2010-12-05 20:54 ` Benedikt Meurer
2010-12-05 20:12 ` Jon Harrop
2010-12-05 21:21 ` Benedikt Meurer
2010-12-05 21:44 ` Benedikt Meurer
2010-12-06 22:38 ` Jon Harrop
2010-12-05 22:41 ` Erik de Castro Lopo
2010-12-05 22:34 ` Erik de Castro Lopo
2010-12-06 8:27 ` Benedikt Meurer
2010-12-06 9:28 ` David Rajchenbach-Teller
2010-12-06 11:08 ` Richard Jones
2010-12-06 20:18 ` Jon Harrop
2010-12-01 0:16 ` [Caml-list] OCamlJIT2 vs. OCamlJIT Erik de Castro Lopo
2010-12-01 1:34 ` Yoann Padioleau
2010-12-01 12:58 ` Jon Harrop
2010-12-01 13:55 ` ivan chollet
2010-11-30 21:19 ` 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='0a8b01cb90da$da5e6240$8f1b26c0$@com' \
--to=jonathandeanharrop@googlemail.com \
--cc=bluestorm.dylc@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=padator@wanadoo.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