caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Mark Shinwell <mshinwell@janestreet.com>
To: Francois Berenger <francois.berenger@inria.fr>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml release roadmap
Date: Mon, 11 May 2015 09:31:40 -0400	[thread overview]
Message-ID: <CAM3Ki76XbOz+a5MSf2TTtVBQhJY+_Aga-vdmcU95ODrvnt5NPg@mail.gmail.com> (raw)
In-Reply-To: <CAM3Ki77cyDFyJeyoxVM6zzd0YVGQE1tVUuEM1aLPD=rtzDv5AA@mail.gmail.com>

Sorry, I missed one paragraph: the multicore support is being
developed at OCaml Labs in Cambridge, UK.

Mark

On 11 May 2015 at 09:31, Mark Shinwell <mshinwell@janestreet.com> 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.
>
> Mark
>
> On 11 May 2015 at 07:46, Francois Berenger <francois.berenger@inria.fr> 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

  reply	other threads:[~2015-05-11 13:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06 17:24 Damien Doligez
2015-05-11 11:46 ` Francois Berenger
2015-05-11 13:31   ` Mark Shinwell
2015-05-11 13:31     ` Mark Shinwell [this message]
2015-05-26 17:13     ` Richard W.M. Jones
2015-06-04 20:34       ` Damien Doligez
2015-05-13 13:20 ` Jonas Jensen
2015-05-14 20:51   ` Damien Doligez
2015-05-14 21:20     ` Gabriel Scherer

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=CAM3Ki76XbOz+a5MSf2TTtVBQhJY+_Aga-vdmcU95ODrvnt5NPg@mail.gmail.com \
    --to=mshinwell@janestreet.com \
    --cc=caml-list@inria.fr \
    --cc=francois.berenger@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).