From: Stephen Dolan <stephen.dolan@cl.cam.ac.uk>
To: jon@ffconsultancy.com
Cc: Gabriel Scherer <gabriel.scherer@gmail.com>,
Pierre Chambart <pierre.chambart@laposte.net>,
Goswin von Brederlow <goswin-v-b@web.de>,
caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Why List.map does not be implemented tail-recursively?
Date: Tue, 2 Jun 2015 13:04:46 +0100 [thread overview]
Message-ID: <CA+mHimMfPCrF-5ai3uhKuee=m+LVjBc1e7WJ14WireiLWWmiHQ@mail.gmail.com> (raw)
In-Reply-To: <00fb01d09c62$c5da4ad0$518ee070$@ffconsultancy.com>
On Mon, Jun 1, 2015 at 1:02 PM, Jon Harrop <jon@ffconsultancy.com> wrote:
> What happens when the first allocation in the creation of a cyclic immutable structure incurs a minor collection?
>
> let rec xs = 0::ys and ys = 1::xs
Such allocations are handled specially. Essentially, it boils down to
having a write barrier on the final mutation that ties the knot on the
cyclic data structure. This isn't multicore-specific: see
caml_alloc_dummy and caml_update_dummy in byterun/alloc.c for the gory
details.
In multicore, this mutation needs to promote (copy to the shared heap)
the cyclic data structure if the head node has already been collected.
Stephen
next prev parent reply other threads:[~2015-06-02 12:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-28 19:31 Shuai Wang
2014-09-28 19:36 ` Gabriel Scherer
2014-09-28 19:45 ` Anthony Tavener
2014-09-29 12:08 ` Goswin von Brederlow
2014-09-29 14:02 ` Pierre Chambart
2014-09-29 15:44 ` Yaron Minsky
2014-09-29 21:00 ` Gabriel Scherer
2014-09-30 8:46 ` [Caml-list] Why List.map does not be implemented oleg
2014-09-30 9:07 ` Gabriel Scherer
2014-10-01 10:29 ` oleg
2014-10-01 12:00 ` Gerd Stolpmann
2014-10-29 10:11 ` Gabriel Scherer
2014-10-02 10:09 ` [Caml-list] Why List.map does not be implemented tail-recursively? Stephen Dolan
2015-06-01 12:02 ` Jon Harrop
2015-06-02 12:04 ` Stephen Dolan [this message]
2015-06-05 10:21 ` Goswin von Brederlow
2014-09-30 6:29 ` Goswin von Brederlow
-- strict thread matches above, loose matches on Subject: below --
2014-09-28 19:28 Shuai Wang
2014-09-28 19:45 ` Malcolm Matalka
2014-09-28 20:26 ` Yaron Minsky
2014-09-29 2:31 ` Shuai Wang
2014-09-29 4:09 ` Anthony Tavener
2014-09-29 5:40 ` Martin Jambon
2014-09-29 9:13 ` Erkki Seppala
2014-09-29 9:15 ` Erkki Seppala
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='CA+mHimMfPCrF-5ai3uhKuee=m+LVjBc1e7WJ14WireiLWWmiHQ@mail.gmail.com' \
--to=stephen.dolan@cl.cam.ac.uk \
--cc=caml-list@inria.fr \
--cc=gabriel.scherer@gmail.com \
--cc=goswin-v-b@web.de \
--cc=jon@ffconsultancy.com \
--cc=pierre.chambart@laposte.net \
/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).