From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: doco scm_remember_upto_1
Date: Thu, 22 May 2003 10:21:21 -0500 [thread overview]
Message-ID: <87r86rqa6m.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <lj1xyrl3l3.fsf@troy.dt.e-technik.uni-dortmund.de> (Marius Vollmer's message of "22 May 2003 11:42:48 +0200")
Marius Vollmer <marius.vollmer@uni-dortmund.de> writes:
> Yes, that would be an improvement. As Rob say, you are safe right
> now, but having one scm_remember_upto_here too many does not hurt.
I presume they affect the available optimizations, but I suppose the
effect of "too many" would still be likely to be minimal...
>> Marius may need to comment here, but I was under the impression that
>> at the moment we haven't been trying to write all the code to
>> accomodate a C-side preemptive GC.
>
> Yes, but I'd say that for new code we could be more careful with the
> scm_remembers.
Hmm. So what level of preemption are we planning to support, or
rather for what kind of preemption should we be coding defensively? I
ask because it's been my experience that trying to write libraries to
support fine grained preemption can sometimes be expensive, both with
respect to coding and runtime.
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-05-22 15:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-21 23:15 doco scm_remember_upto_1 Kevin Ryde
2003-05-22 7:07 ` Rob Browning
2003-05-22 9:42 ` Marius Vollmer
2003-05-22 15:21 ` Rob Browning [this message]
2003-05-24 1:19 ` Kevin Ryde
2003-05-30 0:04 ` Kevin Ryde
2003-06-01 21:41 ` Marius Vollmer
2003-06-11 23:07 ` Kevin Ryde
2003-06-18 23:36 ` Marius Vollmer
2003-06-21 23:02 ` Kevin Ryde
2003-07-27 14:49 ` Marius Vollmer
2003-05-30 13:26 ` Marius Vollmer
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=87r86rqa6m.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--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).