From: oliver <oliver@first.in-berlin.de>
To: "Török Edwin" <edwintorok@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Why NOT to compile OCaml via C
Date: Sat, 10 Dec 2011 00:38:03 +0100 [thread overview]
Message-ID: <20111209233802.GD9346@siouxsie> (raw)
In-Reply-To: <4EE21B89.2010306@gmail.com>
On Fri, Dec 09, 2011 at 04:30:33PM +0200, Török Edwin wrote:
[...]
> Is binary compatibility with a specific version of ocamlopt necessary?
> I think that ocaml-llvm could detect the mismatch and print an error, like you get for an ABI mismatch.
>
> Sure it'd be nice to be able to try out ocaml-llvm without rebuilding all OCaml packages,
> but such a rebuilt is required when new OCaml releases come out anyway, as they are usually not ABI compatible with each-other.
[...]
If it produces the same output as OCaml does now,
why to investigate ocaml-llvm?
Maybe changing OCaml from non-optimizing to an optimizing compiler
would outperform any llvm attempts.
Mabye the core team alkready works on this... who knows? ;-)
Ciao,
Oliver
next prev parent reply other threads:[~2011-12-09 23:38 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 [this message]
2011-12-09 21:22 ` Richard W.M. Jones
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=20111209233802.GD9346@siouxsie \
--to=oliver@first.in-berlin.de \
--cc=caml-list@inria.fr \
--cc=edwintorok@gmail.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).