From: Damien Doligez <Damien.Doligez@inria.fr>
To: caml-list@inria.fr
Subject: Re: Gc Question
Date: Thu, 23 Dec 1999 17:54:04 +0100 [thread overview]
Message-ID: <199912231654.RAA10243@tobago.inria.fr> (raw)
>From: skaller <skaller@maxtal.com.au>
>How does (or should I say 'can') the garbage collector
>tell the difference between a pointer to a structured block,
>and a pointer to something else (outside the caml heap)?
Quite simply, a pointer to outside the heap points outside the heap...
Concretely, this is done by dividing the memory into 4k "pages" and
having a table of bytes to tell for each page whether it is in the
heap.
>unless
>the collector 'knows' where all structure blocks live
>and tests for that. [Conservative collectors often do just that]
>Is this the case??
In short, yes, although the collector doesn't know about each block
individually.
-- Damien
next reply other threads:[~1999-12-23 18:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-23 16:54 Damien Doligez [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-24 17:53 GC question MATTHEW HAMMER
2005-07-05 7:59 dmitry grebeniuk
2001-01-13 2:16 Vitaly Lugovsky
2001-01-23 8:29 ` Xavier Leroy
1999-12-12 23:59 Gc Question skaller
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=199912231654.RAA10243@tobago.inria.fr \
--to=damien.doligez@inria.fr \
--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).