Peter Tanski wrote:
Simon Marlow wrote:
Joe Buehler wrote:
What is the purpose of RESERVED_C_STACK_BYTES? Are stg routines
expecting a free area of that size at *top* of stack? I need to make
sure
that I have saved the registers at the correct end of the stack frame
created
in StgRun. It is difficult to tell from the existing hppa code what
exactly
was intended.
I had the same problem. I think you can define USE_MINIINTERPRETER (in
rts/Makefile:STANDARD_OPTS or as build.mk:SRC_CC_OPTS) and that will get
around StgCRun/Return. The problem I had was finding out where
everything was supposed to go: I needed to see the actual C compiler
output to make sure things were safe. In the end I gave
up--Windows-native RTS is unregisterised for now because CL cannot
create Explicit Register Variables or use the 'register' storage class
for global variables (both are used in includes/Regs.h).
yikes! Really? I can't see a good reason that you need to force
unregisterised compilation at all. GHC is compiling to native code, the C
compiler isn't involved. If the sticking point is just StgCRun.c, then
code up that little fragment in assembler instead, it's only a handful of
instructions.
Cheers,
Simon
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
