From: Erik de Castro Lopo <mle+ocaml@mega-nerd.com>
To: caml-list@inria.fr
Subject: Re: ocamlopt LLVM support (Was: [Caml-list] OCamlJIT2 vs. OCamlJIT)
Date: Mon, 6 Dec 2010 09:41:45 +1100 [thread overview]
Message-ID: <20101206094145.ac1e4a6e.mle+ocaml@mega-nerd.com> (raw)
In-Reply-To: <004901cb94b8$c03abf80$40b03e80$@com>
Jon Harrop wrote:
> My point was that HLVM's data representation is far more flexible than
> ocamlopt's,
Would you be able to list those differences for us?
> In particular, I am saying that (from my own measurements) LLVM does not
> cope with data representations like ocamlopt's at all well. Specifically,
> when you box and cast away type information.
Yes, thats obviously a mistake when generating typed assembly language
like LLVM.
> Ultimately, LLVM was built specifically to exploit a typed intermediate
> representation whereas ocamlopt removes type information very early.
That suggests that a first pass at adding an LLVM backend would
be to extend the used of typed data representations through to the
backend of the compiler.
> And faster tuples, ints, chars, complex numbers, low-dimensional
> vectors/matrices, hash tables and so on. More types (e.g. int16 and
> float32).
So specifically, you keep much more data in unboxed form?
Erik
--
----------------------------------------------------------------------
Erik de Castro Lopo
http://www.mega-nerd.com/
next prev parent reply other threads:[~2010-12-05 22:42 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 8:36 OCamlJIT2 vs. OCamlJIT 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
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 [this message]
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=20101206094145.ac1e4a6e.mle+ocaml@mega-nerd.com \
--to=mle+ocaml@mega-nerd.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