> ghc-4.02-i386-unknown-linux binary taken from ftp.dcs.gla.ac.uk
>
> says `EVACUATED object entered!'
>
> after ghc -c Bug.hs
I can't repeat this I'm afraid. But it looks like a garbage collector bug,
perhaps the difference in pathname arguments passed to hsc on your machine
is enough to trigger it.
> for the program enclosed below.
>
> Slight modifications of this program (commenting out its small parts)
> cause various effects:
> * hsc: fatal error: evacuate: strange closure type
Haven't seen this one
> * warnings on `static closure ... such and such closure'
> - at the stage of C compilation.
These are harmless (we've looked into it).
> * compiler may take an unnaturally large piece of memory for this
> module and does not seem to finish compilation
Bug.hs compiled with a maximum residency of 8M here.
I'll try to track this one down, but I haven't got any examples which
display the bug, which makes it quite hard...
Cheers,
Simon
