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 mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 8D3AA7F75C for ; Thu, 25 Sep 2014 13:19:07 +0200 (CEST) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of edwin+ml-ocaml@etorok.net) identity=pra; client-ip=62.113.205.31; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="edwin+ml-ocaml@etorok.net"; x-sender="edwin+ml-ocaml@etorok.net"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of edwin+ml-ocaml@etorok.net designates 62.113.205.31 as permitted sender) identity=mailfrom; client-ip=62.113.205.31; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="edwin+ml-ocaml@etorok.net"; x-sender="edwin+ml-ocaml@etorok.net"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of postmaster@mx.etorok.net designates 62.113.205.31 as permitted sender) identity=helo; client-ip=62.113.205.31; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="edwin+ml-ocaml@etorok.net"; x-sender="postmaster@mx.etorok.net"; x-conformance=sidf_compatible; x-record-type="v=spf1" X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjgFAGn5I1Q+cc0f/2dsb2JhbABggw5TV4MBx2qHTgKBCRYBe4QEAQEEIx04Ag8LGAICBRMDCwICCQMCAQIBRRMIAog+CatGeIUIkSICBIEsjnkWgmKBU4tLilSHCZVWg2Y6LwGCSQEBAQ X-IPAS-Result: AjgFAGn5I1Q+cc0f/2dsb2JhbABggw5TV4MBx2qHTgKBCRYBe4QEAQEEIx04Ag8LGAICBRMDCwICCQMCAQIBRRMIAog+CatGeIUIkSICBIEsjnkWgmKBU4tLilSHCZVWg2Y6LwGCSQEBAQ X-IronPort-AV: E=Sophos;i="5.04,596,1406584800"; d="scan'208";a="97832753" Received: from mx.etorok.net ([62.113.205.31]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-SHA; 25 Sep 2014 13:19:06 +0200 Received: by mx.etorok.net (OpenSMTPD) with ESMTP id edd3a0e9; for ; Thu, 25 Sep 2014 14:19:05 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=etorok.net; h= message-id:date:from:mime-version:to:references:in-reply-to :content-type:content-transfer-encoding; s=ml; l=699; bh=u44y/OR 8ENW/gjd+2adwqBIvsPs=; b=GshMQCKJ1J0ljumTSprQjRvCnGah/tA9jF89lZ+ ddBNkDvpUtevqS+xMPGCEPXTU38CQ0dw+aBVIH6dR1y3xSYt4TRRChMFYyds7anb tEvEKxTienYvWIcKkFJtVn2WRsILIomrTTk1YeJSJE85xHvW773LXQrXOTya/0Wd KRbo= Received: by mx.etorok.net (OpenSMTPD) with ESMTPSA id 598d06af; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; for ; Thu, 25 Sep 2014 14:19:05 +0300 (EEST) Message-ID: <5423FA28.8010003@etorok.net> Date: Thu, 25 Sep 2014 14:19:04 +0300 From: =?UTF-8?B?VMO2csO2ayBFZHdpbg==?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.0 MIME-Version: 1.0 To: caml-list@inria.fr References: In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Caml-list] Threads in byte code and native code work differently On 09/25/2014 01:26 PM, Kakadu wrote: > Hello, > > I have demo application [1] which creates OCaml threads and executes > C++ event loop from different libraries. When I compile it to native > code everything is fine but when I create custom bytecode executable > OCaml threads doesn't work. > > I have tested it with Qt4, Qt5 and GTK2 and behaviour is same. Can you > explain me what is happening there, please See https://sympa.inria.fr/sympa/arc/caml-list/2004-07/msg00305.html If you use '-vmthread' the runtime doesn't create new system threads for you. Is there a particular reason why you need to use 'ocamlc -vmthread' instead of 'ocamlc -thread'? Best regards, --Edwin