caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Benedikt Meurer <benedikt.meurer@googlemail.com>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: "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 13:08:40 +0100	[thread overview]
Message-ID: <A46ACDBE-9251-42BB-AC04-86FD5DD8593B@googlemail.com> (raw)
In-Reply-To: <CAPFanBEJOtQ5=VD8_-1T2xUPqpL5DvRFX+mtkEPV3LG_hrbUQg@mail.gmail.com>


On Dec 9, 2011, at 10:58 , Gabriel Scherer wrote:

>> I find the idea of making ocamlopt a GCC (or
>> LLVM) frontend the most sensible and constructive one I've seen in these
>> discussions.
> 
> I found back some of this links thanks to the excellent "OCaml Weekly
> News" summary:
>  http://alan.petitepomme.net/cwn/2011.08.02.html
> (Where Benedikt announces that he has a student working on an LLVM backend.)

You can follow the progress here: https://github.com/colinbenner/ocamlllvm

It does work for some simple examples already, but it's still very early prototype quality and requires a patched LLVM. LLVM as such is not a bad idea for the compiler backend, but getting things to work with stuff compiled by the regular OCaml backends is the difficult part. We'll see how that turns out.

>> However, one barrier is the licensing: QPL is incompatible with almost
>> any license (even QT does no longer use it!). Has it ever been
>> considered to switch the "public" license to e.g. GPLv3 (which looks
>> constraining enough, and compatible with GCC)?
> 
> Stéphane, I am surprised at how good your are at raising trollish topics !

I don't think it's a trollish topic raised by Stéphane. The QPL is a serious problem and I fear many of us may already already be violating the terms of the QPL, it would be nice to get rid of that issue at some point. The exact license (GPL, LGPL, MIT, BSD, Apache, ...) doesn't matter all that much, almost every other open source license is better than the QPL (just my 2c).

Benedikt

  parent reply	other threads:[~2011-12-09 12:08 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 [this message]
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
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=A46ACDBE-9251-42BB-AC04-86FD5DD8593B@googlemail.com \
    --to=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;
as well as URLs for NNTP newsgroup(s).