Re: Adding the system stack to the GC

I'll take a stab at it. Got a few questions, tho:

a) Can I assume the stack always extends into larger-addressed memory, or
must I handle both cases?

b) What's the largest alignment guaranteed for pointers? Byte-level?

c) Where should this code go, such that it can be replaced for the
OS/platforms which need it differently? resources.c? <platform>.c? Maybe
in resources.c with each <platform>.c calling the generic one in
resources.c (since win32, generic, darwin, etc are all likely to share the
same logic.)

Mike Lambert


Dan Sugalski wrote:

> Date: Fri, 12 Jul 2002 13:05:54 -0400
> From: Dan Sugalski <dan@sidhe.org>
> To: perl6-internals@perl.org
> Subject: Adding the system stack to the GC
>
> Okay, anyone up for this? Should be fairly trivial--take the address
> of an auto variable in runops, store it in the interpreter, take the
> address of *another* auto variable in the GC, and walk the contiguous
> chunk of memory between, looking for valid PMC and Buffer pointers.
>
> Anyone?
> --
>                                          Dan
>
> --------------------------------------"it's like this"-------------------
> Dan Sugalski                          even samurai
> dan@sidhe.org                         have teddy bears and even
>                                        teddy bears get drunk
>
>

• Adding the system stack to the GC by Dan Sugalski
• Re: Adding the system stack to the GC by Mike Lambert
• Re: Adding the system stack to the GC by Dan Sugalski
• Re: Adding the system stack to the GC by Mike Lambert