I checked it with CVS repo of 29-mar-99 23:50 EET sources. PrelArr.lhs is compiled OK.
The single bug rests (as before):
------------------------------------------------------------------------
==fptools== make all --unix --no-print-directory -r;
in /f/cygnus/cygwin-b20/home/mvn/fpbuild/ghc/compiler
------------------------------------------------------------------------
...
ghc -cpp -fglasgow-exts -Rghc-timing -I. -IcodeGen -InativeGen -Iparser
-iutils:basicTypes:types:hsSyn:prelude:rename:typecheck:deSugar:coreSyn:specialise:simplCore:stranal:stgSyn:simplStg:codeGen:absCSyn:main:reader:profiling:parser:nativeGen
-recomp -Onot -H45m -fno-warn-incomplete-patterns -c rename/ParseIface.hs -o
rename/ParseIface.o -osuf o
GHC's heap exhausted;
while trying to allocate 0 bytes in a 67108864-byte heap;
use the `-H<size>' option to increase the total heap size.
make[2]: *** [rename/ParseIface.o] Error 1
make[1]: *** [all] Error 1
make: *** [all] Error 1
I followed to Sigbjorn Finne's advise to fight it with -dcore-lint option.
Wishes,
Michael
-----Original Message-----
From: Simon Marlow <[EMAIL PROTECTED]>
To: 'GHC Users Mailing List' <[EMAIL PROTECTED]>
Date: 30 ??????? 1999 ?. 12:21
Subject: RE: Re2: GHC-4.03 heap managemen bug?
>> [ Just a "me too" from Munich :-]
>>
>> "Michael V. Nikolaev" wrote:
>> > [...] PrelArr.lhs compilation permanently completes with error:
>> >
>> > ../../../ghc/driver/ghc -recomp -cpp -fglasgow-exts -fvia-C
>> -Rghc-timing -O -split-objs -odir PrelArr -H8m -c
>> PrelArr.lhs -o PrelArr.o -osuf o
>> > hsc: fatal error: scavenge_stack: weird activation record
>> found on stack.
>> >
>> > make[3]: *** [PrelArr.o] Error 1
>> > make[2]: *** [all] Error 1
>> > make[1]: *** [all] Error 1
>> > make: *** [all] Error 1
>>
>> Alas, I have the same problem with today's ghc-4.03, too. Two days ago
>> everything was fine.
>
>I've tried in vain to reproduce this one - even with an allocation area size
>of 10k doing 21000 GCs. Our nightly 3-stage bootstrap build went through
>without incident last night.
>
>Could you check and see if the current sources still do this?
>
>Cheers,
> Simon
>
