From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <rich@annexia.org>
X-Original-To: caml-list@sympa.inria.fr
Delivered-To: caml-list@sympa.inria.fr
Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104])
	by sympa.inria.fr (Postfix) with ESMTPS id F3F2F7ED99
	for <caml-list@sympa.inria.fr>; Tue, 26 May 2015 19:13:46 +0200 (CEST)
Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  rich@annexia.org) identity=pra; client-ip=80.68.91.176;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="rich@annexia.org";
  x-sender="rich@annexia.org"; x-conformance=sidf_compatible
Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of
  rich@annexia.org designates 80.68.91.176 as permitted sender)
  identity=mailfrom; client-ip=80.68.91.176;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="rich@annexia.org";
  x-sender="rich@annexia.org"; x-conformance=sidf_compatible;
  x-record-type="v=spf1"
Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  postmaster@furbychan.cocan.org) identity=helo;
  client-ip=80.68.91.176;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="rich@annexia.org";
  x-sender="postmaster@furbychan.cocan.org";
  x-conformance=sidf_compatible
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D8CgBOqWRV/7BbRFBcgxCEA65VAQUBgQSYUgKBRzwQAQEBAQEBAYEKQQWDXQEBBDo/EAsOCgkTEg8FKCGIQwHUBAEBAQcCIIYWOYRrhQUHgxeBFgWQTII8iw6BKpItg1kjg3k9gngBAQE
X-IPAS-Result: A0D8CgBOqWRV/7BbRFBcgxCEA65VAQUBgQSYUgKBRzwQAQEBAQEBAYEKQQWDXQEBBDo/EAsOCgkTEg8FKCGIQwHUBAEBAQcCIIYWOYRrhQUHgxeBFgWQTII8iw6BKpItg1kjg3k9gngBAQE
X-IronPort-AV: E=Sophos;i="5.13,499,1427752800"; 
   d="scan'208";a="127875498"
Received: from furbychan.cocan.org ([80.68.91.176])
  by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/AES128-SHA; 26 May 2015 19:13:46 +0200
Received: from rich by furbychan.cocan.org with local (Exim 4.84)
	(envelope-from <rich@annexia.org>)
	id 1YxIQC-000158-BI; Tue, 26 May 2015 18:13:44 +0100
Date: Tue, 26 May 2015 18:13:44 +0100
From: "Richard W.M. Jones" <rich@annexia.org>
To: Mark Shinwell <mshinwell@janestreet.com>
Cc: Francois Berenger <francois.berenger@inria.fr>,
	"caml-list@inria.fr" <caml-list@inria.fr>
Message-ID: <20150526171344.GA4073@annexia.org>
References: <CALGm1VhSaSQi3_ooL8OWY3SyPFjn8mkiQPMis6MU1yVtBsMbHA@mail.gmail.com>
 <555096AB.9090208@inria.fr>
 <CAM3Ki77cyDFyJeyoxVM6zzd0YVGQE1tVUuEM1aLPD=rtzDv5AA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAM3Ki77cyDFyJeyoxVM6zzd0YVGQE1tVUuEM1aLPD=rtzDv5AA@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Subject: Re: [Caml-list] OCaml release roadmap

On Mon, May 11, 2015 at 09:31:03AM -0400, Mark Shinwell wrote:
> I can answer two of your points:
> 
> I think it's unlikely that multicore support is going to be in a
> production-ready state for 4.03, although I may be proven wrong.  It
> seems plausible that a beta version of the support will be ready at
> that time, however.
> 
> Degradation of the performance of code not using the new parallelism
> features (but possibly using the existing thread support) is a matter
> of serious concern for some users, and best efforts will be made to
> minimize or eliminate it.  We will know more on this front in the next
> few months.

Will there be implications for C bindings?  We have rather a lot ...

Rich.

-- 
Richard Jones
Red Hat