[Git][ghc/ghc][wip/recomp-fixes-9.4] 13 commits: gitlab: Reintroduce Fedora 27 job

Matthew Pickering (@mpickering) gitlab at gitlab.haskell.org
Tue Dec 27 11:16:25 UTC 2022



Matthew Pickering pushed to branch wip/recomp-fixes-9.4 at Glasgow Haskell Compiler / GHC


Commits:
0476f4e6 by Ben Gamari at 2022-12-22T17:09:46-05:00
gitlab: Reintroduce Fedora 27 job

- - - - -
34d1f0fb by Ben Gamari at 2022-12-23T10:30:21-05:00
compiler: Ensure that GHC toolchain is first in search path

As noted in #22561, it is important that GHC's toolchain look
first for its own headers and libraries to ensure that the
system's are not found instead. If this happens things can
break in surprising ways (e.g. see #22561).

(cherry picked from commit 8071efc307ba2df7362ff3b96c898afc61addc21)

- - - - -
cafe7594 by Ben Gamari at 2022-12-23T10:31:33-05:00
docs/relnotes: Mention #22561

- - - - -
bc7b1b26 by Ben Gamari at 2022-12-24T17:42:00-05:00
configure: Set RELEASE=NO

- - - - -
2c095c92 by Matthew Pickering at 2022-12-27T11:16:17+00:00
Fix recompilation checking for multiple home units

The key part of this change is to store a UnitId in the
`UsageHomeModule` and `UsageHomeModuleInterface`.

* Fine-grained dependency tracking is used if the dependency comes from
  any home unit.
* We actually look up the right module when checking whether we need to
  recompile in the `UsageHomeModuleInterface` case.

These scenarios are both checked by the new tests (
multipleHomeUnits_recomp and multipleHomeUnits_recomp_th )

Fixes #22675

- - - - -
150b0385 by Matthew Pickering at 2022-12-27T11:16:17+00:00
Augment target filepath by working directory when checking if module satisfies target

This fixes a spurious warning in -Wmissing-home-modules.

This is a simple oversight where when looking for the target in the
first place we augment the search by the -working-directory flag but
then fail to do so when checking this warning.

Fixes #22676

- - - - -
ca13eb72 by Matthew Pickering at 2022-12-27T11:16:17+00:00
Use NodeKey rather than ModuleName in pruneCache

The `pruneCache` function assumes that the list of `CachedInfo` all have unique `ModuleName`, this is not true:

* In normal compilation, the same module name can appear for a file and it's boot file.
* In multiple home unit compilation the same ModuleName can appear in different units

The fix is to use a `NodeKey` as the actual key for the interfaces which includes `ModuleName`, `IsBoot` and `UnitId`.

Fixes #22677

- - - - -
d4b3a928 by Matthew Pickering at 2022-12-27T11:16:17+00:00
Recompilation checking: Don't try to find artefacts for Interactive & hs-boot combo

In interactive mode we don't produce any linkables for hs-boot files. So
we also need to not going looking for them when we check to see if we
have all the right objects needed for recompilation.

Ticket #22669

- - - - -
8a107014 by Matthew Pickering at 2022-12-27T11:16:17+00:00
Don't write o-boot files in Interactive mode

We should not be producing object files when in interactive mode but we
still produced the dummy o-boot files. These never made it into a
`Linkable` but then confused the recompilation checker.

Fixes #22669

- - - - -
570d5b23 by Matthew Pickering at 2022-12-27T11:16:17+00:00
Improve driver diagnostic messages by including UnitId in message

Currently the driver diagnostics don't give any indication about which unit they correspond to.

For example `-Wmissing-home-modules` can fire multiple times for each different home unit and gives no indication about which unit it's actually reporting about.

Perhaps a longer term fix is to generalise the providence information away from a SrcSpan so that these kind of whole project errors can be reported with an accurate provenance. For now we can just include the `UnitId` in the error message.

Fixes #22678

- - - - -
29f8a1ac by Matthew Pickering at 2022-12-27T11:16:17+00:00
Key ModSummary cache by UnitId as well as FilePath

Multiple units can refer to the same files without any problem. Just
another assumption which needs to be updated when we may have multiple
home units.

However, there is the invariant that within each unit each file only
maps to one module, so as long as we also key the cache by UnitId then
we are all good.

This led to some confusing behaviour in GHCi when reloading,
multipleHomeUnits_shared distils the essence of what can go wrong.

Fixes #22679

- - - - -
8db8f6f4 by Matthew Pickering at 2022-12-27T11:16:17+00:00
Finder: Look in current unit before looking in any home package dependencies

In order to preserve existing behaviour it's important to look within the current component before consideirng a module might come from an external component.

This already happened by accident in `downsweep`, (because roots are used to repopulated the cache) but in the `Finder` the logic was the wrong way around.

Fixes #22680

- - - - -
b415d610 by Matthew Pickering at 2022-12-27T11:16:17+00:00
Debug: Print full NodeKey when pretty printing ModuleGraphNode

This is helpful when debugging multiple component issues.

- - - - -


30 changed files:

- .gitlab/gen_ci.hs
- .gitlab/jobs.yaml
- compiler/GHC/Driver/Errors/Ppr.hs
- compiler/GHC/Driver/Errors/Types.hs
- compiler/GHC/Driver/Main.hs
- compiler/GHC/Driver/Make.hs
- compiler/GHC/Driver/Pipeline/Execute.hs
- compiler/GHC/HsToCore/Usage.hs
- compiler/GHC/Iface/Load.hs
- compiler/GHC/Iface/Recomp.hs
- compiler/GHC/Settings/IO.hs
- compiler/GHC/Unit/Finder.hs
- compiler/GHC/Unit/Module/Deps.hs
- compiler/GHC/Unit/Module/Graph.hs
- configure.ac
- docs/users_guide/9.4.4-notes.rst
- m4/fp_settings.m4
- testsuite/tests/driver/Makefile
- + testsuite/tests/driver/T22669.hs
- + testsuite/tests/driver/T22669.hs-boot
- testsuite/tests/driver/all.T
- + testsuite/tests/driver/multipleHomeUnits/A.hs
- + testsuite/tests/driver/multipleHomeUnits/Dep.hs
- testsuite/tests/driver/multipleHomeUnits/Makefile
- + testsuite/tests/driver/multipleHomeUnits/Recomp.hs
- + testsuite/tests/driver/multipleHomeUnits/RecompTH.hs
- testsuite/tests/driver/multipleHomeUnits/all.T
- + testsuite/tests/driver/multipleHomeUnits/multipleHomeUnits_import_order.stderr
- + testsuite/tests/driver/multipleHomeUnits/multipleHomeUnits_recomp.stdout
- + testsuite/tests/driver/multipleHomeUnits/multipleHomeUnits_recomp_th.stdout


The diff was not included because it is too large.


View it on GitLab: https://gitlab.haskell.org/ghc/ghc/-/compare/4a27a4949511c1303b21453a9ab52abbeef1c114...b415d6107b2db8ccd48ac68c4b63c3cfe9a0ed95

-- 
View it on GitLab: https://gitlab.haskell.org/ghc/ghc/-/compare/4a27a4949511c1303b21453a9ab52abbeef1c114...b415d6107b2db8ccd48ac68c4b63c3cfe9a0ed95
You're receiving this email because of your account on gitlab.haskell.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-commits/attachments/20221227/1c1765e2/attachment-0001.html>


More information about the ghc-commits mailing list