From: "Richard W.M. Jones" <rich@annexia.org>
To: Benedikt Meurer <benedikt.meurer@googlemail.com>
Cc: "Gabriel Scherer" <gabriel.scherer@gmail.com>,
"Stéphane Glondu" <steph@glondu.net>,
oleg@okmij.org, caml-list@inria.fr, ontologiae@gmail.com,
caml@inria.fr
Subject: Re: [Caml-list] Why NOT to compile OCaml via C
Date: Fri, 9 Dec 2011 21:22:16 +0000 [thread overview]
Message-ID: <20111209212216.GA29092@annexia.org> (raw)
In-Reply-To: <59A74C55-C12B-4C98-9496-2E83BE8A39F0@googlemail.com>
On Fri, Dec 09, 2011 at 03:05:43PM +0100, Benedikt Meurer wrote:
> Hm, I'm not sure. It's really easy to generate LLVM code for OCaml
> in general, the problem is getting things to interact with legacy
> OCaml code, with exception handling being one of the most important
> issue.
As Edwin said, I don't think interaction with existing ocamlopt-
compiled code is that important. Debian and Fedora routinely
"recompile the world". What is more important is compatibility with C
extensions. How difficult is just C extension compatibility? Or
something that was mostly compatible but needed a few changes to C
extensions?
Rich.
--
Richard Jones
Red Hat
next prev parent reply other threads:[~2011-12-09 21:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 6:57 oleg
2011-12-09 7:52 ` Stéphane Glondu
2011-12-09 9:58 ` Gabriel Scherer
2011-12-09 10:06 ` [Caml-devel] " Jonathan Protzenko
2011-12-09 11:03 ` Mehdi Dogguy
2011-12-09 12:08 ` Benedikt Meurer
2011-12-09 12:37 ` Gabriel Scherer
2011-12-09 14:05 ` Benedikt Meurer
2011-12-09 14:30 ` Török Edwin
2011-12-09 14:51 ` Benedikt Meurer
2011-12-09 23:38 ` oliver
2011-12-09 21:22 ` Richard W.M. Jones [this message]
2011-12-10 9:36 ` Benedikt Meurer
2011-12-10 11:34 ` Jon Harrop
2011-12-09 23:01 ` oliver
2011-12-09 23:18 ` Goswin von Brederlow
2011-12-10 0:20 ` Till Varoquaux
2011-12-10 7:35 ` oleg
2011-12-10 15:40 ` Basile Starynkevitch
2011-12-10 23:56 ` Peter Hawkins
2011-12-11 8:24 ` Basile Starynkevitch
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=20111209212216.GA29092@annexia.org \
--to=rich@annexia.org \
--cc=benedikt.meurer@googlemail.com \
--cc=caml-list@inria.fr \
--cc=caml@inria.fr \
--cc=gabriel.scherer@gmail.com \
--cc=oleg@okmij.org \
--cc=ontologiae@gmail.com \
--cc=steph@glondu.net \
/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