From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 D474A7FCCB for ; Mon, 11 May 2015 15:31:07 +0200 (CEST) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of mshinwell@janestreet.com) identity=pra; client-ip=38.105.200.112; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="mshinwell@janestreet.com"; x-sender="mshinwell@janestreet.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of mshinwell@janestreet.com designates 38.105.200.112 as permitted sender) identity=mailfrom; client-ip=38.105.200.112; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="mshinwell@janestreet.com"; x-sender="mshinwell@janestreet.com"; 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@mxout1.mail.janestreet.com) identity=helo; client-ip=38.105.200.112; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="mshinwell@janestreet.com"; x-sender="postmaster@mxout1.mail.janestreet.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0BbAQCzrlBVnHDIaSZcg2NeBoMYsnuOY4FYhgUCgSgHOhIBAQEBAQEBEQEBAQEBBhYJT4QhAQEEEhEdAQEsCwEPCwsNAgIJHQICIhIBBQEKEgYTEhCHdQMSAwqnVj4xikhwhGIBBYkxA4UcAQEBAQEBAQEBAQEBAQEBAQEVBgqBF4kWgQKFBQeCaIFFhUcKkQ+GRYEkPoMcjgSCCxIjgRWENlOCRgEBAQ X-IPAS-Result: A0BbAQCzrlBVnHDIaSZcg2NeBoMYsnuOY4FYhgUCgSgHOhIBAQEBAQEBEQEBAQEBBhYJT4QhAQEEEhEdAQEsCwEPCwsNAgIJHQICIhIBBQEKEgYTEhCHdQMSAwqnVj4xikhwhGIBBYkxA4UcAQEBAQEBAQEBAQEBAQEBAQEVBgqBF4kWgQKFBQeCaIFFhUcKkQ+GRYEkPoMcjgSCCxIjgRWENlOCRgEBAQ X-IronPort-AV: E=Sophos;i="5.13,407,1427752800"; d="scan'208";a="117324527" Received: from mxout1.mail.janestreet.com ([38.105.200.112]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-SHA; 11 May 2015 15:31:06 +0200 Received: from tot-qpr-mailcore1.delacy.com ([172.27.56.68] helo=tot-qpr-mailcore1) by mxout1.mail.janestreet.com with smtp (Exim 4.82) (envelope-from ) id 1YrnnU-0001Yd-0y for caml-list@inria.fr; Mon, 11 May 2015 09:31:04 -0400 X-JS-Flow: external Received: by tot-qpr-mailcore1 with JS-mailcore (0.1) (envelope-from ) id BVUK8Y-AAAGWK-Ae; 2015-05-11 09:31:04.016233-04:00 Received: from mail-oi0-f45.google.com ([209.85.218.45]) by mxgoog1.mail.janestreet.com with esmtps (UNKNOWN:AES128-GCM-SHA256:128) (Exim 4.72) (envelope-from ) id 1YrnnT-00069I-OD for caml-list@inria.fr; Mon, 11 May 2015 09:31:03 -0400 Received: by oift201 with SMTP id t201so104130486oif.3 for ; Mon, 11 May 2015 06:31:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=janestreet.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xbA4QsAQWilwu0bvr8ol4byePpp/dGLTH3qpnySY0iU=; b=GR4Bi22m42mIsIlM/fu/muKgERXHmDGI8zZgM0G0f8wLzDiRxd/WEEs6foDzch+/c7 UYF6H/8068OZj/vYyLWp8QGrMeFGnHv2OxpRoXrnFwqARxjdd+L/L1o2O2U5Kjfbp9vt Qtmf9PMg/LftLHhP1eAUih/qv+GLvc5SLr6Og= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=xbA4QsAQWilwu0bvr8ol4byePpp/dGLTH3qpnySY0iU=; b=VNAlj6sjOX5F+lyJ/5It/6/sAr3U+W2xS55TQUtC6Xa58GL22eMjnlOjsf8j54v140 9YA+invHASDORQStT9aJisxpvDtsZXInKiilGkZ0KP/JpOzvZJbuC/fGr/av7lB6BZmT YEMcv+0j0zuLA+lxnRBAjInO09ZhSwZvEcsNSywT4zAZaKF3TSs334hdLD60JgL9tOru /aH1idxRfgDM82dE/kt6zG22HtMwLmNE7fMEXnu7Px4IHuNDrlDOTpKz9WTV6R8KQk/+ 3ce8L3g/GjJwRARmio4RknCm3gO16zvy4KZrloP28IvtHLh7JTnOTOP6UWeiOa/yVuNx isbg== X-Gm-Message-State: ALoCoQnRs88fJYGpcfntFYGzFNBLZ0kAhsFzx4jgVOqpW6fxb8LpuhhdwJ7N9koTlq1Fa6kNva3LLSarU9N6DGWdIhq9HBUgpoT19GOTa86xQJfusGPmkicNOfkD1uVpX/zjKP+drdu9 X-Received: by 10.60.179.200 with SMTP id di8mr7902527oec.1.1431351063340; Mon, 11 May 2015 06:31:03 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.60.179.200 with SMTP id di8mr7902521oec.1.1431351063261; Mon, 11 May 2015 06:31:03 -0700 (PDT) Received: by 10.202.107.209 with HTTP; Mon, 11 May 2015 06:31:03 -0700 (PDT) In-Reply-To: <555096AB.9090208@inria.fr> References: <555096AB.9090208@inria.fr> Date: Mon, 11 May 2015 09:31:03 -0400 Message-ID: From:Mark Shinwell To:Francois Berenger Cc:"caml-list@inria.fr" Content-Type: text/plain; charset=UTF-8 X-JS-Processed-by: mailcore X-Validation-by: mshinwell@janestreet.com Subject: Re: [Caml-list] OCaml release roadmap 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. Mark On 11 May 2015 at 07:46, Francois Berenger wrote: > On 05/06/2015 07:24 PM, Damien Doligez wrote: >> >> Dear OCaml users, >> >> We are now preparing release 4.02.2, mostly a bug-fix release with a >> few new features. We are planning to release it in the first week of >> June (about 1 month from now). If you want to try a preview, get it: >> - from github: < https://github.com/ocaml/ocaml/tree/4.02 > (don't >> forget to switch to branch 4.02 after cloning) >> - through OPAM: opam switch 4.02.0+trunk (watch out for the misnomer) >> If you find bugs, please report them as quickly as possible. >> >> As for the next major release, it will include a number of new >> features (including, if all goes well, support for multicore). It will >> be released some time around the end of this year. > > > Who added the support for multicore? > > Will it have an impact on the performance of sequential programs (i.e. which > don't use multicore)? > > Does it mean we will be able to write parallel code that scales better > than what we currently can get with parmap? > I.e. we could see a speedup even if the task is very fine grain. > > Will we have to rewrite Parmap ? ;) > >> -- Damien Doligez for the OCaml development team >> > > -- > Regards, > Francois. > > > -- > Caml-list mailing list. Subscription management and archives: > https://sympa.inria.fr/sympa/arc/caml-list > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners > Bug reports: http://caml.inria.fr/bin/caml-bugs