GitLab

This removes a burden from developers, and I can't remember an
occasion where it would have caught a regression.

It's used by ESC/Haskell.

We use the GHC version number, as the old runghc one doesn't seem very
useful.

My Windows build has started complaining about lacking final newlines,
I'm not entirely sure why.

By default, gcc on OS X will generate SSE instructions, which need
things 16-byte aligned, but we don't 16-byte align things. Thus drop
back to generic i686 compatibility.

If you manually set HSCOLOUR_SRCS=YES then the build will fail if
HsColour wasn't found.

See the Note [Dictionary-like types] in TcType for the full story here
Should only affect programs that use -fdicts-cheap, for
which you'll get better arities

This is a fix to 
  Tue Mar  3 17:42:58 GMT 2009  simonpj@microsoft.com
    * Fix Trac #3066: checking argument types in foreign calls
which I embarassingly got wrong.

Have to be careful when expanding recursive newtypes.

Pls merge.

The problem is that calls to boxyUnify would panic if the types involved
contained type functions. 
It looks like one should wrap these calls with getLIE, although I don't
really know what I am doing here

When checking argument types in a foreign call we were stupidly
looking through foralls.  The fix is easy.

Merge to 6.10.2

The universal type variables of a data constructor are not necessarily
identical to those of its parent type constructor, especially if the
data type is imported.

While I was at it, I did a significant refactoring to make all this
traversal of types more comprehensible, by adding the data type
FFoldType.

Among others:
- Fixed Stg->C-- translation of let-no-escapes -- it's important to use the
  right continuation...
- Fixed infinite recursion in X86 backend (shortcutJump mishandled infinite loops)
- Fixed yet another wrong calling convention -- primops take args only in vanilla regs,
  but they may return results on the stack!
- Removed StackInfo from LGraph and Block -- now in LastCall and CmmZ
- Updated avail-variable and liveness code

We want the internal format to contain LFs only. This makes it easier to work
with the doc strings for clients of the GHC API.

Digits already have a couple of meanings in z-encoding (Z3T is a tuple,
and z123U is a unicode character), so we encode digits as unicode
characters to avoid trying to squeeze in another meaning.

Also removed a little GHC < 6.2 compatibility hack.