feat: upgrade ghc to 9.0.2-5 (Imported from debian)

GIT_COMMIT_ID

@@ -1 +1 @@
-6cf8f835267581d551ca6695b3b02c34797e2cf4
+6554ff2843d53dddeb875cb145ab892725eac54c

HACKING.md

@@ -8,24 +8,24 @@ information to help you get started right away.
 The GHC Developer's Wiki
 ========================
 
-The home for GHC hackers is our Trac instance, located here:
+The home for GHC hackers is our GitLab instance, located here:
 
-<http://ghc.haskell.org/trac/ghc>
+<https://gitlab.haskell.org/ghc/ghc>
 
-From here, you can file bugs (or look them up,) use the wiki, view the
+From here, you can file bugs (or look them up), use the wiki, view the
 `git` history, among other things. Of particular note is the building
 page, which has the high level overview of the build process and how
 to get the source:
 
-<http://ghc.haskell.org/trac/ghc/wiki/Building>
+<https://gitlab.haskell.org/ghc/ghc/wikis/building>
 
 Contributing patches to GHC in a hurry
 ======================================
 
 Make sure your system has the necessary tools to compile GHC. You can
 find an overview here:
 
-<http://ghc.haskell.org/trac/ghc/wiki/Building/Preparation>
+<https://gitlab.haskell.org/ghc/ghc/wikis/building/preparation>
 
 Next, clone the repository and all the associated libraries:
 
@@ -34,7 +34,7 @@ $ git clone --recursive git@gitlab.haskell.org:ghc/ghc.git
 ```
 
 On Windows, you need an extra repository containing some build tools.
-These can be downloaded for you by configure. This only needs to be done once by running:
+These can be downloaded for you by `configure`. This only needs to be done once by running:
 
 ```
 $ ./configure --enable-tarballs-autodownload
@@ -50,7 +50,7 @@ $ ... double-check mk/build.mk ...
 ```
 
 Now build. The convenient `validate` script will build the tree in a way which
-is both quick to build and consistent with our testsuite,
+is both quick to build and consistent with our testsuite:
 
 ```
 $ ./validate --build-only
@@ -62,35 +62,42 @@ newly built compiler.
 Now, hack on your copy and rebuild (with `make`) as necessary.
 
 Then start by making your commits however you want. When you're done, you can submit
