caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Raoul Duke <raould@gmail.com>
To: OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] whither portability?
Date: Sun, 27 Sep 2015 10:19:29 -0700	[thread overview]
Message-ID: <CAJ7XQb51ZjGXAyy7NStdZaQAw31vv7F+jEqLD65d5GE_mh0PWg@mail.gmail.com> (raw)
In-Reply-To: <1acefe77c30ce33c0adba49605bd9325@whitequark.org>

> Right now, LLVM IR (of which the bitcode is a serialization) is not
> flexible enough to express the invariants and metadata required
> for the OCaml GC to function[1]. Even if someone released the necessary,
> highly nontrivial changes to both LLVM and OCaml today, it would take
> many months for them to be reviewed, merged & propagated into Apple's
> LLVM fork--all for a small improvement in a select few numeric workloads
> that can benefit from using the instruction selector tailored for
> the particular device, and a substantial reduction in being able to
> debug your code[2].

Thanks for the details. I am (only) a little bit aware of the history
of LLVM vs. GCs, so I can believe what you report. I would much prefer
to be able to debug, as well.

(Given Apple, I wouldn't be surprised if an a year they required
bitcode, however.)

  reply	other threads:[~2015-09-27 17:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-25 21:13 Raoul Duke
2015-09-26  9:28 ` Gerd Stolpmann
2015-09-26 12:48   ` Raoul Duke
2015-09-26 15:59     ` whitequark
2015-09-26 16:21       ` Gerd Stolpmann
2015-09-26 23:29       ` Raoul Duke
2015-09-27  0:47         ` Spiros Eliopoulos
2015-09-27  0:51           ` Raoul Duke
2015-09-27  0:20       ` Oliver Bandel
2015-09-27  0:27         ` Yotam Barnoy
2015-09-27 14:10           ` Oliver Bandel
2015-09-27  0:55       ` Raoul Duke
2015-09-27 14:33         ` whitequark
2015-09-27 17:19           ` Raoul Duke [this message]
2015-09-27 17:41             ` whitequark
2015-09-26 17:10     ` Gerd Stolpmann

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=CAJ7XQb51ZjGXAyy7NStdZaQAw31vv7F+jEqLD65d5GE_mh0PWg@mail.gmail.com \
    --to=raould@gmail.com \
    --cc=caml-list@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;
as well as URLs for NNTP newsgroup(s).