cvs commit: fptools/ghc/compiler/stranal DmdAnal.lhs
Marcin 'Qrczak' Kowalczyk
4 Aug 2001 08:39:01 GMT
Thu, 2 Aug 2001 09:31:13 -0700, Simon Marlow <firstname.lastname@example.org> pisze:
> Turn the strictness analyser back on again.
Why ghc still needs huge amounts of memory to compile itself (after
bootstrapping a few times)?
BTW, options like -H16M when the number is smaller than 64 seems to
be ignored. (Such options are used in various places, so I expect
them to break when they become respected.)
AFAIK there is no way to say: use up to 120MB of heap, but don't
allocate such big heap at once, only if needed. This strategy works
automatically until the hard-coded limit of 64MB, but can't be used
above that. IMHO it would be desirable to be able to specify that.
I don't like the fact that programs use much memory, including ghc
itself. Reasonably sized modules (e.g. parsers) can't be compiled
with default compiler settings, especially with optimization turned on.
Hard for ghc are modules with large cases (e.g. parsers generated by
happy) and large constant data structures (they often generate tons
of cruft in interface files - an external entry for each cons cell
and list element!).
__("< Marcin Kowalczyk * email@example.com http://qrczak.ids.net.pl/
^^ SYGNATURA ZASTĘPCZA