trustworthy module in the same package.

In arrow commands, the function position in an application (HsApp)
is a command, not an expression.

as it maintains 16-byte alignment of the stack pointer (see #5250)

head-normal-form, and similarly for spark#.

  seq#   :: a -> State# s -> (# State# s, a #)
  spark# :: a -> State# s -> (# State# s, a #)

seq# is a version of seq that can be used in a State#-passing
context.  We will use it to implement Control.Exception.evaluate and
thus fix #5129.  Also we have plans to use it to fix #5262.

spark# is to seq# as par is to pseq.  That is, it creates a spark in a
State#-passing context.  We will use spark# and seq# to implement rpar
and rseq respectively in an improved implementation of the Eval monad.

HPC expects the end column of a span to be one less than the
convention used by SrcSpan, and we had lost the "-1", causing various
HPC tests to fail.

calling convention.

Patch based on one by Karel Gardas.

wrong platform by mistake.

The OS X ABI requires the C stack pointer to be 16-byte aligned at a
function call.  As far as I know this is not a requirement on other
x86 ABIs, but it seems that gcc is now generating SSE2 code that
assumes stack alignment (-mincoming-stack-boundary defaults to 4), so
we have to respect 16-byte alignment.

It looks like where x86 assembly is using '@' character,
ARM assembly requires '%' character. This makes a problem in the patch
814edf44 'Force re-linking if
the options have changed (#4451)' which makes linking assembly
file uncompilable on ARM. This patch fixes this.

There was an extra % in the strftime string used in the fingerprint
script to name the output files. It worked fine in python 2.6 on mac
os, but was producing bad file names in python 2.7 on linux.

There are two things in this patch. First, a new feature.
Given     (case x of I# y -> ...)
where 'x' is known to be evaluated, the float-out pass
will float the case outwards towards x's binding.  Of
course this doesn't happen if 'x' is evaluated because
of an enclosing case (becuase then the inner case would
be eliminated) but it *does* happen when x is bound by
a constructor with a strict field.  This happens in DPH.
Trac #4081.

The second change is a significant refactoring of the
way the let-floater works.  Now SetLevels makes a decision
about whether the let (or case) will move, and records
that decision in the FloatSpec flag.  This change makes
the whole caboodle much easier to think about.

An identifier used in an unfolding wasn't getting marked
as an external Id, which caused subsequent chaos.

In understanding and fixing this I refactored some of
chooseExternalIds.  As a side benefit, the order in which
it enumerates the free variables of the IdInfo is now
deterministic (this was a to-do before).

    ghc $ ./configure --build=armv5tel-softfloat-linux-gnueabi \
                      --host=armv5tel-softfloat-linux-gnueabi \
                      --target=armv5tel-softfloat-linux-gnueabi
    checking for gfind... no
    checking for find... /usr/bin/find
    checking for sort... /usr/bin/sort
    checking for GHC version date... inferred 7.1.20110626
    checking for ghc... /usr/bin/ghc
    checking version of ghc... 7.0.4
    checking build system type... armv5tel-softfloat-linux-gnueabi
    checking host system type... armv5tel-softfloat-linux-gnueabi
    checking target system type... armv5tel-softfloat-linux-gnueabi
    Unknown vendor softfloat

Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>

It now matches PACKAGES_STAGE2

Patch by Peter Wortmann!

Based on a patch from David Terei.

Some parts are a little ugly (e.g. defining things that only ASSERTs
use only when DEBUG is defined), so we might want to tweak things a
little.

I've also turned off -Werror for didn't-inline warnings, as we now
get a few such warnings.