caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Andrey Riabushenko <cdome@bk.ru>
To: caml-list@yquem.inria.fr
Subject: Re: Caml-list Digest, Vol 45, Issue 63
Date: Sun, 22 Mar 2009 00:04:48 +0200	[thread overview]
Message-ID: <200903220004.49019.cdome@bk.ru> (raw)
In-Reply-To: <20090321161035.9FA65BC1F@yquem.inria.fr>

>The OCaml compilers remove type information in the early stages of 
>compilation but LLVM is a typed assembler and needs that information to be 
>conveyed all the way through to the back end.
>
>The OCaml compilers make no attempt to provide reusable intermediate 
>representations.

It is problem that I will have to solve. Make sure that type info is passed.

>JIT is the single most important benefit of LLVM in the context of OCaml. 
With 
>JIT: You can instantiate polymorphic definitions for each combination of type 
>parameters that they are used with, providing substantial performance 
>mprovements.

>You can generate code that is optimized for the current machine.
>You can provide a performant top-level.
>Forgetting about JIT would certainly be a mistake.


Because I not going to JIT the ocaml source, I do not need neither LLVM 
libraries nor its ocaml bindings. I am going to produce LLVM assembler 
directly without introduction of new dependencies to the ocaml trunk (this is 
really important for ocaml). If I JIT the code then it will become a whole 
new project which we never be merged to the ocaml trunk. I do not want 

>Collaboration with the existing HLVM effort would probably be far more 
>productive.

Unfortunately, LLVM want ocaml LLVM front-end, they willl object against HLVM 
front-end. Too bad...



Do authors of ocaml has something to say about the idea?


       reply	other threads:[~2009-03-21 22:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090321161035.9FA65BC1F@yquem.inria.fr>
2009-03-21 22:04 ` Andrey Riabushenko [this message]
2009-03-23  0:06   ` [Caml-list] " 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=200903220004.49019.cdome@bk.ru \
    --to=cdome@bk.ru \
    --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;
as well as URLs for NNTP newsgroup(s).