caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Basile Starynkevitch <basile@starynkevitch.net>
To: caml-list@inria.fr
Subject: Re: [Caml-list] serialization of closures
Date: Thu, 3 Jun 2021 19:20:32 +0200	[thread overview]
Message-ID: <950e3e57-ec7b-b85d-c3f5-7e11a5c336dd@starynkevitch.net> (raw)
In-Reply-To: <20210603171753.nci6b45fepzyupnm@oulala>

[-- Attachment #1: Type: text/plain, Size: 926 bytes --]


On 03/06/2021 19:17, Christophe Raffalli wrote:
> Hello dear camlers,
>
> I just noticed that in 4.12+effect, in the road to multicore, we have now the
> nice exception:
>
>    Failure("Serializing closures is broken in multicore")
>
> This is a bit a pity: if you want to use both multicore and multi-machine
> parallelism, then, marshalling closures was useful for communication between
> machines in some cases. Is it a final decision or serialization of closures will
> be lost forever in OCaml ?


My guess is that serialization of closures might work in bytecode, and 
is broken in native, in relation to ASLR 
<https://en.wikipedia.org/wiki/Address_space_layout_randomization>.

Of course, I could be very wrong.


Cheers

-- 
Basile Starynkevitch                  <basile@starynkevitch.net>
(only mine opinions / les opinions sont miennes uniquement)
92340 Bourg-la-Reine, France
web page: starynkevitch.net/Basile/


[-- Attachment #2: Type: text/html, Size: 1528 bytes --]

  reply	other threads:[~2021-06-03 17:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03 17:17 Christophe Raffalli
2021-06-03 17:20 ` Basile Starynkevitch [this message]
2021-06-04 17:14 ` Xavier Leroy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=950e3e57-ec7b-b85d-c3f5-7e11a5c336dd@starynkevitch.net \
    --to=basile@starynkevitch.net \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).