Peter Tanski wrote: > would grow) it moves up the stack (addl back up into the stack). This > would save memory (RESERVED_C_STACK_BYTES is defined in Constants.h as > (2048 * SIZEOF_LONG)) but only if it is already known that the stack > space above was used by the GHC program. The point being that knowing > what is controlling the stack you are using--GHC or the C > compiler--would help. Am I way off here?
I got the hppa registerised port running. 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. -- Joe Buehler _______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
