On Mon, Mar 16, 2009 at 1:34 AM, Juho Snellman <jsnell@iki.fi> wrote:
Jean-Claude Beaudoin <jean.claude.beaudoin@gmail.com> writes:
> Does SBCL indeed do any such manipulation to the stack of the
> initial thread?  

Yes, it switches stacks in call_into_lisp_first_time.

 

Could you describe the role that this stack switch plays in SBCL?
I am even more puzzled when I see in the source code that the
Win32 port seems to do away with it, staying on the original
system allocated stack, and still be a working instance of SBCL.
What does this stack manipulation buy for SBCL?

Cheers,

Jean-Claude Beaudoin