From: Han-Wen Nienhuys <hanwen@cs.uu.nl>
Cc: guile-devel@gnu.org
Subject: Re: lazy sweeping.
Date: Mon, 29 Jul 2002 15:06:01 +0200 [thread overview]
Message-ID: <15685.15801.966292.145689@meddo.cs.uu.nl> (raw)
In-Reply-To: <s3sn22lmef.fsf@cmm.kakpryg.net.cmm>
guile@cmm.kakpryg.net writes:
> >> ditto for malloced memory, I guess.
> >
> > Hrm. I'll have to add some more logic then -- we want to be able to
> > completely clean the heap, but not advance the "free mem starts here"
> > pointer. What would be the right behavior: doing a full sweep, or a
> > mark + full sweep? Or maybe just both (first the full sweep, if it
> > doesn't yield enough: the full mark.)
>
> that's what I've meant, yes. however, it's just as optimization, and
> the occurences where it might theoretically matter (system heap
> exhaustion or running out of file descriptors) could probably be
> considered to be rare enough.
>
> as long as you take care to finish the last sweep before marking, you
> should be fine, correctness-wise.
at first I didn't, and it barfed all over the place. That is neat
about working with the GC itself. Any error will blow up grotesquely:
that makes debugging a lot easier.
by-the-by: anyone for a quick hint how to setup a C catch handler from C?
--
Han-Wen Nienhuys | hanwen@cs.uu.nl | http://www.cs.uu.nl/~hanwen/
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-07-29 13:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-28 23:32 lazy sweeping Han-Wen
2002-07-29 0:07 ` Michael Livshin
2002-07-29 9:48 ` Han-Wen Nienhuys
2002-07-29 10:14 ` Michael Livshin
2002-07-29 12:40 ` Han-Wen Nienhuys
2002-07-29 13:00 ` Michael Livshin
2002-07-29 13:06 ` Han-Wen Nienhuys [this message]
2002-07-30 10:09 ` Han-Wen
2002-07-30 12:10 ` Michael Livshin
2002-07-29 4:31 ` Tom Lord
2002-07-29 15:17 ` Han-Wen Nienhuys
2002-07-29 13:16 ` Mikael Djurfeldt
2002-07-29 13:22 ` Han-Wen Nienhuys
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=15685.15801.966292.145689@meddo.cs.uu.nl \
--to=hanwen@cs.uu.nl \
--cc=guile-devel@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).