From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: * X-Spam-Status: No, score=1.9 required=5.0 tests=AWL,DNS_FROM_RFC_ABUSE, DNS_FROM_RFC_POST,RCVD_IN_NJABL_PROXY autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by yquem.inria.fr (Postfix) with ESMTP id A8527BBAF for ; Thu, 24 Sep 2009 16:11:26 +0200 (CEST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AssCAA8bu0pDww+vm2dsb2JhbACRSnqIPQEBAQEBCAkKCROqIoExj2oBBQMBhBcF X-IronPort-AV: E=Sophos;i="4.44,445,1249250400"; d="scan'208";a="36746441" Received: from web111508.mail.gq1.yahoo.com ([67.195.15.175]) by mail1-smtp-roc.national.inria.fr with SMTP; 24 Sep 2009 16:11:25 +0200 Received: (qmail 15387 invoked by uid 60001); 24 Sep 2009 14:11:24 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1253801484; bh=NioJq90jtd09ifC/A0StBeUb87fkVAkAJJ/hi74iOQw=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=wfsmGHrHKxa2Fd9akrQlPB00GmVko2JEUqxIuDLBOSAFXhU9Sb5hUbv9sx30oL2DrRkJfOSzWddJa9haIcjYfy5HT6XqW97j/R7d8YBGIfjkbkwxq1mpxvil6AANqPEJBSR2E5jwc6z3BO9+s3eRNun4dmAELLa/zKQ3UtG45Xk= DomainKey-Signature:a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=idGXrV4qmhKmp9PaTmeJdccMzxBWjEYUfF6woMPAzsn3F48/eSmkQ0Ufrrf11B4JdNtm1aFublr7uBqPehOKdMZjA2XDWwXlffNovNY33ejxkh0uEpy3kXvkl2dHJkgrc1DYhnUbf/cmfVFR1cmwoBkCKBsyvMfodhkCEoItRYE=; Message-ID: <613980.13877.qm@web111508.mail.gq1.yahoo.com> X-YMail-OSG: ZEfKtbwVM1k57MDDsKOJMWBMSl4jnobGmd4v55aoIXOws5hj4keaYj6fx.JcjYnaQVg6bHv_g_T7PCZ3OMNQ9PdqAUTzJyj2L.zlMvcCSjrCuHz08palgq5ltEW0o.mlHOtDfY31YcfQNli3t9WgWhTe6xqjEZRXJdlTSt0pOMZopwp25r_HFru64DATh5lcNwo8I5PiV3Yg0KaF0eC.dOkaKGwhlOKEnCowGxzyFaI6Z9wU9xkYDDV6f1ifBJ3MUXy.uZZ31jXdOSFoF13kwag3IV2HwZA4fBxSqg-- Received: from [213.205.70.208] by web111508.mail.gq1.yahoo.com via HTTP; Thu, 24 Sep 2009 07:11:24 PDT X-Mailer: YahooMailClassic/7.0.14 YahooMailWebService/0.7.347.3 Date: Thu, 24 Sep 2009 07:11:24 -0700 (PDT) From: Dario Teixeira Subject: Re: [Caml-list] OC4MC : OCaml for Multicore architectures To: caml-list@inria.fr, Philippe Wang In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam: no; 0.00; ocaml:01 cheers:01 compile-time:01 merging:01 caml-list:01 imperative:01 tree:02 tree:02 constructs:02 constructs:02 correctly:04 i'd:06 context:06 inria:06 implementing:06 Hi,=0A=0ACheers for the work you guys put into this project! And I'd like = to join=0Athe crowd that has questions, if I may:=0A=0Aa) If I understand c= orrectly, part of prerequisites for implementing the=0A new GC was cleani= ng up the excessive use of imperative constructs in=0A the compiler's tre= e. Will the new tree be also more amenable to the=0A implementation of n= ew language constructs such as GADTs?=0A=0Ab) Could you quantify the perfor= mance penalty (if any) of using the new GC=0A in a single-thread context?= And should this penalty be significant, are=0A there provisions for a c= ompile-time choice of which GC to use?=0A=0Ac) Is there an understanding be= tween you and the folks at INRIA concerning=0A the eventual merging of th= is code into the mainline tree?=0A=0AThanks a lot for your time!=0ABest reg= ards,=0ADario Teixeira=0A=0A=0A=0A