[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GC and stack marking
From: |
Eli Zaretskii |
Subject: |
Re: GC and stack marking |
Date: |
Mon, 19 May 2014 23:03:22 +0300 |
> Date: Mon, 19 May 2014 12:58:34 -0700
> From: Paul Eggert <address@hidden>
> CC: address@hidden, address@hidden
>
> On 05/19/2014 12:14 PM, Eli Zaretskii wrote:
> >> >
> >> >We could have the garbage collector treat purify-flag specially, I
> >> >suppose.
> > I'm not sure I understand the suggestion. Can you elaborate?
>
> I was thinking of a horrible hack where the GC knows about purify-flag,
> so that when you set purify-flag to nil the GCC immediately frees the
> object that purify-flag used to contain, and that we make purify-flag
> special in this way.
Right, but that would only work for that single object. The problem,
by contrast, sounds more general than that.
> Maybe we should get rid of the hash-table purify-flag hack, for
> example.
Maybe, I'm not sure I fully understand its purpose to begin with
(speed of finding objects?). There's a comment by Stefan there saying
something about some savings.
Re: GC and stack marking, Stefan Monnier, 2014/05/20
- Re: GC and stack marking, Eli Zaretskii, 2014/05/20
- Re: GC and stack marking, Stefan Monnier, 2014/05/20
- Re: GC and stack marking, Eli Zaretskii, 2014/05/20
- Re: GC and stack marking, Stefan Monnier, 2014/05/20
- Re: GC and stack marking, Eli Zaretskii, 2014/05/20
- Re: GC and stack marking, Stefan Monnier, 2014/05/20
- Re: GC and stack marking, Eli Zaretskii, 2014/05/21