From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <jhc0033@gmail.com>
X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr
X-Spam-Level: 
X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled 
	version=3.1.3
X-Original-To: caml-list@yquem.inria.fr
Delivered-To: caml-list@yquem.inria.fr
Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105])
	by yquem.inria.fr (Postfix) with ESMTP id 137B4BBAF
	for <caml-list@yquem.inria.fr>; Thu, 10 Jul 2008 07:57:47 +0200 (CEST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvAlAMZBdUhIDszuSWdsb2JhbACLDocHOQEBFQYBBgYRljiGfA
X-IronPort-AV: E=Sophos;i="4.30,336,1212357600"; 
   d="scan'208";a="27186065"
Received: from qb-out-0506.google.com ([72.14.204.238])
  by mail4-smtp-sop.national.inria.fr with ESMTP; 10 Jul 2008 07:57:46 +0200
Received: by qb-out-0506.google.com with SMTP id p30so7021185qba.15
        for <caml-list@yquem.inria.fr>; Wed, 09 Jul 2008 22:57:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from:to
         :subject:mime-version:content-type:content-transfer-encoding
         :content-disposition;
        bh=BbPy+UqUI1D4FDCn/Jl7x8SuXvxDW+scM9RNFIX0V3w=;
        b=pG3hRkOe1YNocAAQS3Ln9mwNhtLIk5uGXmjdnBIo5GOlfHNhG0KC/P2knfBLUgleyE
         cHvIapklyzoOGL8R02M0Vr8NXlpGH+bvfxmYAvriyJG84YPG7Q/ADpmKsTPsP8lQ2isN
         Ps52xJfzK6yUwOMZXK2QasYIXEj1WPH0RLkjk=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:mime-version:content-type
         :content-transfer-encoding:content-disposition;
        b=Xm3PHXrmdLGKo7gB0vrKoObNOQy5XDmQDzMhq/gKbTvEIKpve/qm7g5F2tTy62OXhV
         DkeI2SM6Rk25/pFa2VG+TWioRPxxwQJ/EV9/nizAWMyX90K9+tjzpfi/nJ3JFl4S0i6k
         8CvWoI0j/o70WBWrqDJYxFxwwWJEgtUNkUBys=
Received: by 10.114.53.1 with SMTP id b1mr10389207waa.165.1215669464565;
        Wed, 09 Jul 2008 22:57:44 -0700 (PDT)
Received: by 10.114.147.12 with HTTP; Wed, 9 Jul 2008 22:57:44 -0700 (PDT)
Message-ID: <c6c368760807092257v7a125fey534fbc6d5444d14@mail.gmail.com>
Date: Wed, 9 Jul 2008 22:57:44 -0700
From: "J C" <jhc0033@gmail.com>
To: caml-list@yquem.inria.fr
Subject: thousands of CPU cores
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam: no; 0.00; haskell:01 jhc:98 0033:98 cnet:98 threads:01 threads:01 sml:01 primitives:01 caml:02 caml:02 investment:93 mouth:93 thousands:91 looks:08 product:89 

I know that Caml team wanted to see if many-core shared-memory systems
were going to stick around before bothering with Caml development that
takes advantage of them.

Well, it looks like they are here to stay, after all:

http://news.cnet.com/8301-13924_3-9981760-64.html

As much as I hate to look a gift horse in the mouth, and I think Caml
has been a great and grossly underappreciated product, I need to see
if writing Caml is a viable code investment for the coming years or
something like Haskell, SML, F# or even Ada will be a better long-term
alternative.

Are there plans to make Caml threads OS-native threads, or add
OpenMP-style primitives, or otherwise support multiple CPU cores? And
if so, roughly in what time frame?