Simon Peyton-Jones wrote:
I ran a full testsuite today. Several bytestring tests are seg-faulting
consistently, when -O is on. See below. Does anyone have a clue about why?
Simon
=====> bytestring001(normal)
cd ./lib/Data.ByteString && '/64playpen/simonpj/builds/HEAD-1/ghc/stage2-inplace/ghc'
-fforce-recomp -dcore-lint -dcmm-lint -Dx86_64_unknown_linux -dno-debug-output -o bytestring001
bytestring001.hs -package bytestring -package QuickCheck >bytestring001.comp.stderr
2>&1
cd ./lib/Data.ByteString && ./bytestring001 </dev/null
>bytestring001.run.stdout 2>bytestring001.run.stderr
=====> bytestring001(optc)
cd ./lib/Data.ByteString && '/64playpen/simonpj/builds/HEAD-1/ghc/stage2-inplace/ghc'
-fforce-recomp -dcore-lint -dcmm-lint -Dx86_64_unknown_linux -dno-debug-output -o bytestring001
bytestring001.hs -O -fvia-C -package bytestring -package QuickCheck
>bytestring001.comp.stderr 2>&1
Compile failed (status 35584) errors were:
/64playpen/simonpj/builds/HEAD-1/ghc/stage2-inplace/ghc: line 2: 14869 Segmentation fault
/64playpen/simonpj/builds/HEAD-1/ghc/stage2-inplace/libexec/ghc
-B/64playpen/simonpj/builds/HEAD-1/inplace-datadir/. -dynload wrapped ${1+"$@"}
This is a segfault from GHC - perhaps you have old interface files in
your bytestring package?
Cheers,
Simon
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
