> | I never found a satisfactory answer. On IA64 we just hope that ghc
> | generates C code that does not turn into object code that uses too many
> | variables. We tried playing with gcc flags to make it only use the
> | limited number of registers but could not make it work. The only
> | workarounds I know of are to use less aggressive optimisation, both in
> | ghc and gcc, so try with -optc-O rather than -optc-O2 and try -O0 rather
> | than -O.
> |
> | Duncan