- a pull request on Github for small changes. For larger changes the patch needs to be
- submitted to [Phabricator](https://phabricator.haskell.org/) for code review.
- The GHC Trac Wiki has a good summary for the [overall process](https://ghc.haskell.org/trac/ghc/wiki/WorkingConventions/FixingBugs)
- as well as a guide on 
- [how to use Phabricator/arcanist](https://ghc.haskell.org/trac/ghc/wiki/Phabricator).
+a pull request on Github for small changes. For larger changes the patch needs to be
+submitted to [GitLab](https://gitlab.haskell.org/ghc/ghc/merge_requests) for code review.
+The GHC Wiki has a good summary for the [overall process](https://gitlab.haskell.org/ghc/ghc/wikis/working-conventions/fixing-bugs). One or several reviewers will review your PR, and when they are ok with your changes, they will assign the PR to [Marge Bot](https://gitlab.haskell.org/marge-bot) which will automatically rebase, batch and then merge your PR (assuming the build passes).
 
 
 Useful links:
 =============
 
-An overview of things like using git, the release process, filing bugs
+An overview of things like using Git, the release process, filing bugs
 and more can be located here:
 
-<http://ghc.haskell.org/trac/ghc/wiki/WorkingConventions>
+<https://gitlab.haskell.org/ghc/ghc/wikis/contributing>
 
 You can find our coding conventions for the compiler and RTS here:
 
-<http://ghc.haskell.org/trac/ghc/wiki/Commentary/CodingStyle>
-<http://ghc.haskell.org/trac/ghc/wiki/Commentary/Rts/Conventions>
-
-A high level overview of the bug tracker:
-
-<http://ghc.haskell.org/trac/ghc/wiki/WorkingConventions/BugTracker>
+<https://gitlab.haskell.org/ghc/ghc/wikis/commentary/coding-style>
+<https://gitlab.haskell.org/ghc/ghc/wikis/commentary/rts/conventions>
 
 If you're going to contribute regularly, **learning how to use the
 build system is important** and will save you lots of time. You should
 read over this page carefully:
 
-<http://ghc.haskell.org/trac/ghc/wiki/Building/Using>
+<https://gitlab.haskell.org/ghc/ghc/wikis/building/using>
+
+A web based code explorer for the GHC source code with semantic analysis
+and type information of the GHC sources is available at:
+
+<https://haskell-code-explorer.mfix.io/>
+
+Look for `GHC` in `Package-name`. For example, here is the link to
+[GHC-8.6.5](https://haskell-code-explorer.mfix.io/package/ghc-8.6.5).
+
+If you want to watch issues and code review activities, the following page is a good start:
+
+<https://gitlab.haskell.org/ghc/ghc/activity>
+
 
 How to communicate with us
 ==========================
@@ -126,10 +133,6 @@ undoubtedly also interested in the other mailing lists:
 
  * [glasgow-haskell-users](http://www.haskell.org/mailman/listinfo/glasgow-haskell-users)
    is where developers/users meet.
- * [ghc-tickets](http://www.haskell.org/mailman/listinfo/ghc-tickets)
-   for email from Trac.
- * [ghc-builds](http://www.haskell.org/mailman/listinfo/ghc-builds)
-   for nightly build emails.
  * [ghc-commits](http://www.haskell.org/mailman/listinfo/ghc-commits)
    for commit messages when someone pushes to the repository.
 

INSTALL.md

@@ -18,7 +18,7 @@ XeLaTex (only for PDF output).
 
 Quick start:  the following gives you a default build:
 
-    $ python3 boot
+    $ ./boot
     $ ./configure
     $ make
     $ make install
@@ -31,7 +31,7 @@ Quick start:  the following gives you a default build:
 You can use Make's `-jN` option to parallelize the build. It's generally best
 to set `N` somewhere around the core count of the build machine.
 
-The `python3 boot` step is only necessary if this is a tree checked out from
+The `./boot` step is only necessary if this is a tree checked out from
 git. For source distributions downloaded from GHC's web site, this step has
 already been performed.
 
@@ -43,6 +43,6 @@ It can take a long time.  To customise the build, see the file
 References
 ==========
 
- [1] http://www.haskell.org/ghc/
- [2] http://ghc.haskell.org/trac/ghc/wiki/Building/Preparation
- [3] http://www.haskell.org/haddock/
+ - [1] http://www.haskell.org/ghc/
+ - [2] https://gitlab.haskell.org/ghc/ghc/wikis/building/preparation
+ - [3] http://www.haskell.org/haddock/

MAKEHELP.md

@@ -3,9 +3,9 @@ Quick `make` guide for GHC
 
 For a "Getting Started" guide, see:
 
-  https://ghc.haskell.org/trac/ghc/wiki/Building/QuickStart
-  https://ghc.haskell.org/trac/ghc/wiki/Building/Using
-  https://ghc.haskell.org/trac/ghc/wiki/Building/StandardTargets
+  - https://gitlab.haskell.org/ghc/ghc/wikis/building/quick-start
+  - https://gitlab.haskell.org/ghc/ghc/wikis/building/using
+  - https://gitlab.haskell.org/ghc/ghc/wikis/building/standard-targets
 
 Common commands:
 
@@ -21,18 +21,18 @@ Common commands:
 
     Builds everything in the given directory.
 
-  - cd <dir>; make help
+  - `cd <dir>; make help`
 
     Shows the targets available in <dir>
 
-  - make install
-  - make install-strip
+  - `make install`
+  - `make install-strip`
 
     Installs GHC, libraries and tools under $(prefix). The install-strip
     variant strips executable files while installing them.
 
-  - make sdist
-  - make binary-dist
+  - `make sdist`
+  - `make binary-dist`
 
     Builds a source or binary distribution respectively
 
@@ -42,9 +42,9 @@ Common commands:
     Show the value of make variable <var>. The show! variant works right after
     ./configure (it skips reading package-data.mk files).
 
-  - make clean
-  - make distclean
-  - make maintainer-clean
+  - `make clean`
+  - `make distclean`
+  - `make maintainer-clean`
 
     Various levels of cleaning: "clean" restores the tree to the
     state after "./configure", "distclean" restores to the state
@@ -87,3 +87,10 @@ Using `make` in subdirectories
 
     Bring a particular file up to date, e.g. make dist/build/Module.o
     The name <file> is relative to the current directory
+
+Useful links:
+=============
+
+See also "new Hadrian build system":
+
+  - https://gitlab.haskell.org/ghc/ghc/wikis/building/hadrian

Makefile

@@ -5,8 +5,8 @@
 # This file is part of the GHC build system.
 #
 # To understand how the build system works and how to modify it, see
-#      http://ghc.haskell.org/trac/ghc/wiki/Building/Architecture
-#      http://ghc.haskell.org/trac/ghc/wiki/Building/Modifying
+#      https://gitlab.haskell.org/ghc/ghc/wikis/building/architecture
+#      https://gitlab.haskell.org/ghc/ghc/wikis/building/modifying
 #
 # -----------------------------------------------------------------------------
 
@@ -22,7 +22,7 @@ MAKEFLAGS += --no-builtin-rules
 # -----------------------------------------------------------------------------
 # Sanitize environment
 
-# See Trac #11530
+# See #11530
 export GREP_OPTIONS :=
 
 ifneq "$(filter maintainer-clean distclean clean clean_% help,$(MAKECMDGOALS))" ""
@@ -217,15 +217,15 @@ endif
 # test`, runs each test at least once.
 .PHONY: fasttest
 fasttest:
-	$(MAKE) -C testsuite/tests CLEANUP=1 SUMMARY_FILE=../../testsuite_summary.txt fast
+	$(MAKE) -C testsuite/tests SUMMARY_FILE=../../testsuite_summary.txt fast
 
 .PHONY: test
 test:
-	$(MAKE) -C testsuite/tests CLEANUP=1 SUMMARY_FILE=../../testsuite_summary.txt
+	$(MAKE) -C testsuite/tests SUMMARY_FILE=../../testsuite_summary.txt
 
 .PHONY: slowtest fulltest
 slowtest fulltest:
-	$(MAKE) -C testsuite/tests CLEANUP=1 SUMMARY_FILE=../../testsuite_summary.txt slow
+	$(MAKE) -C testsuite/tests SUMMARY_FILE=../../testsuite_summary.txt slow
 
 .PHONY: fast
 fast: