> Thanks Simon, though I'm still a tad at sea...
>
>
> > Of course you can! Take a look at the User Guide, section 2.12:
> >
> >
> http://www.dcs.gla.ac.uk/fp/software/ghc/4.01/users_guide/user
> s_guide-2.html
> > #ss2.12
> >
> > (under "RTS options for hackers...")
>
> That says it all, I have a nasty feeling... For a kick off, I can
> find neither RtsFlags.lh or rtsdefs.h files in the 4.01 distribution.
> Some scouting around reveals a RtsFlags.h: does that fit both bills?
Looks like the docs are a tad out of date, sorry about that. Patch follows
(you want ghc/rts/RtsFlags.h and ghc/includes/Rts.h respectively).
*** runtime_control.vsgml 1998/01/30 17:02:54 1.1
--- runtime_control.vsgml 1998/12/14 14:48:13
***************
*** 244,250 ****
example, to set @-H8m -K1m@:
<tscreen><verb>
! #include "rtsdefs.h"
void defaultsHook (void) {
RTSflags.GcFlags.stksSize = 1000002 / sizeof(W_);
RTSflags.GcFlags.heapSize = 8000002 / sizeof(W_);
--- 244,250 ----
example, to set @-H8m -K1m@:
<tscreen><verb>
! #include "Rts.h"
void defaultsHook (void) {
RTSflags.GcFlags.stksSize = 1000002 / sizeof(W_);
RTSflags.GcFlags.heapSize = 8000002 / sizeof(W_);
***************
*** 253,259 ****
Don't use powers of two for heap/stack sizes: these are more likely to
interact badly with direct-mapped caches. The full set of flags is
! defined in @ghc/includes/RtsFlags.lh@ the the GHC source tree.
You can also change the messages printed when the runtime system
``blows up,'' e.g., on stack overflow. The hooks for these are as
--- 253,259 ----
Don't use powers of two for heap/stack sizes: these are more likely to
interact badly with direct-mapped caches. The full set of flags is
! defined in @ghc/rts/RtsFlags.h@ the the GHC source tree.
You can also change the messages printed when the runtime system
``blows up,'' e.g., on stack overflow. The hooks for these are as
--
Simon Marlow
Microsoft Research Ltd., Cambridge, U.K.
