[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: |
Thu, 22 May 2014 18:49:13 +0300 |
> Date: Wed, 21 May 2014 20:12:45 -0700
> From: Daniel Colascione <address@hidden>
> CC: address@hidden
>
> What about cleaning the stack (memset from the top to the high water
> mark) every once in a while?
I believe this would be as tedious and expensive as clearing the stack
on entry to a function. It also requires ugly OS-dependent
code/assembly. Also, when would you exactly do that, except where we
call GC?
I think what I suggested a few minutes ago is better, and seems to
solve the problem at hand.
- Re: GC and stack marking, (continued)
Re: GC and stack marking, Barry OReilly, 2014/05/21
- Re: GC and stack marking, Eli Zaretskii, 2014/05/21
- Re: GC and stack marking, Barry OReilly, 2014/05/21
- Re: GC and stack marking, Eli Zaretskii, 2014/05/21
- Re: GC and stack marking, Daniel Colascione, 2014/05/21
- Re: GC and stack marking, David Kastrup, 2014/05/22
- Re: GC and stack marking, Stefan Monnier, 2014/05/22
- Re: GC and stack marking,
Eli Zaretskii <=
Re: GC and stack marking, Barry OReilly, 2014/05/22
Re: GC and stack marking, Eli Zaretskii, 2014/05/22