GitLab

Also, temporarely disable that warning for validate builds, until we
finish fixing them all.

This patch makes
  fiExpr (AnnLam ...)
  noFloatIntoExpr (AnnLam ...)
line up with each other.  Previously they behaved inconsistently
with bad results.

The details are in Trac #7088.    There's a regression test
in simplCore/should_compile/T7088

The main thing is that we now keep unsolved Derived constraints in the
wc_flats of a WantedConstraints, rather than discarding them each time.
This actually fixes a poential (admittedly obscure) bug, when we currently
discard a superclass constraint, and may never re-generate it, and may
thereby miss a functional dependency.

Instead, reportErrors filters out Derived constraints that we don't want
to report.

The other changes are all small refactorings following our walk-through.

This warning was suggested by Trac #6082, where we had
a library RULE that failed to fire because its function
was inlined too soon.

       _ = e

Thse are used in a few libraries, either to add type constraints
via a signature, or to mention some variables that are only
otherwise mentioned in one #ifdef branch

See Note [Calculate unfolding guidance on the non-occ-anal'd expression]
This makes a big difference to residency (530M vs over 800M when compiling
Cabal).

This fixes the majority of the regression in Trac #6104

I suspect I have done the wrong thing; I hope someone can improve.

Fixes Trac #7085

parts of WantedConstraints, and other small refactorings.

We don't need them any more, now that we have DynFlags inside SDoc

	new file:   ghc/ghc-cross.wrapper
	new file:   includes/mkDerivedConstants.cross.awk
	new file:   includes/mkSizeMacros.cross.awk
	new file:   rules/cross-compiling.mk

These are expected to sit quietly in the tree until
the rest of the machinery matures on an (upcoming)
branch. Reviews will begin to make sense as soon as
that has happened. Anyway, comments are welcome. See
<http://www.haskell.org/pipermail/cvs-ghc/2012-July/074456.html>
for background.

Disclaimer: these source files are not (yet) up to the
            quality standards set by the rest of the tree.

Cleanups, move-arounds and rewrites (i.e. .awk -> .hs), as
well as additional comments and documentation will happen
as soon as the basic functionality of a cross-compiler is
working reliably.

The only difference between SevDump and SevOutput in defaultLogAction is
an extra blank line, so we don't need a separate hPrintDump function.

Also make -ddump-to-file consistent with the stdout version, by avoiding
to add the extra empty line when dumping rules.