GitLab

This patch makes the Data.Typeable.Typeable class work with arguments of any
kind. In particular, this removes the Typeable1..7 class hierarchy, greatly
simplyfing the whole Typeable story. Also added is the AutoDeriveTypeable
language extension, which will automatically derive Typeable for all types and
classes declared in that module. Since there is now no good reason to give
handwritten instances of the Typeable class, those are ignored (for backwards
compatibility), and a warning is emitted.

The old, kind-* Typeable class is now called OldTypeable, and lives in the
Data.OldTypeable module. It is deprecated, and should be removed in some future
version of GHC.

ioManagerCapabilitiesChanged now queries getNumCapabilities for the current number of enabled capabilities.

This enables the IO manager to change the number of IO loops it uses (usually one per capability).

Removed checks for empty lists for case expressions and lambda-case.
If -XEmptyCase is not enabled, compilation still fails (appropriately)
in the renamer.

Had to remove dead code from TrieMap to pass the validator.

Thanks to @PHO on #7498 for pointing this out.

* phonohawk/ticket-7498:
  Fix bugs in PPC.Instr.allocMoreStack (#7498)

This patch is ported from #7510, which fixes the same bug in the x86 nativeGen.

It uglifies the code a tiny bit but it's nice to know exactly what
you're using.
Signed-off-by: Austin Seipp <aseipp@pobox.com>

It slipped in on accident.
Signed-off-by: Austin Seipp <aseipp@pobox.com>

Clang gives a big fat warning that there's no return value for the
statement, since the prototype defaults to 'int'.
Signed-off-by: Austin Seipp <aseipp@pobox.com>

Signed-off-by: Austin Seipp <aseipp@pobox.com>

It now checks that the directory exists before complaining that it's
old.

The specialiser needs to know if a dictionay has some structure,
so that it can decide whether to specialise a function. Eg
 (A)    let d = $dfblah d1
        in ....(f d)....

 (B)    \d. ....(f d)....

In (A) it's probably worth specialising f; in (B) it isn't.
Previously we were relying on d's unfolding, but the specialiser
does cloning as it goes, which discards the unfolding. So we
were simply discarding all specialisations for functions with
local dictionary bindings!  This bug seems to have been there
for a long time.

This is what originally caused Trac #5113.  Then we went through a phase
where local bindings were not generalised, and that meant there was
no locally overloaded f to specialise; so the performance problem appeared
to be fixed.  But now we are generalising local bindings again, so it
re-appeared.

This patch fixes the original problem.

version 2.59 seems to be incompatible with our updated macros.
If somebody insists on 2.59 (which is almost 10 years old) I'll
have to hunt down the reason for the recent (Dec 2012?) breakage.

Note that I did not check with 2.60 (I have 2.65), so that one
may still be problematic.

Fixes the following crash:

  internal error: threadStackUnderflow: not enough space for return values

when using STM.

document them.

MSDN says of Sleep:
    If dwMilliseconds is greater than one tick but less than two, the
    wait can be anywhere between one and two ticks, and so on.
so we need to add (milliseconds-per-tick - 1) to the amount of time we
sleep for.

Conflicts:
	compiler/rename/RnSource.lhs
	compiler/simplCore/OccurAnal.lhs
	compiler/vectorise/Vectorise/Exp.hs

NB: Merging instead of rebasing for a change. During rebase Git got confused due to the lack of the submodules in my quite old fork.

We were using "us" elsewhere, so this was inconsistent.