[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gc issues
From: |
Michael Livshin |
Subject: |
Re: gc issues |
Date: |
19 Sep 2000 15:38:43 +0300 |
User-agent: |
Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (20 Minutes to Nikko) |
Mikael Djurfeldt <address@hidden> writes:
> The original idea was, as you said earlier, to stop all threads during
> GC. Furthermore, the idea was not to stop them at any point but at a
> well-defined point, like SCM_TICK or some other macro which we can
> spread out through the Guile source. (The original idea was to do it
> in SCM_ALLOW_INTS.)
>
> If we do this, we are guaranteed at GC time that newly initialized
> cells are in a consistent state.
and this is fine, except I'm not sure whether this guarantee is really
worth the cost of the additional syncronisation.
it seems to me that this is an issue that is better decided by
implementing both variants and measuring them than by speculating on a
mailing list.
you surely thought much more about the subject than me, though...
--
programmer, n:
A red eyed, mumbling mammal capable of conversing with inanimate
monsters.
- Re: gc issues, (continued)
- Re: gc issues, Jim Blandy, 2000/09/15
- Re: gc issues, Michael Livshin, 2000/09/13
- Re: gc issues, Michael Livshin, 2000/09/14
- Re: gc issues, Jim Blandy, 2000/09/14
- Re: gc issues, Michael Livshin, 2000/09/14
- Re: gc issues, Dirk Herrmann, 2000/09/14
- Re: gc issues, Michael Livshin, 2000/09/16
- Re: gc issues, Dirk Herrmann, 2000/09/19
- Re: gc issues, Michael Livshin, 2000/09/19
- Re: gc issues, Mikael Djurfeldt, 2000/09/19
- Re: gc issues,
Michael Livshin <=
- Re: gc issues, Mikael Djurfeldt, 2000/09/19
- Re: gc issues, Mikael Djurfeldt, 2000/09/19