From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Re: Caml-list Digest, Vol 45, Issue 63
Date: Mon, 23 Mar 2009 00:06:22 +0000 [thread overview]
Message-ID: <200903230006.22306.jon@ffconsultancy.com> (raw)
In-Reply-To: <200903220004.49019.cdome@bk.ru>
On Saturday 21 March 2009 22:04:48 Andrey Riabushenko wrote:
> >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.
How will you generate stack maps for OCaml's GC without touching LLVM?
--
Dr Jon Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/?e
prev parent reply other threads:[~2009-03-23 0:00 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
2009-03-23 0:06 ` 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=200903230006.22306.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