Joe Buehler wrote:
... StgRun is supposed to push
registers on the stack and then allocate a further
RESERVED_C_STACK_BYTES
before calling into STG-world. The STG code ends up with
RESERVED_C_STACK_BYTES at top of stack for whatever it wants to use
it for.
That's what I thought but adding to the stack pointer moves it back
up the stack (subtracting from %esp or the equivalent grows the stack
down). What I was missing was a call to __alloca, which I did not
see until I looked at the assembler output from gcc. It makes more
sense now. Thanks for the clarification.
Cheers,
Pete
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
