From: Matthias Koeppe <mkoeppe@mail.math.uni-magdeburg.de>
Cc: guile-user@gnu.org
Subject: Re: GC ??
Date: Wed, 03 Dec 2003 11:44:22 +0100 [thread overview]
Message-ID: <uw5k75exjsp.fsf@merkur.math.uni-magdeburg.de> (raw)
In-Reply-To: <OF8E656C15.79825398-ON65256DF1.002803DB-65256DF1.00284EC2@ad.skynet> (dv praveen's message of "Wed, 3 Dec 2003 12:50:15 +0530")
dv.praveen@skyworksinc.com writes:
> My question is still unasnwered. Shouldn't the
> garbage collector attend all the globals and the
> recurse on the internal scm objects during the
> trace operation?
The garbage collector only scans the Scheme heap and the C/Scheme
stack, but neither the global C data nor the C heap. I think the
rationale is that it would be very expensive to scan these memory
regions because they may be very large and contain only very few
Scheme objects. Moreover, they may contain many "false pointers" that
look like Scheme objects, which would make garbage collection
ineffective.
Therefore one needs to manually protect Scheme objects that are stored
in these memory regions from being garbage collected.
--
Matthias Koeppe -- http://www.math.uni-magdeburg.de/~mkoeppe
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2003-12-03 10:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 7:20 GC ?? dv.praveen
2003-12-03 10:44 ` Matthias Koeppe [this message]
2003-12-03 12:45 ` Stephen Compall
2003-12-03 15:55 ` Ludovic Courtès
2003-12-03 17:04 ` Matthias Koeppe
-- strict thread matches above, loose matches on Subject: below --
2003-12-03 12:58 dv.praveen
2003-12-03 17:08 ` Matthias Koeppe
[not found] <200312030720.hB37Khv7022012@smtp1.urprovider.com>
2003-12-03 11:25 ` Andreas Rottmann
2003-12-02 11:59 dv.praveen
2003-12-02 14:32 ` Andreas Rottmann
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uw5k75exjsp.fsf@merkur.math.uni-magdeburg.de \
--to=mkoeppe@mail.math.uni-magdeburg.de \
--cc=guile-user@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).