From: Edgar Friendly <thelema314@gmail.com>
To: Jon Harrop <jon@ffconsultancy.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] JIT & HLVM, LLVM
Date: Sun, 27 Sep 2009 15:07:10 -0400 [thread overview]
Message-ID: <4ABFB7DE.2050108@gmail.com> (raw)
In-Reply-To: <200909271951.27762.jon@ffconsultancy.com>
Jon Harrop wrote:
> C++ has those features and they are blamed for slow compilation. However,
> separate compilation is not the issue so much as dynamic loading.
>
Yes, dynamic loading doesn't mix with whole-program analysis. Although
I wonder if it's possible to have our cake and eat it too, with a fast
bytecode compiler and a slower native code compiler that does great
specialization.
> I think
> that an OCaml-like language that addresses OCaml's performance (including
> parallelism) and FFI issues would be much more widely useful and is an
> entirely achievable goal.
>
I'm not as committed to abandoning OCaml as you seem, and have hope for
incremental improvement of OCaml's weaknesses, although I realize we'll
have to break a number of things to get to where we both (and likely
many others) want to be.
E
next prev parent reply other threads:[~2009-09-27 19:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-27 17:18 David McClain
2009-09-27 17:22 ` [Caml-list] " Vincent Aravantinos
2009-09-27 17:35 ` Edgar Friendly
2009-09-27 18:51 ` Jon Harrop
2009-09-27 19:07 ` Edgar Friendly [this message]
2009-09-27 19:23 ` kcheung
2009-09-27 19:33 ` Jon Harrop
2009-09-27 21:10 ` Jon Harrop
2009-09-27 21:45 ` Vincent Aravantinos
2009-09-30 1:08 ` Mikkel Fahnøe Jørgensen
2009-09-30 11:57 ` Stéphane Glondu
2009-09-30 12:54 ` Mikkel Fahnøe Jørgensen
2009-09-30 13:42 ` Stéphane Glondu
2009-09-30 19:11 ` Mikkel Fahnøe Jørgensen
2009-09-30 15:22 ` Jon Harrop
2009-09-30 19:35 ` Mikkel Fahnøe Jørgensen
2009-09-28 12:25 ` Gerd Stolpmann
[not found] <20090927214558.D40C5BC5C@yquem.inria.fr>
2009-09-27 21:59 ` CUOQ Pascal
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=4ABFB7DE.2050108@gmail.com \
--to=thelema314@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=jon@ffconsultancy.com \
/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).