From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 BC91D7FC41 for ; Thu, 5 Mar 2015 03:31:50 +0100 (CET) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of masateru.k@gmail.com) identity=pra; client-ip=209.85.216.173; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="masateru.k@gmail.com"; x-sender="masateru.k@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of masateru.k@gmail.com designates 209.85.216.173 as permitted sender) identity=mailfrom; client-ip=209.85.216.173; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="masateru.k@gmail.com"; x-sender="masateru.k@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-qc0-f173.google.com) identity=helo; client-ip=209.85.216.173; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="masateru.k@gmail.com"; x-sender="postmaster@mail-qc0-f173.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0AAAQB9v/dUlK3YVdFahC4EyCsHTQEBAQEBARABAQEBBwsLCRIwhAYiLgEbHgMSCAECBV0BEQEFAVeHeAEDEa1igys+MY0ZgnePWQoZJw1UhQ0BBQ6QD4QVBYphjm+SIBIjgQwJgWgMAYIrLzGCQwEBAQ X-IPAS-Result: A0AAAQB9v/dUlK3YVdFahC4EyCsHTQEBAQEBARABAQEBBwsLCRIwhAYiLgEbHgMSCAECBV0BEQEFAVeHeAEDEa1igys+MY0ZgnePWQoZJw1UhQ0BBQ6QD4QVBYphjm+SIBIjgQwJgWgMAYIrLzGCQwEBAQ X-IronPort-AV: E=Sophos;i="5.11,344,1422918000"; d="scan'208";a="102149787" Received: from mail-qc0-f173.google.com ([209.85.216.173]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 05 Mar 2015 03:31:49 +0100 Received: by qcyl6 with SMTP id l6so41086732qcy.2 for ; Wed, 04 Mar 2015 18:31:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=AQpjxTyyyXgPJzqSvyzEvPUTuz55455efssHnJA9F94=; b=WU5Do8T4gg5VaH01j5c3Ocr+SCLYtESSwFuI0Fm/wMNu4m0bgZHjCskjGnaw+Hd9eG 30Gv8UQyd5+0YIJqsTYChn10nnTlUWFNqx4uDSZE+5G8etCegYp+EgopjHraGTlAoHVd BU3BZiBz1P/hUP1HwOBt/gkagge/5kwzzeeZ4dvfREPzBsuyJvsztKAnGdoJr56dWWpy d4LZ3/qYXpBVvymFw74NA4IAjQLLmaWYZ31hC6SGi54ZofXs+lK/0mWGLQzCCqpefs93 SE/TozJ6Pq5BJbSn1ley9efgiq1SBrS5bX/qGCFv4vbF9OVq2R6b1ALu8A2gUH3KLTbr qeHQ== X-Received: by 10.140.239.136 with SMTP id k130mr10168246qhc.2.1425522708735; Wed, 04 Mar 2015 18:31:48 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.98.118 with HTTP; Wed, 4 Mar 2015 18:31:18 -0800 (PST) From: Masateru Kawaguchi Date: Thu, 5 Mar 2015 11:31:18 +0900 Message-ID: To: caml-list@inria.fr Content-Type: multipart/alternative; boundary=001a11359256ac8a7d0510815ee1 Subject: [Caml-list] C function calls OCaml function in multithreads --001a11359256ac8a7d0510815ee1 Content-Type: text/plain; charset=ISO-8859-1 Hello, I'm implementing a C function that calls an OCaml function. If the C function is called by multithreads, the OCaml function works fine ? Is that all right when the C function uses mutual exclusion locks ? Best regards, Masateru Kawaguchi --001a11359256ac8a7d0510815ee1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello,

I'm implementing = a C function that calls an OCaml function.

If = the C function is called by multithreads, the OCaml function works fine ?
Is that all right when the C function uses mutual exclusion locks = ?=A0

Best regards,
Masateru Kawaguchi

--001a11359256ac8a7d0510815ee1--