From: Jean Krivine <jean.krivine@gmail.com>
To: Lukasz Stafiniak <lukstafi@gmail.com>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] out-of-the-heap 'a arrays ?
Date: Wed, 6 Nov 2013 10:19:42 +0100 [thread overview]
Message-ID: <CAEQoNCk6wYD5BEMFaq0NCtYsgCVp+Jxbepk=0xwRSBcBh=yyFQ@mail.gmail.com> (raw)
In-Reply-To: <CAJMfKEXWeUjOxk2tJ9i0E9-w=rCt5cxm1eGARWsMqC3Le0hdmw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
It seems that Ancient requires the values that are moved to be immutable
full point. I understand that there is a problem if you have pointers from
Ancient Heap to Ocaml Heap. But what about pointers that are internal to
the Ancient Heap ? Am I talking nonsense? Sorry if I do.
J
On Tue, Nov 5, 2013 at 8:15 PM, Lukasz Stafiniak <lukstafi@gmail.com> wrote:
> On Tue, Nov 5, 2013 at 8:06 PM, Lukasz Stafiniak <lukstafi@gmail.com>wrote:
>
>> On Tue, Nov 5, 2013 at 6:07 PM, Jean Krivine <jean.krivine@gmail.com>wrote:
>>
>>>
>>> As far as I understand there is a module Ancient which I can use to tell
>>> the GC to ignore my array but, if I understand well, it would only work if
>>> I use my array in a read only fashion.
>>>
>>
>> You cannot have pointers from Ancient heap to OCaml heap unless you do
>> weak pointer management (e.g. in the finalizer of a value). Otherwise I
>> think you're fine with modifying Ancient.
>>
>
> Scratch that, totally thoughtless -- of course values are moved around so
> you cannot have pointers from Ancient heap to OCaml heap, period.
>
[-- Attachment #2: Type: text/html, Size: 2138 bytes --]
next prev parent reply other threads:[~2013-11-06 9:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 17:07 Jean Krivine
2013-11-05 19:06 ` Lukasz Stafiniak
2013-11-05 19:15 ` Lukasz Stafiniak
2013-11-06 9:19 ` Jean Krivine [this message]
2013-11-06 14:20 ` Richard W.M. Jones
2013-11-06 9:44 ` Francois Berenger
2013-11-06 13:10 ` Gerd Stolpmann
2013-11-06 13:39 ` Jean Krivine
2013-11-06 14:19 ` Richard W.M. Jones
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='CAEQoNCk6wYD5BEMFaq0NCtYsgCVp+Jxbepk=0xwRSBcBh=yyFQ@mail.gmail.com' \
--to=jean.krivine@gmail.com \
--cc=caml-list@inria.fr \
--cc=lukstafi@gmail.com \
/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