RE: GHC Source Build documentation BUG

[Simon Marlow]

 
 while trying to adapt the local bootstrap-from-scratch script 
 that allows
 us to install a somewhat customized GHC onto our systems starting from
 nothing but an installed GCC 2.95, I noticed a bug in the 
 documentation
 accompanying the GHC 6.2 release. On
 http://www.haskell.org/ghc/download_ghc_62.html there is a 
 note stating
   The source distribution needs an installed GHC 4.08.X, 5.X 
 or 6.X to build.
 
 As 4.08.2 is relatively easily bootstrapped using a C 
 compiler, that is
 the base we start off, and thus I figured I could just jump 
 from 4.08.2
 to 6.2. Unfortunately, the compilation itself then states:
   :94: #error GHC = 5.00 is required for bootstrapping GHC
 
 Annoying, that. Especially given that I *checked* if I could jump from
 4.08.2 to 6.2.

Sorry about that.  We lost the ability to bootstrap from 4.08 in 6.2,
and didn't update the docs.

However, as Don pointed out, 6.2 can be bootstrapped from C sources
rather more easily than previous versions, so there's no need to start
from 4.08.  Follow the detailed instructions in the Building Guide, and
you should be fine.

Cheers,
Simon
___
Glasgow-haskell-bugs mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

ghc 6.2 panic or program segfault, depending on flags

[Abraham Egnor]

If I compile my program with -O or -O2, I get the following:

[EMAIL PROTECTED]:~/local/tla/genome/src/test] $ ghc -O -package genome -o test
test.hs
ghc-6.2: panic! (the `impossible' happened, GHC version 6.2):
simplCore/Simplify.lhs:1538: Non-exhaustive patterns in function
bind_args

However, if I add -dcore-lint or remove the -O, the program compiles but
segfaults mid-run.  This bug showed up when I added an Eq a context to a
typeclass definition in some code in the genome package (which itself
compiles fine with or without optimizations).

In addition, if instead of compiling the genome code as a package, I build
it into the test program using ghc --make, the resulting test program
compiles *and* runs without problems, even with -O.

Unfortunately, as with Isaac Jones, I working with Aetion internal code
and can't post it, but I'll happily do any follow-up investigation people
suggest.

Abe

___
Glasgow-haskell-bugs mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs