This changes GHC's treatment of so-called Naughty Quantification
Candidates to issue errors, instead of zapping to Any.

Close #16775.

No new test cases, because existing ones cover this well.

This patch implements overloaded quotation brackets which generalise the
desugaring of all quotation forms in terms of a new minimal interface.

The main change is that a quotation, for example, [e| 5 |], will now
have type `Quote m => m Exp` rather than `Q Exp`. The `Quote` typeclass
contains a single method for generating new names which is used when
desugaring binding structures.

The return type of functions from the `Lift` type class, `lift` and `liftTyped` have
been restricted to `forall m . Quote m => m Exp` rather than returning a
result in a Q monad.

More details about the feature can be read in the GHC proposal.

https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0246-overloaded-bracket.rst

[skip ci]

This brings the pretty-printer for Core in line with how visible
type applications are normally printed: namely, with no whitespace
after the `@` character (i.e., `f @a` instead of `f @ a`). While I'm
in town, I also give the same treatment to type abstractions (i.e.,
`\(@a)` instead of `\(@ a)`) and coercion applications (i.e.,
`f @~x` instead of `f @~ x`).

Fixes #17643.

(cherry picked from commit feb3b955)

Analyzing the call sites for `HsModule` reveals that it is only ever
used with parsed code (i.e., `GhcPs`). This simplifies `HsModule` by
concretizing its `pass` parameter to always be `GhcPs`.

Fixes #17642.

`parallel` is no longer a submodule since 3cb063c8

Otherwise the testsuite driver may not have an up-to-date
baseline.

Refactoring to follow.

Previously we used platform.system() and while this worked fine (e.g.
returned `Windows`, as expected) locally under both msys and MingW64
Python distributions, it inexplicably returned `MINGW64_NT-10.0`
under MingW64 Python on CI. It seems os.name is more reliable so we now
use that instead..

In addition, we prefer the Mingw64 Python distribution on Windows due
to #17483.

Due to #17607.

Also refactor FP_GCC_EXTRA_FLAGS in a few ways:

 * We no longer support compilers which lack support for -fno-builtin
   and -fwrapv so remove the condition on GccVersion
 * These flags are only necessary when using the via-C backend
   so make them conditional on Unregisterised.

Fixes #15742.

I have seen this fail both on x86-64/Debian 9 and armv7/Debian 9

See #17554.

This is to prepare for ghc-bignum which implements some but not all of
gmp functions.

This a small utility function that comes in handy when debugging the
lexer and the parser.

Metric Increase:
    haddock.Cabal

* stgToCmm hook
* cmmToRawCmm hook

These hooks are used by Asterius and could be useful to other clients of
the GHC API.

It increases the Parser dependencies (test CountParserDeps) to 184. It's
still less than 200 which was the initial request (cf
https://mail.haskell.org/pipermail/ghc-devs/2019-September/018122.html)
so I think it's ok to merge this.

When dumping Cmm groups check if the group is empty, to avoid generating
empty sections in dump files like

    ==================== Output Cmm ====================
    []

Also fixes a few bad indentation in the code around changes.

Fixed tests:

* haddockA039: added to all.T
* haddockE004: replaced with T17561 (marked as expect_broken)

New tests:

* haddockA040: deriving clause for a data instance
* haddockA041: haddock and CPP #include

As noted in #17624, it's quite unstable, especially, for some reason, on
i386 and armv7 (something about 32-bit platforms perhaps?).

Metric Increase:
    T1969

This makes it easier to see the true magnitude of fluctuations.
Also do some house-keeping in the argument parsing department.

Previously we would throw away source ticks when the debug level was
non-zero. This is precisely the opposite of what was intended.

Fixes #17616.

Metric Decrease:
    T13056
    T9020
    T9961
    T12425

Lest we fail to rebuild when they change. Fixes #17611.

LLVM does not guarantee any particular semantics when dereferencing null
pointers. Consequently, this test actually passes when built with the
LLVM backend.

As noted in #17606, Docker disallows the get_mempolicy syscall by
default. This caused numerous tests to fail under CI in the `debug_numa`
way. Avoid this by disabling the NUMA probing logic when --debug-numa is
in use, instead setting n_numa_nodes in RtsFlags.c.

Fixes #17606.

Previously things like `+RTS --numa-debug` would enable NUMA support,
despite being an invalid flag.

This was a hack which is no longer necessary now since we introduce a
dedicated entry block for each procedure.