GitLab

appendStringBuffer was completely bogus - the arguments to copyArray
were the wrong way around, which meant that corruption was very likely
to occur by overwriting the end of the buffer in the first argument.

This definitely fixes #1736.  The other two bugs, #2169 and #2240 are
harder to reproduce, but we can see how they could occur: in the case
of #2169, the options parser is seeing the contents of an old buffer,
and in the case of #2240, appendStringBuffer is corrupting an
interface file in memory, since strng buffers and interface files are
both allocated in the pinned region of memory.

This is an embarassing one: a missing occurs check meant that a type-incorrect
program could leak through.  Yikes!  

(An indirect consequence of extra complexity introduced by boxy types. Sigh.)

Merge to 6.8.4 if we release it.

See Note [Trimming and Template Haskell] in TidyPgm.

Merge to 6.8.4 if we ever release it.

Now we just run make in it at the start of the stage1 build

This is very rough around teh edges at the moment.

It's no longer an extralib

The wiki commentary is now the official description of recompilation
checking.

http://hackage.haskell.org/trac/ghc/wiki/Commentary/Compiler/RecompilationAvoidance

We now get them from the bootstrapping package.conf instead

We were accepting some instances that should have been rejected as
their fundep constraints were violated. e.g. we accepted
    class C a b c | b -> c
    instance C Bool Int Float
    instance C Char Int Double

This goes through the testlog and spits out any sections that contain
"unexpected".

We now build a copy of Cabal and put it in a bootstrapping package.conf.

We also make boot in libraries much earlier in the build process, so we
can use cabal-bin for more stuff in the future.

We don't need to put the program name in it, as that happens automatically

It's -fdph-seq and -fdph-par at the moment, I'll think of a nicer setup later.