Re: GC and stack marking

[Daniel Colascione <dancol@dancol.org>]

[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]

On 05/21/2014 07:43 PM, Eli Zaretskii wrote:
>> Date: Wed, 21 May 2014 16:49:22 -0400
>> From: Barry OReilly <gundaetiapo@gmail.com>
>> Cc: emacs-devel@gnu.org
>>
>> Even if we're only talking about the stack variables in the frames that are
>> active during your particular problematic case (and perhaps in the idle
>> Emacs GC case)?
> 
> I thought you were asking about having the compiler generate the code
> to do that, which would then happen everywhere.
> 
> If you propose doing that selectively, I don't know how this would be
> possible, since on the C level you don't have a way of telling how
> much stack is allocated in a given function.
> 
>> Have you already ruled out whether stack_top_variable contributes one of
>> the bytes in your false positive lookup in the mem_node tree?
> 
> Yes.  I looked at all the local variables in that stack frame, and
> their addresses on the stack are different from the one that triggers
> the problem.

What about cleaning the stack (memset from the top to the high water
mark) every once in a while?


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]