Matthew Pickering authored 5 years ago and Marge Bot committed 5 years ago

This was removed from make in 077b92fa

Alfredo Di Napoli authored 5 years ago and Marge Bot committed 5 years ago

This commit fixes #16874 by using `fsep` rather than `sep` when pretty
printing long patterns and expressions.

Richard Eisenberg authored 5 years ago and Marge Bot committed 5 years ago

This was requested in #15650.

Ryan Scott authored 5 years ago and Marge Bot committed 5 years ago

This makes the `maintainer-clean` rule in `ghc.mk` slightly more
sophisticated so that it does not remove the version-controlled
file `libraries/ghc-boot/ghc.mk`, which was checked into version
control in commit 24782b89.

Fixes #16953.

Vladislav Zavialov authored 5 years ago and Marge Bot committed 5 years ago

9366e019 introduced a check for orphan roles to fix #8485

6ab5da99 changed the lookup code and made the check redundant.

Now it is removed.

As noted in #16909.

Fixed in #14759.

This requires code loading and therefore can't be run in the profiled
ways when GHC is dynamically linked.

As noted in #11645 and #8862, forking and profiling don't go well
together.

Bumps hpc and unix submodules.

Previously it was not marked as broken in profthreaded

As noted in #16914, the value `True` was used instead of `YES` here, in
contrast to the other boolean fields emitted by `--info`. This confused
the testsuite driver and broke the `ghc_debugged` testsuite predicate.

Otherwise the unique counter starts at 0, causing us to immediately
underflow.

See #16803.

This should help identify a few cases where this is throwing warnings

Otherwise we don't compile the stage2 compiler with DEBUG, meaning the
testsuite isn't checked with assertions.

Metric Increase:
    haddock.Cabal

Sebastian Graf authored 5 years ago and Marge Bot committed 5 years ago

By not building anything in the dynamic way on Windows, where we don't
have a working story for DLLs yet.

Also the ghcid command needs to call bash on the hadrian/ghci.sh script
explicitly as the path gets interpreted differently otherwise.

John Ericson authored 5 years ago and Marge Bot committed 5 years ago

This prepares the way for making Int32# and Word32# the actual size they
claim to be.

Updates binary submodule for (de)serializing the new runtime reps.

Daniel Gröber (dxld) authored 5 years ago and Marge Bot committed 5 years ago

Currently initProfiling gets defined by Profiling.c only if PROFILING is
defined. Otherwise the ProfHeap.c defines it.

This is just needlessly complicated so in this commit I make Profiling and
ProfHeap into properly seperate modules and call their respective init
functions from RtsStartup.c.

Ben Gamari authored 5 years ago and Marge Bot committed 5 years ago

Unfortunately this will require more work; register allocation is
quite broken.

This reverts commit acd79558.

Artem Pelenitsyn authored 5 years ago and Marge Bot committed 5 years ago

Hadrian used to have a separate flag --progress-colour to control
colored output during the build. After introduction of a Shake flag
with similar purpose Hadrian's flag became redundant. The commit removes
--progress-colour and switches to Shake's flag. The only difference
between the two is that Hadrian has special default mode when it tries
to determine if the terminal support colored output. The user can
override it using (Shake's) `--[no-]color`.

See also the discussion at #16592

Niklas Hambüchen authored 5 years ago and Marge Bot committed 5 years ago

Found by @lehins.

John Ericson authored 5 years ago and Marge Bot committed 5 years ago

These are unexploded minds as far as the linter is concerned. I don't
want to hit in my MRs by mistake!

I did this with `sed`, and then rolled back some changes in the docs,
config.guess, and the linter itself.

John Ericson authored 5 years ago and Marge Bot committed 5 years ago

 - docs which document the lint and need to contain the unutterable

 - vendored code which is outside our purview

John Ericson authored 5 years ago and Marge Bot committed 5 years ago

Instead following @angerman's suggestion put them in the config file.
Maybe we could re-key llvm-targets someday, but this is good for now.