From: Mikael Djurfeldt <djurfeldt@nada.kth.se>
Cc: guile-devel@gnu.org
Subject: Re: scm_remember_upto_here asm volatile
Date: Sun, 01 Jun 2003 21:29:28 +0200 [thread overview]
Message-ID: <xy7k7c5d2av.fsf@nada.kth.se> (raw)
In-Reply-To: <87znl1ocrn.fsf@zagadka.ping.de> (Marius Vollmer's message of "01 Jun 2003 20:47:56 +0200")
[Answers given "out-of-context"---can't read the thread right now.]
Marius Vollmer <mvo@zagadka.de> writes:
> And since a GC does only run when all other threads are stopped in a
> safe place, there won't be any GCs at critical moments.
That's right.
> Since this is so convenient, I think we should continue to make this
> guarantee (that a GC wont happen spontanously). Mikael?
Yes, I think this at least gives a simple model for what to expect.
Any other more conservative model might have the advantage to preserve
more freedom to change the GC/thread policy in the future, but will
also need to be much more complex. Besides, we wouldn't know now what
kind of cautions are important to think about...
(Was that answer intelligible? :)
Mikael
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-06-01 19:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-11 22:19 scm_remember_upto_here asm volatile Kevin Ryde
2003-05-17 20:26 ` Marius Vollmer
2003-05-19 0:24 ` Kevin Ryde
2003-06-01 18:47 ` Marius Vollmer
2003-06-01 19:29 ` Mikael Djurfeldt [this message]
2003-08-13 21:09 ` Kevin Ryde
2003-08-23 10:32 ` Dirk Herrmann
2003-08-25 23:48 ` Kevin Ryde
2003-08-27 4:28 ` Dirk Herrmann
2003-08-27 23:49 ` Kevin Ryde
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=xy7k7c5d2av.fsf@nada.kth.se \
--to=djurfeldt@nada.kth.se \
--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).