From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ygrekheretix@gmail.com>
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 F0118820A1
	for <caml-list@sympa.inria.fr>; Tue, 10 Sep 2013 19:43:51 +0200 (CEST)
Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  ygrekheretix@gmail.com) identity=pra;
  client-ip=209.85.192.174;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="ygrekheretix@gmail.com";
  x-sender="ygrekheretix@gmail.com";
  x-conformance=sidf_compatible
Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of
  ygrekheretix@gmail.com designates 209.85.192.174 as permitted
  sender) identity=mailfrom; client-ip=209.85.192.174;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="ygrekheretix@gmail.com";
  x-sender="ygrekheretix@gmail.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@mail-pd0-f174.google.com) identity=helo;
  client-ip=209.85.192.174;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="ygrekheretix@gmail.com";
  x-sender="postmaster@mail-pd0-f174.google.com";
  x-conformance=sidf_compatible
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AswBAHhZL1LRVcCum2dsb2JhbABbgz+DNL9dgSYWDgEBAQEBBgsLCRQogiUBAQQBOgYBGx4DAQsGBSETEg8UEQEFAQ4BDRmHbwEDCQUBDKIWjFGDBYQpChknDWSINQEFDI9WFoQHA4k0hXiISQGBL45TQYRV
X-IPAS-Result: AswBAHhZL1LRVcCum2dsb2JhbABbgz+DNL9dgSYWDgEBAQEBBgsLCRQogiUBAQQBOgYBGx4DAQsGBSETEg8UEQEFAQ4BDRmHbwEDCQUBDKIWjFGDBYQpChknDWSINQEFDI9WFoQHA4k0hXiISQGBL45TQYRV
X-IronPort-AV: E=Sophos;i="4.90,879,1371074400"; 
   d="scan'208";a="26393978"
Received: from mail-pd0-f174.google.com ([209.85.192.174])
  by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 10 Sep 2013 19:43:50 +0200
Received: by mail-pd0-f174.google.com with SMTP id y13so7946525pdi.5
        for <caml-list@inria.fr>; Tue, 10 Sep 2013 10:43:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=date:from:to:subject:message-id:in-reply-to:references:mime-version
         :content-type:content-transfer-encoding;
        bh=nhjsgu0yBvjXdKQEIaB8ck/gEg02Sb9LduhTGfMgisA=;
        b=SEupl+sjWE0NcXM0x8C7KsoswH3bVNPbIgN0lCfi/JyeDlfX7gICnkxQHVtzK5Oenm
         Ka4OhLCKzktU8Ct+gcQrAozkf+ZtKUai44j0AVBw6qTQEQ1OVG9WpvZhEOb/iFJMAtJZ
         4tYnw8HFm86L1O9PQIg+OmG+SgrxQlRlz1R4ZqbSSjH+4Hp0pbLayN9usNZ9XGaykScH
         2aqPgnea9bd4L1ffQ1t/cnJSCYrjr0ghbuYouKw4zQ2wIMKKcxAmEHDqT2hjcc+E1uUd
         WUwQWKsmMzadoqlRO+VFuEuUiPdqQzkKVbjmuf48PyhxHZUdeKjqSeAS3k+KpUBQeaQ3
         V4RA==
X-Received: by 10.68.218.6 with SMTP id pc6mr3248235pbc.187.1378835029391;
        Tue, 10 Sep 2013 10:43:49 -0700 (PDT)
Received: from kiwi.local.tld (cm241.eta97.maxonline.com.sg. [116.88.97.241])
        by mx.google.com with ESMTPSA id gh9sm24325768pbc.40.1969.12.31.16.00.00
        (version=SSLv3 cipher=RC4-SHA bits=128/128);
        Tue, 10 Sep 2013 10:43:48 -0700 (PDT)
Date: Wed, 11 Sep 2013 01:43:44 +0800
From: ygrek <ygrekheretix@gmail.com>
To: caml-list@inria.fr
Message-ID: <20130911014344.41b4b798@kiwi.local.tld>
In-Reply-To: <20130910165355.GA17264@notk.org>
References: <20130910020157.41613.qmail@www1.g3.pair.com>
	<522F4CE3.5040507@inria.fr>
	<20130910165355.GA17264@notk.org>
X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [Caml-list] Accelerating compilation

On Tue, 10 Sep 2013 18:53:55 +0200
Adrien Nader <adrien@notk.org> wrote:

> IIRC the name for unix-related functions are different for Win32, or
> maybe that some are missing (non-implemented functions). There was
> something that broke building the compiler (I'm really having a hard
> time remembering the details though).
> 
> It's been months since I last touched that part but in the end it was
> workable and anyway, I doubt many people will try to use bytecode for
> Windows anyway.

They will, and they are brave :
http://roscidus.com/blog/blog/2013/07/07/ocaml-binary-compatibility/#windows--linux-compatibility

--