Cheng Shao pushed to branch wip/T25821 at Glasgow Haskell Compiler / GHC

Commits:

• 652cba7e
  by Peng Fan at 2025-05-14T04:24:35-04:00

  Add LoongArch NCG support
  
  Not supported before.
  

• c01f4374
  by Lin Runze at 2025-05-14T04:24:35-04:00

  ci: Add LoongArch64 cross-compile CI for testing
  

• ce6cf240
  by Ben Gamari at 2025-05-14T04:25:18-04:00

  rts/linker: Don't fail due to RTLD_NOW
  
  In !12264 we started using the NativeObj machinery introduced some time
  ago for loading of shared objects. One of the side-effects of this
  change is shared objects are now loaded eagerly (i.e. with `RTLD_NOW`).
  This is needed by NativeObj to ensure full visibility of the mappings of
  the loaded object, which is in turn needed for safe shared object
  unloading.
  
  Unfortunately, this change subtly regressed, causing compilation
  failures in some programs. Specifically, shared objects which refer to
  undefined symbols (e.g. which may be usually provided by either the
  executable image or libraries loaded via `dlopen`) will fail to load
  with eager binding. This is problematic as GHC loads all package
  dependencies while, e.g., evaluating TemplateHaskell splices. This
  results in compilation failures in programs depending upon (but not
  using at compile-time) packages with undefined symbol references.
  
  To mitigate this NativeObj now first attempts to load an object via
  eager binding, reverting to lazy binding (and disabling unloading) on
  failure.
  
  See Note [Don't fail due to RTLD_NOW].
  
  Fixes #25943.
  

• 88ee8bb5
  by Sylvain Henry at 2025-05-14T04:26:15-04:00

  Deprecate GHC.JS.Prim.Internal.Build (#23432)
  
  Deprecated as per CLC proposal 329 (https://github.com/haskell/core-libraries-committee/issues/329)
  

• b4ed465b
  by Cheng Shao at 2025-05-14T04:26:57-04:00

  libffi: update to 3.4.8
  
  Bumps libffi submodule.
  

• a3e71296
  by Matthew Pickering at 2025-05-14T04:27:38-04:00

  Remove leftover trace
  

• 2d0ecdc6
  by Cheng Shao at 2025-05-14T04:28:19-04:00

  Revert "ci: re-enable chrome for wasm ghci browser tests"
  
  This reverts commit fee9b351fa5a35d5778d1252789eacaaf5663ae8.
  Unfortunately the chrome test jobs may still timeout on certain
  runners (e.g. OpenCape) for unknown reasons.
  

• 3b3a5dec
  by Ben Gamari at 2025-05-15T16:10:01-04:00

  Don't emit unprintable characters when printing Uniques
  
  When faced with an unprintable tag we now instead print the codepoint
  number.
  
  Fixes #25989.
  
  (cherry picked from commit e832b1fadee66e8d6dd7b019368974756f8f8c46)
  

• e1ef8974
  by Mike Pilgrem at 2025-05-16T16:09:14-04:00

  Translate iff in Haddock documentation into everyday English
  

• fd64667d
  by Vladislav Zavialov at 2025-05-20T03:25:08-04:00

  Allow the 'data' keyword in import/export lists (#25899)
  
  This patch introduces the 'data' namespace specifier in import and
  export lists. The intended use is to import data constructors without
  their parent type constructors, e.g.
  
    import Data.Proxy as D (data Proxy)
    type DP = D.Proxy   -- promoted data constructor
  
  Additionally, it is possible to use 'data' to explicitly qualify any
  data constructors or terms, incl. operators and field selectors
  
    import Prelude (Semigroup(data (<>)))
    import Data.Function (data (&))
    import Data.Monoid (data Dual, data getDual)
  
    x = Dual "Hello" <> Dual "World" & getDual
  
  The implementation mostly builds on top of the existing logic for the
  'type' and 'pattern' namespace specifiers, plus there are a few tweaks
  to how we generate suggestions in error messages.
  

• acc86753
  by Ben Gamari at 2025-05-20T03:25:51-04:00

  compiler: Use field selectors when creating BCOs
  
  This makes it easier to grep for these fields.
  

• 60a55fd7
  by Ben Gamari at 2025-05-20T03:25:51-04:00

  compiler: Clarify BCO size
  
  Previously the semantics and size of StgBCO was a bit unclear.
  Specifically, the `size` field was documented to contain the size of the
  bitmap whereas it was actually the size of the closure *and* bitmap.
  Additionally, it was not as clear as it could be that the bitmap was a
  full StgLargeBitmap with its own `size` field.
  

• ac9fb269
  by Simon Peyton Jones at 2025-05-20T09:19:04-04:00

  Track rewriter sets more accurately in constraint solving
  
  This MR addresses #26003, by refactoring the arcane
  intricacies of Note [Equalities with incompatible kinds].
  NB: now retitled to
      Note [Equalities with heterogeneous kinds].
  and the main Note for this MR.
  
  In particular:
  
  * Abandon invariant (COERCION-HOLE) in Note [Unification preconditions] in
    GHC.Tc.Utils.Unify.
  
  * Abandon invariant (TyEq:CH)) in Note [Canonical equalities] in
    GHC.Tc.Types.Constraint.
  
  * Instead: add invariant (REWRITERS) to Note [Unification preconditions]:
    unify only if the constraint has an empty rewriter set.
  
  Implementation:
  
  * In canEqCanLHSFinish_try_unification, skip trying unification if there is a
    non-empty rewriter set.
  
  * To do this, make sure the rewriter set is zonked; do so in selectNextWorkItem,
    which also deals with prioritisation.
  
  * When a coercion hole is filled, kick out inert equalities that have that hole
    as a rewriter.  It might now be unlocked and available to unify.
  
  * Remove the ad-hoc `ch_hetero_kind` field of `CoercionHole`.
  
  * In `selectNextWorkItem`, priorities equalities withan empty rewriter set.
  
  * Defaulting: see (DE6) in Note [Defaulting equalities]
    and Note [Limited defaulting in the ambiguity check]
  
  * Concreteness checks: there is some extra faff to try to get decent
    error messages when the FRR (representation-polymorphism) checks
    fail. In partiular, add a "When unifying..." explanation when the
    representation-polymorphism check arose from another constraint.
  

• 86406f48
  by Cheng Shao at 2025-05-20T09:19:47-04:00

  rts: fix rts_clearMemory logic when sanity checks are enabled
  
  This commit fixes an RTS assertion failure when invoking
  rts_clearMemory with +RTS -DS. -DS implies -DZ which asserts that free
  blocks contain 0xaa as the designated garbage value. Also adds the
  sanity way to rts_clearMemory test to prevent future regression.
  Closes #26011.
  
  ChatGPT Codex automatically diagnosed the issue and proposed the
  initial patch in a single shot, given a GHC checkout and the following
  prompt:
  
  ---
  
  Someone is reporting the following error when attempting to use `rts_clearMemory` with the RTS option `-DS`:
  
  ```
  test.wasm: internal error: ASSERTION FAILED: file rts/sm/Storage.c, line 1216
  
      (GHC version 9.12.2.20250327 for wasm32_unknown_wasi)
      Please report this as a GHC bug:  https://www.haskell.org/ghc/reportabug
  ```
  
  What's the culprit? How do I look into this issue?
  
  ---
  
  I manually reviewed & revised the patch, tested and submitted it.
  

• 7147370b
  by Cheng Shao at 2025-05-20T17:22:19-04:00

  compiler: do not allocate strings in bytecode assembler
  
  This patch refactors the compiler to avoid allocating iserv buffers
  for BCONPtrStr at assemble-time. Now BCONPtrStr ByteStrings are
  recorded as a part of CompiledByteCode, and actual allocation only
  happens at link-time. This refactoring is necessary for adding
  bytecode serialization functionality, as explained by the revised
  comments in this commit.
  

• a67db612
  by Cheng Shao at 2025-05-20T17:22:19-04:00

  compiler: make bc_strs serializable
  
  This commit makes the bc_strs field in CompiledByteCode serializable;
  similar to previous commit, we preserve the ByteString directly and
  defer the actual allocation to link-time, as mentioned in updated
  comment.
  

• 5faf34ef
  by Cheng Shao at 2025-05-20T17:22:19-04:00

  compiler: make bc_itbls serializable
  
  This commit makes bc_itbls in CompiledByteCode serializable. A
  dedicated ConInfoTable datatype has been added in ghci which is the
  recipe for dynamically making a datacon's info table, containing the
  payload of the MkConInfoTable iserv message.
  

• 2abaf8c1
  by Cheng Shao at 2025-05-20T17:22:19-04:00

  compiler: remove FFIInfo bookkeeping in BCO
  
  This commit removes the bc_ffis field from CompiledByteCode
  completely, as well as all the related bookkeeping logic in
  GHC.StgToByteCode. bc_ffis is actually *unused* in the rest of GHC
  codebase! It is merely a list of FFIInfo, which is just a remote
  pointer of the libffi ffi_cif struct; once we allocate the ffi_cif
  struct and put its pointer in a CCALL instruction, we'll never free it
  anyway. So there is no point of bookkeeping.
  

• adb9e4d2
  by Cheng Shao at 2025-05-20T17:22:19-04:00

  compiler: make FFIInfo serializable in BCO
  
  This commit makes all the FFIInfo needed in CCALL instructions
  serializable. Previously, when doing STG to BCO lowering, we would
  allocate a libffi ffi_cif struct and keep its remote pointer as
  FFIInfo; but actually we can just keep the type signature as FFIInfo
  and defer the actual allocation to link-time.
  

• 200f401b
  by Cheng Shao at 2025-05-20T17:22:19-04:00

  ghci: remove redundant NewBreakModule message
  
  This commit removes the redundant NewBreakModule message from ghci: it
  just allocates two strings! This functionality can be implemented with
  existing MallocStrings in one iserv call.
  

• ddaadca6
  by Cheng Shao at 2025-05-20T17:22:19-04:00

  compiler: make breakpoint module name and unit id serializable
  
  This commit makes breakpoint module name and unit id serializable, in
  BRK_FUN instructions as well as ModBreaks. We can simply keep the
  module name and unit ids, and defer the buffer allocation to link
  time.
  

• a0fde202
  by Cheng Shao at 2025-05-20T17:22:19-04:00

  compiler: remove unused newModule
  
  This commit removes the now unused newModule function from GHC.
  

• 68c8f140
  by Cheng Shao at 2025-05-20T17:22:19-04:00

  compiler: add BCONPtrFS for interned top level string literals in BCO
  
  This commit adds BCONPtrFS as a BCO non-pointer literal kind, which
  has the same semantics of BCONPtrStr, except it contains a FastString
  instead of a ByteString. By using BCONPtrFS to represent top level
  string literals that are already FastString in the compilation
  pipeline, we enjoy the FastString interning logic and avoid allocating
  a bunch of redundant ByteStrings for the same FastStrings, especially
  when we lower the BRK_FUN instruction.
  

• f2b532bc
  by Peng Fan at 2025-05-20T17:23:15-04:00

  hadrian: enable GHCi for loongarch64
  

• 8ded2330
  by kwxm at 2025-05-20T17:24:07-04:00

  Fix bugs in `integerRecipMod` and `integerPowMod`
  
  This fixes #26017.
  
    * `integerRecipMod x 1` now returns `(# 1 | #)` for all x; previously it
      incorrectly returned `(# | () #)`, indicating failure.
  
    * `integerPowMod 0 e m` now returns `(# | () #)` for e<0 and m>1, indicating
      failure; previously it incorrectly returned `(# 0 | #)`.
  

• c9abb87c
  by Andreas Klebinger at 2025-05-20T17:24:50-04:00

  Specialise: Don't float out constraint components.
  
  It was fairly complex to do so and it doesn't seem to improve anything.
  Nofib allocations were unaffected as well.
  
  See also Historical Note [Floating dictionaries out of cases]
  

• 202b201c
  by Andreas Klebinger at 2025-05-21T10:16:14-04:00

  Interpreter: Add limited support for direct primop evaluation.
  
  This commit adds support for a number of primops directly
  to the interpreter. This avoids the indirection of going
  through the primop wrapper for those primops speeding interpretation
  of optimized code up massively.
  
  Code involving IntSet runs about 25% faster with optimized core and these
  changes. For core without breakpoints it's even more pronouced and I
  saw reductions in runtime by up to 50%.
  
  Running GHC itself in the interpreter was sped up by ~15% through this
  change.
  
  Additionally this comment does a few other related changes:
  
  testsuite:
  * Run foundation test in ghci and ghci-opt ways to test these
  primops.
  * Vastly expand the foundation test to cover all basic primops
    by comparing result with the result of calling the wrapper.
  
  Interpreter:
  * When pushing arguments for interpreted primops extend each argument to
    at least word with when pushing. This avoids some issues with big
    endian. We can revisit this if it causes performance issues.
  * Restructure the stack chunk check logic. There are now macros for
    read accesses which might cross stack chunk boundries and macros which
    omit the checks which are used when we statically know we access an
    address in the current stack chunk.
  

• 67a177b4
  by sheaf at 2025-05-21T10:17:04-04:00

  QuickLook: do a shape test before unifying
  
  This commit ensures we do a shape test before unifying. This ensures
  we don't try to unify a TyVarTv with a non-tyvar, e.g.
  
    alpha[tyv] := Int
  
  On the way, we refactor simpleUnifyCheck:
  
    1. Move the checkTopShape check into simpleUnifyCheck
    2. Refactors simpleUnifyCheck to return a value of the new type
       SimpleUnifyResult type. Now, simpleUnifyCheck returns "can unify",
       "cannot unify" or "dunno" (with "cannot unify" being the new result
       it can return). Now:
         - touchabilityTest is included; it it fails we return "cannot unify"
         - checkTopShape now returns "cannot unify" instead of "dunno" upon failure
    3. Move the call to simpleUnifyCheck out of checkTouchableTyVarEq.
       After that, checkTouchableTyVarEq becames a simple call to
       checkTyEqRhs, so we inline it.
  
  This allows the logic in canEqCanLHSFinish_try_unification to be simplified.
  In particular, we now avoid calling 'checkTopShape' twice.
  Two further changes suggested by Simon were also implemented:
  
    - In canEqCanLHSFinish, if checkTyEqRhs returns PuFail with
      'do_not_prevent_rewriting', we now **continue with this constraint**.
      This allows us to use the constraint for rewriting.
  
    - checkTyEqRhs now has a top-level check to avoid flattening a tyfam app
      in a top-level equality of the form alpha ~ F tys, as this is
      going around in circles. This simplifies the implementation without
      any change in behaviour.
  
  Fixes #25950
  Fixes #26030
  

• 4020972c
  by sheaf at 2025-05-21T10:17:04-04:00

  FixedRuntimeRepError: omit unhelpful explanation
  
  This commit tweaks the FixedRuntimeRepError case of pprTcSolverReportMsg,
  to avoid including an explanation which refers to a type variable that
  appears nowhere else.
  
  For example, the old error message could look like the following:
  
    The pattern binding does not have a fixed runtime representation.
    Its type is:
      T :: TYPE R
    Cannot unify ‘R’ with the type variable ‘c0’
    because the former is not a concrete ‘RuntimeRep’.
  
  With this commit, we now omit the last two lines, because the concrete
  type variable (here 'c0') does not appear in the type displayed to the
  user (here 'T :: TYPE R').
  

• 6d058a69
  by Andrea Bedini at 2025-05-21T16:00:51-04:00

  Don't fail when ghcversion.h can't be found (#26018)
  
  If ghcversion.h can't be found, don't try to include it. This happens
  when there is no rts package in the package db and when -ghcversion-file
  argument isn't passed.
  
  Co-authored-by: Syvlain Henry <sylvain@haskus.fr>
  

• b1212fbf
  by Vladislav Zavialov at 2025-05-21T16:01:33-04:00

  Implement -Wpattern-namespace-specifier (#25900)
  
  In accordance with GHC Proposal #581 "Namespace-specified imports",
  section 2.3 "Deprecate use of pattern in import/export lists", the
  `pattern` namespace specifier is now deprecated.
  
  Test cases: T25900 T25900_noext
  

• e650ec3e
  by Ben Gamari at 2025-05-23T03:42:46-04:00

  base: Forward port changelog language from 9.12
  

• 94cd9ca4
  by Ben Gamari at 2025-05-23T03:42:46-04:00

  base: Fix RestructuredText-isms in changelog
  

• 7722232c
  by Ben Gamari at 2025-05-23T03:42:46-04:00

  base: Note strictness changes made in 4.16.0.0
  
  Addresses #25886.
  

• 3f4b823c
  by Ben Gamari at 2025-05-23T03:43:28-04:00

  rts/linker: Factor out ProddableBlocks machinery
  

• 6e23fef2
  by Ben Gamari at 2025-05-23T03:43:28-04:00

  rts/linker: Improve efficiency of proddable blocks structure
  
  Previously the linker's "proddable blocks" check relied on a simple
  linked list of spans. This resulted in extremely poor complexity while
  linking objects with lots of small sections (e.g. objects built with
  split sections).
  
  Rework the mechanism to instead use a simple interval set implemented
  via binary search.
  
  Fixes #26009.
  

• ea74860c
  by Ben Gamari at 2025-05-23T03:43:28-04:00

  testsuite: Add simple functional test for ProddableBlockSet
  

• 74c4db46
  by Ben Gamari at 2025-05-23T03:43:28-04:00

  rts/linker/PEi386: Drop check for LOAD_LIBRARY_SEARCH_*_DIRS
  
  The `LOAD_LIBRARY_SEARCH_USER_DIRS` and
  `LOAD_LIBRARY_SEARCH_DEFAULT_DIRS` were introduced in Windows Vista and
  have been available every since. As we no longer support Windows XP we
  can drop this check.
  
  Addresses #26009.
  

• 972d81d6
  by Ben Gamari at 2025-05-23T03:43:28-04:00

  rts/linker/PEi386: Clean up code style
  

• 8a1073a5
  by Ben Gamari at 2025-05-23T03:43:28-04:00

  rts/Hash: Factor out hashBuffer
  
  This is a useful helper which can be used for non-strings as well.
  

• 44f509f2
  by Ben Gamari at 2025-05-23T03:43:28-04:00

  rts/linker/PEi386: Fix incorrect use of break in nested for
  
  Previously the happy path of PEi386 used `break` in a double-`for` loop
  resulting in redundant calls to `LoadLibraryEx`.
  
  Fixes #26052.
  

• bfb12783
  by Ben Gamari at 2025-05-23T03:43:28-04:00

  rts: Correctly mark const arguments
  

• 08469ff8
  by Ben Gamari at 2025-05-23T03:43:28-04:00

  rts/linker/PEi386: Don't repeatedly load DLLs
  
  Previously every DLL-imported symbol would result in a call to
  `LoadLibraryEx`. This ended up constituting over 40% of the runtime of
  `ghc --interactive -e 42` on Windows. Avoid this by maintaining a
  hash-set of loaded DLL names, skipping the call if we have already
  loaded the requested DLL.
  
  Addresses #26009.
  

• 823d1ccf
  by Ben Gamari at 2025-05-23T03:43:28-04:00

  rts/linker: Expand comment describing ProddableBlockSet
  

• e9de9e0b
  by Sylvain Henry at 2025-05-23T15:12:34-04:00

  Remove emptyModBreaks
  
  Remove emptyModBreaks and track the absence of ModBreaks with `Maybe
  ModBreaks`. It avoids testing for null pointers...
  

• 17db44c5
  by Ben Gamari at 2025-05-23T15:13:16-04:00

  base: Expose Backtraces constructor and fields
  
  This was specified in the proposal (CLC #199) yet somehow didn't make it
  into the implementation.
  
  Fixes #26049.
  

• b08c08ae
  by soulomoon at 2025-05-28T01:57:23+08:00

  Refactor handling of imported COMPLETE pragmas
  from the HPT
  
  Previously, we imported COMPLETE pragmas from all modules in the Home
  Package Table (HPT) during type checking. However, since !13675, there
  may be non-below modules in the HPT from the dependency tree that we do
  not want to import COMPLETE pragmas from. This refactor changes the way
  we handle COMPLETE pragmas from the HPT to only import them from modules
  that are "below" the current module in the HPT.
  
  - Add hugCompleteSigsBelow to filter COMPLETE pragmas from "below"
    modules in the HPT, mirroring hugRulesBelow.
  - Move responsibility for calling hugCompleteSigsBelow to tcRnImports,
    storing the result in the new tcg_complete_match_env field of TcGblEnv.
  - Update getCompleteMatchesTcM to use tcg_complete_match_env.
  
  This refactor only affects how COMPLETE pragmas are imported from the
  HPT, imports from external packages are unchanged.
  

• 16014bf8
  by Hécate Kleidukos at 2025-05-28T20:09:34-04:00

  Expose all of Backtraces' internals for ghc-internal
  
  Closes #26049
  

• a0adc30d
  by Ryan Hendrickson at 2025-05-30T14:12:52-04:00

  haddock: Fix links to type operators
  

• 7b64697c
  by Mario Blažević at 2025-05-30T14:13:41-04:00

  Introduce parenBreakableList and use it in ppHsContext
  

• 5f213bff
  by fendor at 2025-06-02T09:16:24+02:00

  Make GHCi commands compatible with multiple home units
  
  === Design
  
  We enable all GHCi features that were previously guarded by the `inMulti`
  option.
  
  GHCi supported multiple home units up to a certain degree for quite a while now.
  The supported feature set was limited, due to a design impasse:
  One of the home units must be "active", e.g., there must be one `HomeUnit`
  whose `UnitId` is "active" which is returned when calling
  
  ```haskell
  do
    hscActiveUnitId <$> getSession
  ```
  
  This makes sense in a GHC session, since you are always compiling a particular
  Module, but it makes less intuitive sense in an interactive session.
  Given an expression to evaluate, we can't easily tell in which "context" the expression
  should be parsed, typechecked and evaluated.
  That's why initially, most of GHCi features, except for `:reload`ing were disabled
  if the GHCi session had more than one `HomeUnitEnv`.
  
  We lift this restriction, enabling all features of GHCi for the multiple home unit case.
  To do this, we fundamentally change the `HomeUnitEnv` graph to be multiple home unit first.
  Instead of differentiating the case were we have a single home unit and multiple,
  we now always set up a multiple home unit session that scales seamlessly to an arbitrary
  amount of home units.
  
  We introduce two new `HomeUnitEnv`s that are always added to the `HomeUnitGraph`.
  They are:
  
  The "interactive-ghci", called the `interactiveGhciUnit`, contains the same
  `DynFlags` that are used by the `InteractiveContext` for interactive evaluation
  of expressions.
  This `HomeUnitEnv` is only used on the prompt of GHCi, so we may refer to it as
  "interactive-prompt" unit.
  See Note [Relation between the `InteractiveContext` and `interactiveGhciUnitId`]
  for discussing its role.
  
  And the "interactive-session"", called `interactiveSessionUnit` or
  `interactiveSessionUnitId`, which is used for loading Scripts into
  GHCi that are not `Target`s of any home unit, via `:load` or `:add`.
  
  Both of these "interactive" home units depend on all other `HomeUnitEnv`s that
  are passed as arguments on the cli.
  Additionally, the "interactive-ghci" unit depends on `interactive-session`.
  
  We always evaluate expressions in the context of the
  "interactive-ghci" session.
  Since "interactive-ghci" depends on all home units, we can import any `Module`
  from the other home units with ease.
  
  As we have a clear `HomeUnitGraph` hierarchy, we can set `interactiveGhciUnitId`
  as the active home unit for the full duration of the GHCi session.
  In GHCi, we always set `interactiveGhciUnitId` to be the currently active home unit.
  
  === Implementation Details
  
  Given this design idea, the implementation is relatively straight
  forward.
  The core insight is that a `ModuleName` is not sufficient to identify a
  `Module` in the `HomeUnitGraph`. Thus, large parts of the PR is simply
  about refactoring usages of `ModuleName` to prefer `Module`, which has a
  `Unit` attached and is unique over the `HomeUnitGraph`.
  
  Consequentially, most usages of `lookupHPT` are likely to be incorrect and have
  been replaced by `lookupHugByModule` which is keyed by a `Module`.
  
  In `GHCi/UI.hs`, we make sure there is only one location where we are
  actually translating `ModuleName` to a `Module`:
  
  * `lookupQualifiedModuleName`
  
  If a `ModuleName` is ambiguous, we detect this and report it to the
  user.
  
  To avoid repeated lookups of `ModuleName`s, we store the `Module` in the
  `InteractiveImport`, which additionally simplifies the interface
  loading.
  
  A subtle detail is that the `DynFlags` of the `InteractiveContext` are
  now stored both in the `HomeUnitGraph` and in the `InteractiveContext`.
  In UI.hs, there are multiple code paths where we are careful to update
  the `DynFlags` in both locations.
  Most importantly in `addToProgramDynFlags`.
  
  ---
  
  There is one metric increase in this commit:
  
  -------------------------
  Metric Increase:
      T4029
  -------------------------
  
  It is an increase from 14.4 MB to 16.1 MB (+11.8%) which sounds like a
  pretty big regression at first.
  However, we argue this increase is solely caused by using more data
  structures for managing multiple home units in the GHCi session.
  In particular, due to the design decision of using three home units, the
  base memory usage increases... but by how much?
  
  A big contributor is the `UnitState`, of which we have three now, which
  on its own 260 KB per instance. That makes an additional memory usage of
  520 KB, already explaining a third of the overall memory usage increase.
  Then we store more elements in the `HomeUnitGraph`, we have more
  `HomeUnitEnv` entries, etc...
  
  While we didn't chase down each byte, we looked at the memory usage over time
  for both `-hi` and `-hT` profiles and can say with confidence while the memory
  usage increased slightly, we did not introduce any space leak, as
  the graph looks almost identical as the memory usage graph of GHC HEAD.
  
  ---
  
  Adds testcases for GHCi multiple home units session
  
  * Test truly multiple home unit sessions, testing reload logic and code evaluation.
  * Test that GHCi commands such as `:all-types`, `:browse`, etc., work
  * Object code reloading for home modules
  * GHCi debugger multiple home units session
  

• de603d01
  by fendor at 2025-06-02T09:16:24+02:00

  Update "loading compiled code" GHCi documentation
  
  To use object code in GHCi, the module needs to be compiled for use in
  GHCi. To do that, users need to compile their modules with:
  
  * `-dynamic`
  * `-this-unit-id interactive-session`
  
  Otherwise, the interface files will not match.
  

• b255a8ca
  by Vladislav Zavialov at 2025-06-02T16:00:12-04:00

  docs: Fix code example for NoListTuplePuns
  
  Without the fix, the example produces an error:
  
    Test.hs:11:3: error: [GHC-45219]
        • Data constructor ‘Tuple’ returns type ‘Tuple2 a b’
            instead of an instance of its parent type ‘Tuple a’
        • In the definition of data constructor ‘Tuple’
          In the data type declaration for ‘Tuple’
  
  Fortunately, a one line change makes it compile.
  

• 6558467c
  by Ryan Hendrickson at 2025-06-06T05:46:58-04:00

  haddock: Parse math even after ordinary characters
  
  Fixes a bug where math sections were not recognized if preceded by a
  character that isn't special (like space or a markup character).
  

• 265d0024
  by ARATA Mizuki at 2025-06-06T05:47:48-04:00

  AArch64 NCG: Fix sub-word arithmetic right shift
  
  As noted in Note [Signed arithmetic on AArch64], we should zero-extend sub-word values.
  
  Fixes #26061
  

• 05e9be18
  by Simon Hengel at 2025-06-06T05:48:35-04:00

  Allow Unicode in "message" and "hints" with -fdiagnostics-as-json
  
  (fixes #26075)
  

• bfa6b70f
  by ARATA Mizuki at 2025-06-06T05:49:24-04:00

  x86 NCG: Fix code generation of bswap64 on i386
  
  Co-authored-by: sheaf <sam.derbyshire@gmail.com>
  
  Fix #25601
  

• 35826d8b
  by Matthew Pickering at 2025-06-08T22:00:41+01:00

  Hadrian: Add option to generate .hie files for stage1 libraries
  
  The +hie_files flavour transformer can be enabled to produce hie files
  for stage1 libraries. The hie files are produced in the
  "extra-compilation-artifacts" folder and copied into the resulting
  bindist.
  
  At the moment the hie files are not produced for the release flavour,
  they add about 170M to the final bindist.
  
  Towards #16901
  

• e2467dbd
  by Ryan Hendrickson at 2025-06-09T13:07:05-04:00

  Fix various failures to -fprint-unicode-syntax
  

• 1d99d3e4
  by maralorn at 2025-06-12T03:47:39-04:00

  Add necessary flag for js linking
  

• 974d5734
  by maralorn at 2025-06-12T03:47:39-04:00

  Don’t use additional linker flags to detect presence of -fno-pie in configure.ac
  
  This mirrors the behavior of ghc-toolchain
  

• 1e9eb118
  by Andrew Lelechenko at 2025-06-12T03:48:21-04:00

  Add HasCallStack to Control.Monad.Fail.fail
  
  CLC proposal https://github.com/haskell/core-libraries-committee/issues/327
  
  2% compile-time allocations increase in T3064, likely because `fail`
  is now marginally more expensive to compile.
  
  Metric Increase:
      T3064
  

• 6d12060f
  by meooow25 at 2025-06-12T14:26:07-04:00

  Bump containers submodule to 0.8
  
  Also
  
  * Disable -Wunused-imports for containers
  * Allow containers-0.8 for in-tree packages
  * Bump some submodules so that they allow containers-0.8. These are not
    at any particular versions.
  * Remove unused deps containers and split from ucd2haskell
  * Fix tests affected by the new containers and hpc-bin
  

• 537bd233
  by Peng Fan at 2025-06-12T14:27:02-04:00

  NCG/LA64: Optimize code generation and reduce build-directory size.
  
  1. makeFarBranches: Prioritize fewer instruction sequences.
  2. Prefer instructions with immediate numbers to reduce register moves,
    e.g. andi,ori,xori,addi.
  3. Ppr: Remove unnecessary judgments.
  4. genJump: Avoid "ld+jr" as much as possible.
  5. BCOND and BCOND1: Implement conditional jumps with two jump ranges,
    with limited choice of the shortest.
  6. Implement FSQRT, CLT, CTZ.
  7. Remove unnecessary code.
  

• 19f20861
  by Simon Peyton Jones at 2025-06-13T09:51:11-04:00

  Improve redundant constraints for instance decls
  
  Addresses #25992, which showed that the default methods
  of an instance decl could make GHC fail to report redundant
  constraints.
  
  Figuring out how to do this led me to refactor the computation
  of redundant constraints.  See the entirely rewritten
  
     Note [Tracking redundant constraints]
  
  in GHC.Tc.Solver.Solve
  

• 1d02798e
  by Matthew Pickering at 2025-06-13T09:51:54-04:00

  Refactor the treatment of nested Template Haskell splices
  
  * The difference between a normal splice, a quasiquoter and implicit
  splice caused by lifting is stored in the AST after renaming.
  
  * Information that the renamer learns about splices is stored in the
  relevant splice extension points (XUntypedSpliceExpr, XQuasiQuote).
  
  * Normal splices and quasi quotes record the flavour of splice
    (exp/pat/dec etc)
  
  * Implicit lifting stores information about why the lift was attempted,
    so if it fails, that can be reported to the user.
  
  * After renaming, the decision taken to attempt to implicitly lift a
  variable is stored in the `XXUntypedSplice` extension field in the
  `HsImplicitLiftSplice` constructor.
  
  * Since all the information is stored in the AST, in `HsUntypedSplice`,
    the type of `PendingRnSplice` now just stores a `HsUntypedSplice`.
  
  * Error messages since the original program can be easily
    printed, this is noticeable in the case of implicit lifting.
  * The user-written syntax is directly type-checked. Before, some
    desugaring took place in the
  * Fixes .hie files to work better with nested splices (nested splices
    are not indexed)
  * The location of the quoter in a quasiquote is now located, so error
    messages will precisely point to it (and again, it is indexed by hie
    files)
  
  In the future, the typechecked AST should also retain information about
  the splices and the specific desugaring being left to the desugarer.
  
  Also, `runRnSplice` should call `tcUntypedSplice`, otherwise the
  typechecking logic is duplicated (see the `QQError` and `QQTopError`
  tests for a difference caused by this).
  

• f93798ba
  by Cheng Shao at 2025-06-13T09:52:35-04:00

  libffi: update to 3.5.1
  
  Bumps libffi submodule.
  

• c7aa0c10
  by Andreas Klebinger at 2025-06-15T05:47:24-04:00

  Revert "Specialise: Don't float out constraint components."
  
  This reverts commit c9abb87ccc0c91cd94f42b3e36270158398326ef.
  
  Turns out two benchmarks from #19747 regresses by a factor of 7-8x if
  we do not float those out.
  

• fd998679
  by Krzysztof Gogolewski at 2025-06-15T05:48:06-04:00

  Fix EPT enforcement when mixing unboxed tuples and non-tuples
  
  The code was assuming that an alternative cannot be returning a normal
  datacon and an unboxed tuple at the same time. However, as seen in #26107,
  this can happen when using a GADT to refine the representation type.
  
  The solution is just to conservatively return TagDunno.
  

• e64b3f16
  by ARATA Mizuki at 2025-06-17T10:13:42+09:00

  MachRegs.h: Don't define NO_ARG_REGS when a XMM register is defined
  
  On i386, MAX_REAL_VANILLA_REG is 1, but MAX_REAL_XMM_REG is 4.
  If we define NO_ARG_REGS on i386, programs that use SIMD vectors may segfault.
  
  Closes #25985
  
  A couple of notes on the BROKEN_TESTS field:
  
  * This fixes the segfault from T25062_V16.
  * The failure from T22187_run was fixed in an earlier commit (see #25561),
    but BROKEN_TESTS was missed at that time.  Now should be a good time to
    mark it fixed.
  

• 3e7c6b4d
  by Matthew Pickering at 2025-06-18T15:34:04-04:00

  Improve error messages when implicit lifting fails
  
  This patch concerns programs which automatically try to fix level errors
  by inserting `Lift`. For example:
  
  ```
  foo x = [| x |]
  ~>
  foo x = [| $(lift x) |]
  ```
  
  Before, there were two problems with the message.
  
  1. (#26031), the location of the error was reported as the whole
     quotation.
  2. (#26035), the message just mentions there is no Lift instance, but
     gives no indicate why the user program needed a Lift instance in the
     first place.
  
  This problem is especially bad when you disable
  `ImplicitStagePersistence`, so you just end up with a confusing "No
  instance for" message rather than an error message about levels
  
  This patch fixes both these issues.
  
  Firstly, `PendingRnSplice` differentiates between a user-written splice
  and an implicit lift. Then, the Lift instance is precisely requested
  with a specific origin in the typechecker. If the instance fails to be
  solved, the message is reported using the `TcRnBadlyLevelled`
  constructor (like a normal level error).
  
  Fixes #26031, #26035
  

• 44b8cee2
  by Cheng Shao at 2025-06-18T15:34:46-04:00

  testsuite: add T26120 marked as broken
  

• 894a04f3
  by Cheng Shao at 2025-06-18T15:34:46-04:00

  compiler: fix GHC.SysTools.Ar archive member size writing logic
  
  This patch fixes a long-standing bug in `GHC.SysTools.Ar` that emits
  the wrong archive member size in each archive header. It should encode
  the exact length of the member payload, excluding any padding byte,
  otherwise malformed archive that extracts a broken object with an
  extra trailing byte could be created.
  
  Apart from the in-tree `T26120` test, I've also created an out-of-tree
  testsuite at https://github.com/TerrorJack/ghc-ar-quickcheck that
  contains QuickCheck roundtrip tests for `GHC.SysTools.Ar`. With this
  fix, simple roundtrip tests and `writeGNUAr`/GNU `ar` roundtrip test
  passes. There might be more bugs lurking in here, but this patch is
  still a critical bugfix already.
  
  Fixes #26120 #22586.
  
  Co-authored-by: Codex <codex@openai.com>
  

• f677ab5f
  by Lauren Yim at 2025-06-18T15:35:37-04:00

  fix some typos in the warnings page in the user guide
  

• b968e1c1
  by Rodrigo Mesquita at 2025-06-18T15:36:18-04:00

  Add a frozen callstack to throwGhcException
  
  Fixes #25956
  

• a5e0c3a3
  by fendor at 2025-06-18T15:36:59-04:00

  Update using.rst to advertise full mhu support for GHCi
  

• d3e60e97
  by Ryan Scott at 2025-06-18T22:29:21-04:00

  Deprecate -Wdata-kinds-tc, make DataKinds issues in typechecker become errors
  
  !11314 introduced the `-Wdata-kinds-tc` warning as part of a fix for #22141.
  This was a temporary stopgap measure to allow users who were accidentally
  relying on code which needed the `DataKinds` extension in order to typecheck
  without having to explicitly enable the extension.
  
  Now that some amount of time has passed, this patch deprecates
  `-Wdata-kinds-tc` and upgrades any `DataKinds`-related issues in the
  typechecker (which were previously warnings) into errors.
  

• fd5b5177
  by Ryan Hendrickson at 2025-06-18T22:30:06-04:00

  haddock: Add redact-type-synonyms pragma
  
  `{-# OPTIONS_HADDOCK redact-type-synonyms #-}` pragma will hide the RHS
  of type synonyms, and display the result kind instead, if the RHS
  contains any unexported types.
  

• fbc0b92a
  by Vladislav Zavialov at 2025-06-22T04:25:16+03:00

  Visible forall in GADTs (#25127)
  
  Add support for visible dependent quantification `forall a -> t` in
  types of data constructors, e.g.
  
    data KindVal a where
      K :: forall k.
           forall (a::k) ->   -- now allowed!
           k ->
           KindVal a
  
  For details, see docs/users_guide/exts/required_type_arguments.rst,
  which has gained a new subsection.
  
  DataCon in compiler/GHC/Core/DataCon.hs
  ---------------------------------------
  The main change in this patch is that DataCon, the Core representation
  of a data constructor, now uses a different type to store user-written
  type variable binders:
  
    - dcUserTyVarBinders :: [InvisTVBinder]
    + dcUserTyVarBinders :: [TyVarBinder]
  
  where
  
    type TyVarBinder   = VarBndr TyVar ForAllTyFlag
    type InvisTVBinder = VarBndr TyVar Specificity
  
  and
  
    data Specificity  = InferredSpec | SpecifiedSpec
    data ForAllTyFlag = Invisible Specificity | Required
  
  This change necessitates some boring, mechanical changes scattered
  throughout the diff:
  
      ... is now used in place of ...
     -----------------+---------------
      TyVarBinder     | InvisTVBinder
      IfaceForAllBndr | IfaceForAllSpecBndr
      Specified       | SpecifiedSpec
      Inferred        | InferredSpec
      mkForAllTys     | mkInvisForAllTys
  
    additionally,
  
      tyVarSpecToBinders      -- added or removed calls
      ifaceForAllSpecToBndrs  -- removed calls
  
  Visibility casts in mkDataConRep
  --------------------------------
  Type abstractions in Core (/\a. e) always have type (forall a. t)
  because coreTyLamForAllTyFlag = Specified. This is also true of data
  constructor workers. So we may be faced with the following:
  
    data con worker:  (forall a.   blah)
    data con wrapper: (forall a -> blah)
  
  In this case the wrapper must use a visibility cast (e |> ForAllCo ...)
  with appropriately set fco_vis{L,R}. Relevant functions:
  
    mkDataConRep   in compiler/GHC/Types/Id/Make.hs
    dataConUserTyVarBindersNeedWrapper in compiler/GHC/Core/DataCon.hs
    mkForAllVisCos in compiler/GHC/Core/Coercion.hs
    mkCoreTyLams   in compiler/GHC/Core/Make.hs
    mkWpForAllCast in compiler/GHC/Tc/Types/Evidence.hs
  
  More specifically:
  
  - dataConUserTyVarBindersNeedWrapper has been updated to answer "yes"
    if there are visible foralls in the type of the data constructor.
  
  - mkDataConRep now uses mkCoreTyLams to generate the big lambda
    abstractions (/\a b c. e) in the data con wrapper.
  
  - mkCoreTyLams is a variant of mkCoreLams that applies visibility casts
    as needed. It similar in purpose to the pre-existing mkWpForAllCast,
    so the common bits have been factored out into mkForAllVisCos.
  
  ConDecl in compiler/Language/Haskell/Syntax/Decls.hs
  ----------------------------------------------------
  The surface syntax representation of a data constructor declaration is
  ConDecl. In accordance with the proposal, only GADT syntax is extended
  with support for visible forall, so we are interested in ConDeclGADT.
  
  ConDeclGADT's field con_bndrs has been renamed to con_outer_bndrs
  and is now accompanied by con_inner_bndrs:
  
    con_outer_bndrs :: XRec pass (HsOuterSigTyVarBndrs pass)
    con_inner_bndrs :: [HsForAllTelescope pass]
  
  Visible foralls always end up in con_inner_bndrs. The outer binders are
  stored and processed separately to support implicit quantification and
  the forall-or-nothing rule, a design established by HsSigType.
  
  A side effect of this change is that even in absence of visible foralls,
  GHC now permits multiple invisible foralls, e.g.
  
    data T a where { MkT :: forall a b. forall c d. ... -> T a }
  
  But of course, this is done in service of making at least some of these
  foralls visible. The entire compiler front-end has been updated to deal
  with con_inner_bndrs. See the following modified or added functions:
  
    Parser:
        mkGadtDecl     in compiler/GHC/Parser/PostProcess.hs
        splitLHsGadtTy in compiler/GHC/Hs/Type.hs
    Pretty-printer:
        pprConDecl           in compiler/GHC/Hs/Decls.hs
        pprHsForAllTelescope in compiler/GHC/Hs/Type.hs
    Renamer:
        rnConDecl                 in compiler/GHC/Rename/Module.hs
        bindHsForAllTelescopes    in compiler/GHC/Rename/HsType.hs
        extractHsForAllTelescopes in compiler/GHC/Rename/HsType.hs
    Type checker:
        tcConDecl           in compiler/GHC/Tc/TyCl.hs
        tcGadtConTyVarBndrs in compiler/GHC/Tc/Gen/HsType.hs
  
  Template Haskell
  ----------------
  The TH AST is left unchanged for the moment to avoid breakage. An
  attempt to quote or reify a data constructor declaration with visible
  forall in its type will result an error:
  
    data ThRejectionReason       -- in GHC/HsToCore/Errors/Types.hs
      = ...
      | ThDataConVisibleForall   -- new error constructor
  
  However, as noted in the previous section, GHC now permits multiple
  invisible foralls, and TH was updated accordingly. Updated code:
  
        repC         in compiler/GHC/HsToCore/Quote.hs
        reifyDataCon in compiler/GHC/Tc/Gen/Splice.hs
        ppr @Con     in libraries/ghc-boot-th/GHC/Boot/TH/Ppr.hs
  
  Pattern matching
  ----------------
  Everything described above concerns data constructor declarations, but
  what about their use sites? Now it is trickier to type check a pattern
  match fn(Con a b c)=... because we can no longer assume that a,b,c are
  all value arguments. Indeed, some or all of them may very well turn out
  to be required type arguments.
  
  To that end, see the changes to:
  
        tcDataConPat   in compiler/GHC/Tc/Gen/Pat.hs
        splitConTyArgs in compiler/GHC/Tc/Gen/Pat.hs
  
  and the new helpers split_con_ty_args, zip_pats_bndrs.
  
  This is also the reason the TcRnTooManyTyArgsInConPattern error
  constructor has been removed. The new code emits TcRnArityMismatch
  or TcRnIllegalInvisibleTypePattern.
  
  Summary
  -------
  DataCon, ConDecl, as well as all related functions have been updated to
  support required type arguments in data constructors.
  
  Test cases:
    HieGadtConSigs   GadtConSigs_th_dump1   GadtConSigs_th_pprint1
    T25127_data      T25127_data_inst       T25127_infix
    T25127_newtype   T25127_fail_th_quote   T25127_fail_arity
    TyAppPat_Tricky
  
  Co-authored-by: mniip <mniip@mniip.com>
  

• ae003a3a
  by Teo Camarasu at 2025-06-23T05:21:48-04:00

  linters: lint-whitespace: bump upper-bound for containers
  
  The version of containers was bumped in https://gitlab.haskell.org/ghc/ghc/-/merge_requests/13989
  

• 0fb37893
  by Matthew Pickering at 2025-06-23T13:55:10-04:00

  Move ModuleGraph into UnitEnv
  
  The ModuleGraph is a piece of information associated with the
  ExternalPackageState and HomeUnitGraph. Therefore we should store it
  inside the HomeUnitEnv.
  

• 3bf6720e
  by soulomoon at 2025-06-23T13:55:52-04:00

  Remove hptAllFamInstances usage during upsweep
  
  Fixes #26118
  
  This change eliminates the use of hptAllFamInstances during the upsweep phase,
  as it could access non-below modules from the home package table.
  
  The following updates were made:
  
  * Updated checkFamInstConsistency to accept an explicit ModuleEnv FamInstEnv
    parameter and removed the call to hptAllFamInstances.
  * Adjusted hugInstancesBelow so we can construct ModuleEnv FamInstEnv
    from its result,
  * hptAllFamInstances and allFamInstances functions are removed.
  

• 83ee7b78
  by Ben Gamari at 2025-06-24T05:02:07-04:00

  configure: Don't force value of OTOOL, etc. if not present
  
  Previously if `otool` and `install_name_tool` were not present they
  would be overridden by `fp_settings.m4`. This logic was introduced in
  4ff93292243888545da452ea4d4c1987f2343591 without explanation.
  

• 9329c9e1
  by Ben Gamari at 2025-06-24T05:02:07-04:00

  ghc-toolchain: Add support for otool, install_name_tool
  
  Fixes part of ghc#23675.
  

• 25f5c998
  by Ben Gamari at 2025-06-24T05:02:08-04:00

  ghc-toolchain: Add support for llc, opt, llvm-as
  
  Fixes #23675.
  

• 51d150dd
  by Rodrigo Mesquita at 2025-06-24T05:02:08-04:00

  hadrian: Use settings-use-distro-mingw directly
  
  The type `ToolchainSetting` only made sense when we had more settings to
  fetch from the system config file. Even then "settings-use-distro-mingw"
  is arguably not a toolchain setting.
  
  With the fix for #23675, all toolchain tools were moved to the
  `ghc-toolchain` `Toolchain` format. Therefore, we can inline
  `settings-use-distro-mingw` accesses and delete `ToolchainSetting`.
  

• dcf68a83
  by Rodrigo Mesquita at 2025-06-24T05:02:08-04:00

  configure: Check LlvmTarget exists for LlvmAsFlags
  
  If LlvmTarget was empty, LlvmAsFlags would be just "--target=".
  If it is empty now, simply keep LlvmAsFlags empty.
  
  ghc-toolchain already does this right. This fix makes the two
  configurations match up.
  

• 580a3353
  by Ben Gamari at 2025-06-24T05:02:51-04:00

  rts/linker/LoadArchive: Use bool
  
  Improve type precision by using `bool` instead of `int` and `StgBool`.
  

• 76d1041d
  by Ben Gamari at 2025-06-24T05:02:51-04:00

  rts/linker/LoadArchive: Don't rely on file extensions for identification
  
  Previously archive members would be identified via their file extension,
  as described in #13103. We now instead use a more principled approach,
  relying on the magic number in the member's header.
  
  As well, we refactor treatment of archive format detection to improve
  code clarity and error handling.
  
  Closes #13103.
  

• 4b748a99
  by Teo Camarasu at 2025-06-24T15:31:07-04:00

  template-haskell: improve changelog
  
  
  stable -> more stable, just to clarify that this interface isn't fully stable.
  
  errornously -> mistakenly: I typod this and also let's go for a simpler word

• e358e477
  by Sylvain Henry at 2025-06-24T15:31:58-04:00

  Bump stack resolver to use GHC 9.6.7
  
  Cf #26139
  

• 4bf5eb63
  by fendor at 2025-06-25T17:05:43-04:00

  Teach `:reload` about multiple home units
  
  `:reload` needs to lookup the `ModuleName` and must not assume the given
  `ModuleName` is in the current `HomeUnit`.
  
  We add a new utility function which allows us to find a `HomeUnitModule`
  instead of a `Module`.
  
  Further, we introduce the `GhciCommandError` type which can be used to
  abort the execution of a GHCi command.
  This error is caught and printed in a human readable fashion.
  

• b3d97bb3
  by fendor at 2025-06-25T17:06:25-04:00

  Implement `-fno-load-initial-targets` flag
  
  We add the new flag `-fno-load-initial-targets` which doesn't load all `Target`s
  immediately but only computes the module graph for all `Target`s.
  The user can then decide to load modules from that module graph using
  the syntax:
  
      ghci> :reload <Mod>
  
  This will load everything in the module graph up to `Mod`.
  
  The user can return to the initial state by using the builtin target
  `none` to unload all modules.
  
      ghci> :reload none
  
  Is in principle identical to starting a new session with the
  `-fno-load-initial-targets` flag.
  
  The `-fno-load-initial-targets` flag allows for faster startup time of GHCi when a
  user has lots of `Target`s.
  
  We additionally extend the `:reload` command to accept multiple
  `ModuleName`s. For example:
  
      ghci> :reload <Mod1> <Mod2>
  
  Loads all modules up to the modules `Mod1` and `Mod2`.
  

• 49f44e52
  by Teo Camarasu at 2025-06-26T04:19:51-04:00

  Expose ghc-internal unit id through the settings file
  
  This in combination with the unit id of the compiler library allows
  cabal to know of the two unit ids that should not be reinstalled (in
  specific circumstances) as:
  - when using plugins, we want to link against exactly the compiler unit
  id
  - when using TemplateHaskell we want to link against exactly the package
  that contains the TemplateHaskell interfaces, which is `ghc-internal`
  
  See: <https://github.com/haskell/cabal/issues/10087>
  
  Resolves #25282
  

• 499c4efe
  by Bryan Richter at 2025-06-26T04:20:33-04:00

  CI: Fix and clean up capture of timings
  
  * Fixes the typo that caused 'cat ci-timings' to report "no such file or
    directory"
  * Gave ci_timings.txt a file extension so it may play better with other
    systems
  * Fixed the use of time_it so all times are recorded
  * Fixed time_it to print name along with timing
  

• 86c90c9e
  by Bryan Richter at 2025-06-26T04:20:33-04:00

  CI: Update collapsible section usage
  
  The syntax apparently changed at some point.
  

• 04308ee4
  by Bryan Richter at 2025-06-26T04:20:33-04:00

  CI: Add more collapsible sections
  

• 43b606bb
  by Florian Ragwitz at 2025-06-27T16:31:26-04:00

  Tick uses of wildcard/pun field binds as if using the record selector function
  
  Fixes #17834.
  
  See Note [Record-selector ticks] for additional reasoning behind this as well
  as an overview of the implementation details and future improvements.
  

• d4952549
  by Ben Gamari at 2025-06-27T16:32:08-04:00

  testsuite/caller-cc: Make CallerCc[123] less sensitive
  
  These were previously sensitive to irrelevant changes in program
  structure. To avoid this we filter out all by lines emitted by the
  -fcaller-cc from the profile.
  

• 8d33d048
  by Berk Özkütük at 2025-07-07T20:42:20-04:00

  Consider `PromotedDataCon` in `tyConStupidTheta`
  
  Haddock checks data declarations for the stupid theta so as not to
  pretty-print them as empty contexts. Type data declarations end up as
  `PromotedDataCon`s by the time Haddock performs this check, causing a
  panic. This commit extends `tyConStupidTheta` so that it returns an
  empty list for `PromotedDataCon`s. This decision was guided by the fact
  that type data declarations never have data type contexts (see (R1) in
  Note [Type data declarations]).
  
  Fixes #25739.
  

• a26243fd
  by Ryan Hendrickson at 2025-07-07T20:43:07-04:00

  haddock: Document instances from other packages
  
  When attaching instances to `Interface`s, it isn't enough just to look
  for instances in the list of `Interface`s being processed. We also need
  to look in the modules on which they depend, including those outside of
  this package.
  
  Fixes #25147.
  Fixes #26079.
  

• 0fb24420
  by Rodrigo Mesquita at 2025-07-07T20:43:49-04:00

  hadrian: Fallback logic for internal interpreter
  
  When determining whether to build the internal interpreter, the `make`
  build system had a fallback case for platforms not in the list of
  explicitly-supported operating systems and architectures.
  
  This fallback says we should try to build the internal interpreter if
  building dynamic GHC programs (if the architecture is unknown).
  
  Fixes #24098
  

• fe925bd4
  by Ben Gamari at 2025-07-07T20:44:30-04:00

  users-guide: Reference Wasm FFI section
  

• 5856284b
  by Ben Gamari at 2025-07-07T20:44:30-04:00

  users-guide: Fix too-short heading warning
  

• a48dcdf3
  by Duncan Coutts at 2025-07-07T20:45:18-04:00

  Reorganise documentation for allocate* functions
  
  Consolodate interface information into the .h file, keeping just
  implementation details in the .c file.
  
  Use Notes stlye in the .h file and refer to notes from the .c file.
  

• de5b528c
  by Duncan Coutts at 2025-07-07T20:45:18-04:00

  Introduce common utilities for allocating arrays
  
  The intention is to share code among the several places that do this
  already.
  

• b321319d
  by Duncan Coutts at 2025-07-07T20:45:18-04:00

  Use new array alloc utils in Heap.c
  
  The CMM primop can now report heap overflow.
  

• 1d557ffb
  by Duncan Coutts at 2025-07-07T20:45:18-04:00

  Use new array alloc utils in ThreadLabels.c
  
  Replacing a local utility.
  

• e59a1430
  by Duncan Coutts at 2025-07-07T20:45:18-04:00

  Use new array alloc utils in Threads.c
  
  Replacing local open coded version.
  

• 482df1c9
  by Duncan Coutts at 2025-07-07T20:45:18-04:00

  Add exitHeapOverflow helper utility
  
  This will be useful with the array alloc functions, since unlike
  allocate/allocateMaybeFail, they do not come in two versions. So if it's
  not convenient to propagate failure, then one can use this.
  

• 4d3ec8f9
  by Duncan Coutts at 2025-07-07T20:45:18-04:00

  Use new array alloc utils in Weak.c
  
  Also add a cpp macro CCS_SYSTEM_OR_NULL which does what it says. The
  benefit of this is that it allows us to referece CCS_SYSTEM even when
  we're not in PROFILING mode. That makes abstracting over profiling vs
  normal mode a lot easier.
  

• 0c4f2fde
  by Duncan Coutts at 2025-07-07T20:45:18-04:00

  Convert the array alloc primops to use the new array alloc utils
  

• a3354ad9
  by Duncan Coutts at 2025-07-07T20:45:18-04:00

  While we're at it, add one missing 'likely' hint
  
  To a cmm primops that raises an exception, like the others now do.
  

• 33b546bd
  by meooow25 at 2025-07-07T20:46:09-04:00

  Keep scanl' strict in the head on rewrite
  
  `scanl'` forces elements to WHNF when the corresponding `(:)`s are
  forced. The rewrite rule for `scanl'` missed forcing the first element,
  which is fixed here with a `seq`.
  

• 8a69196e
  by Rodrigo Mesquita at 2025-07-08T07:39:47-04:00

  debugger/rts: Allow toggling step-in per thread
  
  The RTS global flag `rts_stop_next_breakpoint` globally sets the
  interpreter to stop at the immediate next breakpoint.
  
  With this commit, single step mode can additionally be set per thread in
  the TSO flag (TSO_STOP_NEXT_BREAKPOINT).
  
  Being able to toggle "stop at next breakpoint" per thread is an
  important requirement for implementing "stepping out" of a function in a
  multi-threaded context.
  
  And, more generally, having a per-thread flag for single-stepping paves the
  way for multi-threaded debugging.
  
  That said, when we want to enable "single step" mode for the whole
  interpreted program we still want to stop at the immediate next
  breakpoint, whichever thread it belongs to.
  
  That's why we also keep the global `rts_stop_next_breakpoint` flag, with
  `rts_enableStopNextBreakpointAll` and `rts_disableStopNextBreakpointAll` helpers.
  
  Preparation for #26042
  

• 73d3f864
  by Rodrigo Mesquita at 2025-07-08T07:39:47-04:00

  docs: Case continuation BCOs
  
  This commit documents a subtle interaction between frames for case BCOs
  and their parents frames. Namely, case continuation BCOs may refer to
  (non-local) variables that are part of the parent's frame.
  
  The note expanding a bit on these details is called [Case continuation BCOs]
  

• d7aeddcf
  by Rodrigo Mesquita at 2025-07-08T07:39:47-04:00

  debugger: Implement step-out feature
  
  Implements support for stepping-out of a function (aka breaking right after
  returning from a function) in the interactive debugger.
  
  It also introduces a GHCi command :stepout to step-out of a function
  being debugged in the interpreter. The feature is described as:
  
      Stop at the first breakpoint immediately after returning from the current
      function scope.
  
      Known limitations: because a function tail-call does not push a stack
      frame, if step-out is used inside of a function that was tail-called,
      execution will not be returned to its caller, but rather its caller's
      first non-tail caller. On the other hand, it means the debugger
      follows the more realistic execution of the program.
      In the following example:
  
      .. code-block:: none
  
      f = do
         a
         b <--- (1) set breakpoint then step in here
         c
      b = do
         ...
         d <--- (2) step-into this tail call
      d = do
         ...
         something <--- (3) step-out here
         ...
  
      Stepping-out will stop execution at the `c` invokation in `f`, rather than
      stopping at `b`.
  
  The key idea is simple: When step-out is enabled, traverse the runtime
  stack until a continuation BCO is found -- and enable the breakpoint
  heading that BCO explicitly using its tick-index.
  The details are specified in `Note [Debugger: Step-out]` in `rts/Interpreter.c`.
  
  Since PUSH_ALTS BCOs (representing case continuations) were never headed
  by a breakpoint (unlike the case alternatives they push), we introduced
  the BRK_ALTS instruction to allow the debugger to set a case
  continuation to stop at the breakpoint heading the alternative that is
  taken. This is further described in `Note [Debugger: BRK_ALTS]`.
  
  Fixes #26042
  

• 5d9adf51
  by Rodrigo Mesquita at 2025-07-08T07:39:47-04:00

  debugger: Filter step-out stops by SrcSpan
  
  To implement step-out, the RTS looks for the first continuation frame on
  the stack and explicitly enables its entry breakpoint. However, some
  continuations will be contained in the function from which step-out was
  initiated (trivial example is a case expression).
  
  Similarly to steplocal, we will filter the breakpoints at which the RTS
  yields to the debugger based on the SrcSpan. When doing step-out, only
  stop if the breakpoint is /not/ contained in the function from which we
  initiated it.
  
  This is especially relevant in monadic statements such as IO which is
  compiled to a long chain of case expressions.
  
  See Note [Debugger: Filtering step-out stops]
  

• 7677adcc
  by Cheng Shao at 2025-07-08T07:40:29-04:00

  compiler: make ModBreaks serializable
  

• 14f67c6d
  by Rodrigo Mesquita at 2025-07-08T07:40:29-04:00

  refactor: "Inspecting the session" moved from GHC
  
  Moved utilities for inspecting the session from the GHC module to
  GHC.Driver.Session.Inspect
  
  Purely a clean up
  

• 9d3f484a
  by Rodrigo Mesquita at 2025-07-08T07:40:30-04:00

  cleanup: Pass the HUG to readModBreaks, not HscEnv
  
  A minor cleanup. The associated history and setupBreakpoint functions
  are changed accordingly.
  

• b595f713
  by Rodrigo Mesquita at 2025-07-08T07:40:30-04:00

  cleanup: Move readModBreaks to GHC.Runtime.Interpreter
  
  With some small docs changes
  

• d223227a
  by Rodrigo Mesquita at 2025-07-08T07:40:30-04:00

  cleanup: Move interpreterProfiled to Interp.Types
  
  Moves interpreterProfiled and interpreterDynamic to
  GHC.Runtime.Interpreter.Types from GHC.Runtime.Interpreter.
  

• 7fdd0a3d
  by Rodrigo Mesquita at 2025-07-08T07:40:30-04:00

  cleanup: Don't import GHC in Debugger.Breakpoints
  
  Remove the top-level
  
      import GHC
  
  from GHC.Runtime.Debugger.Breakpoints
  
  This makes the module dependencies more granular and cleans up the
  qualified imports from the code.
  

• 5e4da31b
  by Rodrigo Mesquita at 2025-07-08T07:40:30-04:00

  refactor: Use BreakpointId in Core and Ifaces
  

• 741ac3a8
  by Rodrigo Mesquita at 2025-07-08T07:40:30-04:00

  stg2bc: Derive BcM via ReaderT StateT
  
  A small refactor that simplifies GHC.StgToByteCode by deriving-via the
  Monad instances for BcM. This is done along the lines of previous
  similar refactors like 72b54c0760bbf85be1f73c1a364d4701e5720465.
  

• 0414fcc9
  by Rodrigo Mesquita at 2025-07-08T07:40:30-04:00

  refact: Split InternalModBreaks out of ModBreaks
  
  There are currently two competing ways of referring to a Breakpoint:
  
      1. Using the Tick module + Tick index
      2. Using the Info module + Info index
  
  1. The Tick index is allocated during desugaring in `mkModBreaks`. It is
  used to refer to a breakpoint associated to a Core Tick. For a given
  Tick module, there are N Ticks indexed by Tick index.
  
  2. The Info index is allocated during code generation (in StgToByteCode)
  and uniquely identifies the breakpoints at runtime (and is indeed used
  to determine which breakpoint was hit at runtime).
  
  Why we need both is described by Note [Breakpoint identifiers].
  
  For every info index we used to keep a `CgBreakInfo`, a datatype containing
  information relevant to ByteCode Generation, in `ModBreaks`.
  
  This commit splits out the `IntMap CgBreakInfo` out of `ModBreaks` into
  a new datatype `InternalModBreaks`.
  
      - The purpose is to separate the `ModBreaks` datatype, which stores
        data associated from tick-level information which is fixed after
        desugaring, from the unrelated `IntMap CgBreakInfo` information
        accumulated during bytecode generation.
  
      - We move `ModBreaks` to GHC.HsToCore.Breakpoints
  
  The new `InternalModBreaks` simply combines the `IntMap CgBreakInfo`
  with `ModBreaks`. After code generation we construct an
  `InternalModBreaks` with the `CgBreakInfo`s we accumulated and the
  existing `ModBreaks` and store that in the compiled BCO in `bc_breaks`.
  
      - Note that we previously only updated the `modBreaks_breakInfo`
        field of `ModBreaks` at this exact location, and then stored the
        updated `ModBreaks` in the same `bc_breaks`.
  
      - We put this new datatype in GHC.ByteCode.Breakpoints
  
  The rest of the pipeline for which CgBreakInfo is relevant is
  accordingly updated to also use `InternalModBreaks`
  

• 2a097955
  by Rodrigo Mesquita at 2025-07-08T07:40:30-04:00

  cleanup: Use BreakpointIds in bytecode gen
  
  Small clean up to use BreakpointId and InternalBreakpointId more
  uniformly in bytecode generation rather than using Module + Ix pairs
  

• 0515cc2f
  by Rodrigo Mesquita at 2025-07-08T07:40:30-04:00

  ghci: Allocate BreakArrays at link time only
  
  Previously, a BreakArray would be allocated with a slot for every tick
  in a module at `mkModBreaks`, in HsToCore. However, this approach has
  a few downsides:
  
  - It interleaves interpreter behaviour (allocating arrays for
    breakpoints) within the desugarer
  
  - It is inflexible in the sense it is impossible for the bytecode
    generator to add "internal" breakpoints that can be triggered at
    runtime, because those wouldn't have a source tick. (This is relevant
    for our intended implementation plan of step-out in #26042)
  
  - It ties the BreakArray indices to the *tick* indexes, while at runtime
    we would rather just have the *info* indexes (currently we have both
    because BreakArrays are indexed by the *tick* one).
  
  Paving the way for #26042 and #26064, this commit moves the allocation
  of BreakArrays to bytecode-loading time -- akin to what is done for CCS
  arrays.
  
  Since a BreakArray is allocated only when bytecode is linked, if a
  breakpoint is set (e.g. `:break 10`) before the bytecode is linked,
  there will exist no BreakArray to trigger the breakpoint in.
  
  Therefore, the function to allocate break arrays (`allocateBreakArrays`)
  is exposed and also used in GHC.Runtime.Eval to allocate a break array
  when a breakpoint is set, if it doesn't exist yet (in the linker env).
  

• 8016561f
  by Simon Peyton Jones at 2025-07-08T07:41:13-04:00

  Add a test for T26176
  

• 454cd682
  by Simon Peyton Jones at 2025-07-08T07:41:13-04:00

  Add test for #14010
  
  This test started to work in GHC 9.6 and has worked since.
  This MR just adds a regression test
  

• ea2c6673
  by Teo Camarasu at 2025-07-08T13:24:43-04:00

  Implement user-defined allocation limit handlers
  
  Allocation Limits allow killing a thread if they allocate more than a
  user-specified limit.
  We extend this feature to allow more versatile behaviour.
  
  - We allow not killing the thread if the limit is exceeded.
  - We allow setting a custom handler to be called when the limit is exceeded.
  
  User-specified allocation limit handlers run in a fresh thread and are passed
  the ThreadId of the thread that exceeded its limit.
  
  We introduce utility functions for getting and setting the allocation
  limits of other threads, so that users can reset the limit of a thread
  from a handler. Both of these are somewhat coarse-grained as we are
  unaware of the allocations in the current nursery chunk.
  
  We provide several examples of usages in testsuite/tests/rts/T22859.hs
  
  Resolves #22859
  

• 03e047f9
  by Simon Hengel at 2025-07-08T13:25:25-04:00

  Fix typo in using.rst
  

• 67957854
  by Ben Gamari at 2025-07-09T09:44:44-04:00

  compiler: Import AnnotationWrapper from ghc-internal
  
  Since `GHC.Desugar` exported from `base` has been deprecated.
  

• 813d99d6
  by Ben Gamari at 2025-07-09T09:44:44-04:00

  ghc-compact: Eliminate dependency on ghc-prim
  

• 0ec952a1
  by Ben Gamari at 2025-07-09T09:44:44-04:00

  ghc-heap: Eliminate dependency on ghc-prim
  

• 480074c3
  by Ben Gamari at 2025-07-09T09:44:44-04:00

  ghc-heap: Drop redundant import
  

• 03455829
  by Ben Gamari at 2025-07-09T09:44:45-04:00

  ghc-prim: Bump version to 0.13.1
  
  There are no interface changes from 0.13.0 but the implementation now
  lives in `ghc-internal`.
  

• d315345a
  by Ben Gamari at 2025-07-09T09:44:45-04:00

  template-haskell: Bump version number to 2.24.0.0
  
  Bumps exceptions submodule.
  

• 004c800e
  by Ben Gamari at 2025-07-09T09:44:45-04:00

  Bump GHC version number to 9.14
  

• eb1a3816
  by Ben Gamari at 2025-07-09T09:44:45-04:00

  Bump parsec to 3.1.18.0
  
  Bumps parsec submodule.
  

• 86f83296
  by Ben Gamari at 2025-07-09T09:44:45-04:00

  unix: Bump to 2.8.7.0
  
  Bumps unix submodule.
  

• 89e13998
  by Ben Gamari at 2025-07-09T09:44:45-04:00

  binary: Bump to 0.8.9.3
  
  Bumps binary submodule.
  

• 55fff191
  by Ben Gamari at 2025-07-09T09:44:45-04:00

  Win32: Bump to 2.14.2.0
  
  Bumps Win32 submodule.
  

• 7dafa40c
  by Ben Gamari at 2025-07-09T09:44:45-04:00

  base: Bump version to 4.22.0
  
  Bumps various submodules.
  

• ef03d8b8
  by Rodrigo Mesquita at 2025-07-09T09:45:28-04:00

  base: Export displayExceptionWithInfo
  
  This function should be exposed from base following CLC#285
  
  Approved change in CLC#344
  
  Fixes #26058
  

• 01d3154e
  by Wen Kokke at 2025-07-10T17:06:36+01:00

  Fix documentation for HEAP_PROF_SAMPLE_STRING
  

• ac259c48
  by Wen Kokke at 2025-07-10T17:06:38+01:00

  Fix documentation for HEAP_PROF_SAMPLE_COST_CENTRE
  

• 2b4db9ba
  by Pi Delport at 2025-07-11T16:40:52-04:00

  (Applicative docs typo: missing "one")
  

• f707bab4
  by Andreas Klebinger at 2025-07-12T14:56:16+01:00

  Specialise: Improve specialisation by refactoring interestingDict
  
  This MR addresses #26051, which concerns missed type-class specialisation.
  The main payload of the MR is to completely refactor the key function
        `interestingDict` in GHC.Core.Opt.Specialise
  
  The main change is that we now also look at the structure of the
  dictionary we consider specializing on, rather than only the type.
  
  See the big `Note [Interesting dictionary arguments]`
  

• ca7a9d42
  by Simon Peyton Jones at 2025-07-12T14:56:16+01:00

  Treat tuple dictionaries uniformly; don't unbox them
  
  See `Note [Do not unbox class dictionaries]` in DmdAnal.hs,
  sep (DNB1).
  
  This MR reverses the plan in #23398, which suggested a special case to
  unbox tuple dictionaries in worker/wrapper.  But:
  
  - This was the cause of a pile of complexity in the specialiser (#26158)
  
  - Even with that complexity, specialision was still bad, very bad
    See https://gitlab.haskell.org/ghc/ghc/-/issues/19747#note_626297
  
  And it's entirely unnecessary!  Specialision works fine without
  unboxing tuple dictionaries.
  

• be7296c9
  by Andreas Klebinger at 2025-07-12T14:56:16+01:00

  Remove complex special case from the type-class specialiser
  
  There was a pretty tricky special case in Specialise which is no
  longer necessary.
     * Historical Note [Floating dictionaries out of cases]
     * #26158
     * #19747 https://gitlab.haskell.org/ghc/ghc/-/issues/19747#note_626297
  
  This MR removes it.  Hooray.
  

• 4acf3a86
  by Ben Gamari at 2025-07-15T05:46:32-04:00

  configure: bump version to 9.15
  

• 45efaf71
  by Teo Camarasu at 2025-07-15T05:47:13-04:00

  rts/nonmovingGC: remove n_free
  
  We remove the nonmovingHeap.n_free variable.
  
  We wanted this to track the length of nonmovingHeap.free.
  But this isn't possible to do atomically.
  
  When this isn't accurate we can get a segfault by going past the end of
  the list.
  
  Instead, we just count the length of the list when we grab it in
  nonmovingPruneFreeSegment.
  
  Resolves #26186
  

• c635f164
  by Ben Gamari at 2025-07-15T14:05:54-04:00

  configure: Drop probing of ld.gold
  
  As noted in #25716, `gold` has been dropped from binutils-2.44.
  
  Fixes #25716.
  
  Metric Increase:
      size_hello_artifact_gzip
      size_hello_unicode_gzip
      ghc_prim_so
  

• 637bb538
  by Ben Gamari at 2025-07-15T14:05:55-04:00

  testsuite/recomp015: Ignore stderr
  
  This is necessary since ld.bfd complains
  that we don't have a .note.GNU-stack section,
  potentially resulting in an executable stack.

• d3cd4ec8
  by Wen Kokke at 2025-07-15T14:06:39-04:00

  Fix documentation for heap profile ID
  

• 73082769
  by Ben Gamari at 2025-07-15T16:56:38-04:00

  Bump win32-tarballs to v0.9

• 3b63b254
  by Ben Gamari at 2025-07-15T16:56:39-04:00

  rts/LoadArchive: Handle null terminated string tables
  
  As of `llvm-ar` now emits filename tables terminated with null
  characters instead of the usual POSIX `/\n` sequence.
  
  Fixes #26150.
  

• 195f6527
  by Tamar Christina at 2025-07-15T16:56:39-04:00

  rts: rename label so name doesn't conflict with param
  

• 63373b95
  by Tamar Christina at 2025-07-15T16:56:39-04:00

  rts: Handle API set symbol versioning conflicts
  

• 48e9aa3e
  by Tamar Christina at 2025-07-15T16:56:39-04:00

  rts: Mark API set symbols as HIDDEN and correct symbol type
  

• 959e827a
  by Tamar Christina at 2025-07-15T16:56:39-04:00

  rts: Implement WEAK EXTERNAL undef redirection by target symbol name
  

• 65f19293
  by Ben Gamari at 2025-07-15T16:56:39-04:00

  rts/LoadArchive: Handle string table entries terminated with /
  
  llvm-ar appears to terminate string table entries with `/\n` [1]. This
  matters in the case of thin archives, since the filename is used. In the
  past this worked since `llvm-ar` would produce archives with "small"
  filenames when possible. However, now it appears to always use the
  string table.
  
  [1] https://github.com/llvm/llvm-project/blob/bfb686bb5ba503e9386dc899e1ebbe2488e6a0a8/llvm/lib/Object/ArchiveWriter.cpp#L314
  

• 9cbb3ef5
  by Ben Gamari at 2025-07-15T16:56:39-04:00

  testsuite: Mark T12497 as fixed
  
  Thanks to the LLVM toolchain update.
  
  Closes #22694.
  

• 2854407e
  by Ben Gamari at 2025-07-15T16:56:39-04:00

  testsuite: Accept new output of T11223_link_order_a_b_2_fail on Windows
  
  The archive member number changed due to the fact that llvm-ar now uses a
  string table.
  

• 28439593
  by Ben Gamari at 2025-07-15T16:56:39-04:00

  rts/linker/PEi386: Implement IMAGE_REL_AMD64_SECREL
  
  This appears to now be used by libc++ as distributed by msys2.
  

• 2b053755
  by Tamar Christina at 2025-07-15T16:56:39-04:00

  rts: Cleanup merge resolution residue in lookupSymbolInDLL_PEi386 and make safe without dependent
  

• e8acd2e7
  by Wen Kokke at 2025-07-16T08:37:04-04:00

  Remove the `profile_id` parameter from various RTS functions.
  
  Various RTS functions took a `profile_id` parameter, intended to be used to
  distinguish parallel heap profile breakdowns (e.g., `-hT` and `-hi`). However,
  this feature was never implemented and the `profile_id` parameter was set to 0
  throughout the RTS. This commit removes the parameter but leaves the hardcoded
  profile ID in the functions that emit the encoded eventlog events as to not
  change the protocol.
  
  The affected functions are `traceHeapProfBegin`, `postHeapProfBegin`,
  `traceHeapProfSampleString`, `postHeapProfSampleString`,
  `traceHeapProfSampleCostCentre`, and `postHeapProfSampleCostCentre`.
  

• 76d392a2
  by Wen Kokke at 2025-07-16T08:37:04-04:00

  Make `traceHeapProfBegin` an init event.
  

• bbaa44a7
  by Peng Fan at 2025-07-16T16:50:42-04:00

  NCG/LA64: Support finer-grained DBAR hints
  
  For LA664 and newer uarchs, they have made finer granularity hints
  available:
  
      Bit4: ordering or completion (0: completion, 1: ordering)
      Bit3: barrier for previous read (0: true, 1: false)
      Bit2: barrier for previous write (0: true, 1: false)
      Bit1: barrier for succeeding read (0: true, 1: false)
      Bit0: barrier for succeeding write (0: true, 1: false)
  
  And not affect the existing models because other hints are treated
  as 'dbar 0' there.
  

• 7da86e16
  by Andreas Klebinger at 2025-07-16T16:51:25-04:00

  Disable -fprof-late-overloaded-calls for join points.
  
  Currently GHC considers cost centres as destructive to
  join contexts. Or in other words this is not considered valid:
  
      join f x = ...
      in
                ... -> scc<tick> jmp
  
  This makes the functionality of `-fprof-late-overloaded-calls` not feasible
  for join points in general. We used to try to work around this by putting the
  ticks on the rhs of the join point rather than around the jump. However beyond
  the loss of accuracy this was broken for recursive join points as we ended up
  with something like:
  
      rec-join f x = scc<tick> ... jmp f x
  
  Which similarly is not valid as the tick once again destroys the tail call.
  One might think we could limit ourselves to non-recursive tail calls and do
  something clever like:
  
    join f x = scc<tick> ...
    in ... jmp f x
  
  And sometimes this works! But sometimes the full rhs would look something like:
  
    join g x = ....
    join f x = scc<tick> ... -> jmp g x
  
  Which, would again no longer be valid. I believe in the long run we can make
  cost centre ticks non-destructive to join points. Or we could keep track of
  where we are/are not allowed to insert a cost centre. But in the short term I will
  simply disable the annotation of join calls under this flag.
  

• 7ee22fd5
  by ARATA Mizuki at 2025-07-17T06:05:30-04:00

  x86 NCG: Better lowering for shuffleFloatX4# and shuffleDoubleX2#
  
  The new implementation
  
  * make use of specialized instructions like (V)UNPCK{L,H}{PS,PD}, and
  * do not require -mavx.
  
  Close #26096
  
  Co-authored-by: sheaf <sam.derbyshire@gmail.com>
  

• c6cd2da1
  by Jappie Klooster at 2025-07-17T06:06:20-04:00

  Update interact docs to explain about buffering
  
  We need to tell the user to set to the
  appropriate buffer format.
  Otherwise, this function may get randomly stuck,
  or just behave confusingly.
  
  issue: https://gitlab.haskell.org/ghc/ghc/-/issues/26131
  
  NB, I'm running this with cabal *NOT* ghci. ghci messes with buffering anyway.
  
  ```haskell
  interaction :: String -> String
  interaction "jappie" = "hi"
  interaction "jakob" = "hello"
  interaction x = "unkown input: " <> x
  
  main :: IO ()
  main = interact  interaction
  ```
  so in my input (prefixed by `>`) I get:
  
  ```
  > jappie
  unkown input: jappie
  ```
  
  we confirmed later this was due to lack of \n matching.
  Anyway movnig on to more unexpected stuff:
  
  ```haskell
  main :: IO ()
  main = do
    interact  (concatMap interaction . lines)
  ```
  
  get's stuck forever.
  actually `^D` (ctrl+d) unstucks it and runs all input as expected.
  for example you can get:
  ```
  > sdfkds
  > fakdsf
  unkown input: sdfkdsunkown input: fakdsf
  ```
  
  This program works!
  ```haskell
  interaction :: String -> String
  interaction "jappie" = "hi \n"
  interaction "jakob" = "hello \n"
  interaction x = "unkown input: " <> x <> "\n"
  
  main :: IO ()
  main = do
    interact  (concatMap interaction . lines)
  ```
  the reason is that linebuffering is set for both in and output by default.
  so lines eats the input lines, and all the \n postfixes make sure the buffer
  is put out.
  

• 9fa590a6
  by Zubin Duggal at 2025-07-17T06:07:03-04:00

  fetch_gitlab: Ensure we copy users_guide.pdf and Haddock.pdf to the release docs directory
  
  Fixes #24093
  

• cc650b4b
  by Andrew Lelechenko at 2025-07-17T12:30:24-04:00

  Add Data.List.NonEmpty.mapMaybe
  
  As per https://github.com/haskell/core-libraries-committee/issues/337
  

• 360fa82c
  by Duncan Coutts at 2025-07-17T12:31:14-04:00

  base: Deprecate GHC.Weak.Finalize.runFinalizerBatch
  
  https://github.com/haskell/core-libraries-committee/issues/342
  

• f4e8466c
  by Alan Zimmerman at 2025-07-17T12:31:55-04:00

  EPA: Update exact printing based on GHC 9.14 tests
  
  As a result of migrating the GHC ghc-9.14 branch tests to
  ghc-exactprint in
  https://github.com/alanz/ghc-exactprint/tree/ghc-9.14, a couple of
  discrepancies were picked up
  
  - The opening paren for a DefaultDecl was printed in the wrong place
  - The import declaration level specifiers were not printed.
  
  This commit adds those fixes, and some tests for them.
  The tests brought to light that the ImportDecl ppr instance had not
  been updated for level specifiers, so it updates that too.
  

• 8b731e3c
  by Matthew Pickering at 2025-07-21T13:36:43-04:00

  level imports: Fix infinite loop with cyclic module imports
  
  I didn't anticipate that downsweep would run before we checked for
  cyclic imports. Therefore we need to use the reachability function which
  handles cyclic graphs.
  
  Fixes #26087
  

• d751a9f1
  by Pierre Thierry at 2025-07-21T13:37:28-04:00

  Fix documentation about deriving from generics
  

• f8d9d016
  by Andrew Lelechenko at 2025-07-22T21:13:28-04:00

  Fix issues with toRational for types capable to represent infinite and not-a-number values
  
  This commit fixes all of the following pitfalls:
  
  > toRational (read "Infinity" :: Double)
  179769313486231590772930519078902473361797697894230657273430081157732675805500963132708477322407536021120113879871393357658789768814416622492847430639474124377767893424865485276302219601246094119453082952085005768838150682342462881473913110540827237163350510684586298239947245938479716304835356329624224137216 % 1
  > toRational (read "NaN" :: Double)
  269653970229347386159395778618353710042696546841345985910145121736599013708251444699062715983611304031680170819807090036488184653221624933739271145959211186566651840137298227914453329401869141179179624428127508653257226023513694322210869665811240855745025766026879447359920868907719574457253034494436336205824 % 1
  
  > realToFrac (read "NaN" :: Double) -- With -O0
  Infinity
  > realToFrac (read "NaN" :: Double) -- With -O1
  NaN
  
  > realToFrac (read "NaN" :: Double) :: CDouble
  Infinity
  > realToFrac (read "NaN" :: CDouble) :: Double
  Infinity
  
  Implements https://github.com/haskell/core-libraries-committee/issues/338
  

• 5dabc718
  by Zubin Duggal at 2025-07-22T21:14:10-04:00

  haddock: Don't warn about missing link destinations for derived names.
  
  Fixes #26114
  

• 9c3a0937
  by Matthew Pickering at 2025-07-22T21:14:52-04:00

  template haskell: use a precise condition when implicitly lifting
  
  Implicit lifting corrects a level error by replacing references to `x`
  with `$(lift x)`, therefore you can use a level `n` binding at level `n
  + 1`, if it can be lifted.
  
  Therefore, we now have a precise check that the use level is 1 more than
  the bind level.
  
  Before this bug was not observable as you only had 0 and 1 contexts but
  it is easily evident when using explicit level imports.
  
  Fixes #26088
  

• 5144b22f
  by Andreas Klebinger at 2025-07-22T21:15:34-04:00

  Add since tag and more docs for do-clever-arg-eta-expansion
  
  Fixes #26113
  

• c865623b
  by Andreas Klebinger at 2025-07-22T21:15:34-04:00

  Add since tag for -fexpose-overloaded-unfoldings
  
  Fixes #26112
  

• 49a44ab7
  by Simon Hengel at 2025-07-23T17:59:55+07:00

  Refactor GHC.Driver.Errors.printMessages
  

• 84711c39
  by Simon Hengel at 2025-07-23T18:27:34+07:00

  Respect `-fdiagnostics-as-json` for error messages from pre-processors
  
  (fixes #25480)
  

• d046b5ab
  by Simon Hengel at 2025-07-24T06:12:05-04:00

  Include the rendered message in -fdiagnostics-as-json output
  
  This implements #26173.
  

• d2b89603
  by Ben Gamari at 2025-07-24T06:12:47-04:00

  rts/Interpreter: Factor out ctoi tuple info tables into data
  
  Instead of a massive case let's put this into data which we can reuse
  elsewhere.
  

• 4bc78496
  by Sebastian Graf at 2025-07-24T16:19:34-04:00

  CprAnal: Detect recursive newtypes (#25944)
  
  While `cprTransformDataConWork` handles recursive data con workers, it
  did not detect the case when a newtype is responsible for the recursion.
  This is now detected in the `Cast` case of `cprAnal`.
  
  The same reproducer made it clear that `isRecDataCon` lacked congruent
  handling for `AppTy` and `CastTy`, now fixed.
  
  Furthermore, the new repro case T25944 triggered this bug via an
  infinite loop in `cprFix`, caused by the infelicity in `isRecDataCon`.
  While it should be much less likely to trigger such an infinite loop now
  that `isRecDataCon` has been fixed, I made sure to abort the loop after
  10 iterations and emitting a warning instead.
  
  Fixes #25944.
  

• 0a583689
  by Sylvain Henry at 2025-07-24T16:20:26-04:00

  STM: don't create a transaction in the rhs of catchRetry# (#26028)
  
  We don't need to create a transaction for the rhs of (catchRetry#)
  because contrary to the lhs we don't need to abort it on retry. Moreover
  it is particularly harmful if we have code such as (#26028):
  
    let cN = readTVar vN >> retry
        tree = c1 `orElse` (c2 `orElse` (c3 `orElse` ...))
    atomically tree
  
  Because it will stack transactions for the rhss and the read-sets of all
  the transactions will be iteratively merged in O(n^2) after the
  execution of the most nested retry.
  

• a49eca26
  by Simon Peyton Jones at 2025-07-25T09:49:58+01:00

  Renaming around predicate types
  
  .. we were (as it turned out) abstracting over
  type-class selectors in SPECIALISATION rules!
  
  Wibble isEqPred
  

• f80375dd
  by Simon Peyton Jones at 2025-07-25T09:49:58+01:00

  Refactor of Specialise.hs
  
  This patch just tidies up `specHeader` a bit, removing one
  of its many results, and adding some comments.
  
  No change in behaviour.
  
  Also add a few more `HasDebugCallStack` contexts.
  

• 1bd12371
  by Simon Peyton Jones at 2025-07-25T09:49:58+01:00

  Improve treatment of SPECIALISE pragmas -- again!
  
  This MR does another major refactor of the way that SPECIALISE
  pragmas work, to fix #26115, #26116, #26117.
  
  * We now /always/ solve forall-constraints in an all-or-nothing way.
    See Note [Solving a Wanted forall-constraint] in GHC.Tc.Solver.Solve
  
    This means we might have unsolved quantified constraints, which need
    to be reported.  See `inert_insts` in `getUnsolvedInerts`.
  
  * I refactored the short-cut solver for type classes to work by
    recursively calling the solver rather than by having a little baby
    solver that kept being not clever enough.
    See Note [Shortcut solving] in GHC.Tc.Solver.Dict
  
  * I totally rewrote the desugaring of SPECIALISE pragmas, again.
    The new story is in Note [Desugaring new-form SPECIALISE pragmas]
    in GHC.HsToCore.Binds
  
    Both old-form and new-form SPECIALISE pragmas now route through the same
    function `dsSpec_help`.   The tricky function `decomposeRuleLhs` is now used only
    for user-written RULES, not for SPECIALISE pragmas.
  
  * I improved `solveOneFromTheOther` to account for rewriter sets. Previously
    it would solve a non-rewritten dict from a rewritten one.  For equalities
    we were already dealing with this, in
  
  Some incidental refactoring
  
  * A small refactor: `ebv_tcvs` in `EvBindsBar` now has a list of coercions, rather
    than a set of tyvars.  We just delay taking the free vars.
  
  * GHC.Core.FVs.exprFVs now returns /all/ free vars.
    Use `exprLocalFVs` for Local vars.
    Reason: I wanted another variant for /evidence/ variables.
  
  * Ues `EvId` in preference to `EvVar`.  (Evidence variables are always Ids.)
    Rename `isEvVar` to `isEvId`.
  
  * I moved `inert_safehask` out of `InertCans` and into `InertSet` where it
    more properly belongs.
  
  Compiler-perf changes:
    * There was a palpable bug (#26117) which this MR fixes in
      newWantedEvVar, which bypassed all the subtle overlapping-Given
      and shortcutting logic.  (See the new `newWantedEvVar`.)  Fixing this
      but leads to extra dictionary bindings; they are optimised away quickly
      but they made CoOpt_Read allocate 3.6% more.
  
    * Hpapily T15164 improves.
  
    * The net compiler-allocation change is 0.0%
  
  Metric Decrease:
      T15164
  Metric Increase:
      CoOpt_Read
      T12425
  

• 953fd8f1
  by Simon Peyton Jones at 2025-07-25T09:49:58+01:00

  Solve forall-constraints immediately, or not at all
  
  This MR refactors the constraint solver to solve forall-constraints immediately,
  rather than emitting an implication constraint to be solved later.
  
  The most immediate motivation was that when solving quantified constraints
  in SPECIALISE pragmas, we really really don't want to leave behind half-
  solved implications.  Also it's in tune with the approach of the new
  short-cut solver, which recursively invokes the solver.
  
  It /also/ saves quite a bit of plumbing; e.g
  
    - The `wl_implics` field of `WorkList` is gone,
  
    - The types of `solveSimpleWanteds` and friends are simplified.
  
    - An EvFun contains binding, rather than an EvBindsVar ref-cell that
      will in the future contain bindings.  That makes `evVarsOfTerm`
      simpler.  Much nicer.
  
  It also improves error messages a bit.
  
  All described in Note [Solving a Wanted forall-constraint] in
  GHC.Tc.Solver.Solve.
  
  One tiresome point: in the tricky case of `inferConstraintsCoerceBased`
  we make a forall-constraint.  This we /do/ want to partially solve, so
  we can infer a suitable context. (I'd be quite happy to force the user to
  write a context, bt I don't want to change behavior.)  So we want to generate
  an /implication/ constraint in `emitPredSpecConstraints` rather than a
  /forall-constraint/ as we were doing before.  Discussed in (WFA3) of
  the above Note.
  
  Incidental refactoring
  
  * `GHC.Tc.Deriv.Infer.inferConstraints` was consulting the state monad for
    the DerivEnv that the caller had just consulted.  Nicer to pass it as an
    argument I think, so I have done that.  No change in behaviour.
  

• 6921ab42
  by Simon Peyton Jones at 2025-07-25T09:49:58+01:00

  Remove duplicated code in Ast.hs for evTermFreeVars
  
  This is just a tidy up.
  

• 1165f587
  by Simon Peyton Jones at 2025-07-25T09:49:58+01:00

  Small tc-tracing changes only
  

• 0776ffe0
  by Simon Hengel at 2025-07-26T04:54:20-04:00

  Respect `-fdiagnostics-as-json` for core diagnostics (see #24113)
  

• cc1116e0
  by Andrew Lelechenko at 2025-07-26T04:55:01-04:00

  docs: add since pragma to Data.List.NonEmpty.mapMaybe
  

• ee2dc248
  by Simon Hengel at 2025-07-31T06:25:35-04:00

  Update comments on `OptKind` to reflect the code reality
  

• b029633a
  by Wen Kokke at 2025-07-31T06:26:21-04:00

  rts: Disable --eventlog-flush-interval unless compiled with -threaded.
  
  This commit fixes issue #26222:
  Using --eventlog-flush-interval with the non-threaded RTS leads to eventlog corruption.
  https://gitlab.haskell.org/ghc/ghc/-/issues/26222
  
  This commit makes three changes when code is compiled against the non-threaded RTS:
  
  1. It disables the --eventlog-flush-interval flag.
  2. It disables the documentation for the --eventlog-flush-interval flag.
  3. It disables the relevant state from RtsConfig and code from Timer.
  4. It updates the entry for --eventlog-flush-interval in the users guide.
  

• 31159f1d
  by Wen Kokke at 2025-07-31T06:26:21-04:00

  rts: Split T20006 into tests with and without -threaded
  

• 618687ef
  by Simon Hengel at 2025-07-31T06:27:03-04:00

  docs/users_guide/win32-dlls.rst: Remove references to `readline`
  

• 083e40f1
  by Rodrigo Mesquita at 2025-08-01T04:38:23-04:00

  debugger: Uniquely identify breakpoints by internal id
  
  Since b85b11994e0130ff2401dd4bbdf52330e0bcf776 (support inlining
  breakpoints), a breakpoint has been identified at runtime by *two* pairs
  of <module,index>.
  
  - The first, aka a 'BreakpointId', uniquely identifies a breakpoint in
    the source of a module by using the Tick index. A Tick index can index
    into ModBreaks.modBreaks_xxx to fetch source-level information about
    where that tick originated.
  
      - When a user specifies e.g. a line breakpoint using :break, we'll reverse
        engineer what a Tick index for that line
      - We update the `BreakArray` of that module (got from the
        LoaderState) at that tick index to `breakOn`.
      - A BCO we can stop at is headed by a BRK_FUN instruction. This
        instruction stores in an operand the `tick index` it is associated
        to. We look it up in the associated `BreakArray` (also an operand)
        and check wheter it was set to `breakOn`.
  
  - The second, aka the `ibi_info_mod` + `ibi_info_ix` of the
    `InternalBreakpointId`, uniquely index into the `imodBreaks_breakInfo`
    -- the information we gathered during code generation about the
    existing breakpoint *ocurrences*.
  
    - Note that with optimisation there may be many occurrences of the
      same source-tick-breakpoint across different modules. The
      `ibi_info_ix` is unique per occurrence, but the `bi_tick_ix` may be
      shared. See Note [Breakpoint identifiers] about this.
  
    - Note that besides the tick ids, info ids are also stored in
      `BRK_FUN` so the break handler can refer to the associated
      `CgBreakInfo`.
  
  In light of that, the driving changes come from the desire to have the
  info_id uniquely identify the breakpoint at runtime, and the source tick
  id being derived from it:
  
  - An InternalBreakpointId should uniquely identify a breakpoint just
    from the code-generation identifiers of `ibi_info_ix` and `ibi_info_mod`.
    So we drop `ibi_tick_mod` and `ibi_tick_ix`.
  - A BRK_FUN instruction need only record the "internal breakpoint id",
    not the tick-level id.
    So we drop the tick mod and tick index operands.
  - A BreakArray should be indexed by InternalBreakpointId rather than
    BreakpointId
  
  That means we need to do some more work when setting a breakpoint.
  Specifically, we need to figure out the internal ids (occurrences of a
  breakpoint) from the source-level BreakpointId we want to set the
  breakpoint at (recall :break refers to breaks at the source level).
  
  Besides this change being an improvement to the handling of breakpoints
  (it's clearer to have a single unique identifier than two competing
  ones), it unlocks the possibility of generating "internal" breakpoints
  during Cg (needed for #26042).
  It should also be easier to introduce multi-threaded-aware `BreakArrays`
  following this change (needed for #26064).
  
  Se also the new Note [ModBreaks vs InternalModBreaks]
  
  On i386-linux:
  
  -------------------------
  Metric Decrease:
      interpreter_steplocal
  -------------------------
  

• bf03bbaa
  by Simon Hengel at 2025-08-01T04:39:05-04:00

  Don't use MCDiagnostic for `ghcExit`
  
  This changes the error message of `ghcExit` from
  
  ```
  <no location info>: error:
  Compilation had errors
  
  ```
  to
  ```
  
  Compilation had errors
  
  ```
  

• a889ec75
  by Simon Hengel at 2025-08-01T04:39:05-04:00

  Respect `-fdiagnostics-as-json` for driver diagnostics (see #24113)
  

• 81577fe7
  by Ben Gamari at 2025-08-02T04:29:39-04:00

  configure: Allow override of CrossCompiling
  
  As noted in #26236, the current inference logic is a bit simplistic. In
  particular, there are many cases (e.g. building for a new libc) where
  the target and host triples may differ yet we are still able to run the
  produced artifacts as native code.
  
  Closes #26236.
  

• 01136779
  by Andreas Klebinger at 2025-08-02T04:30:20-04:00

  rts: Support COFF BigObj files in archives.
  

• 1f9e4f54
  by Stephen Morgan at 2025-08-03T15:14:08+10:00

  refactor: Modify Data.List.sortOn to use (>) instead of compare. (#26184)
  
  This lets a more efficient (>) operation be used if one exists.
  
  This is technically a breaking change for malformed Ord instances, where
  x > y is not equivalent to compare x y == GT.
  
  Discussed by the CLC in issue #332: https://github.com/haskell/core-libraries-committee/issues/332
  

• 4f6bc9cf
  by fendor at 2025-08-04T17:50:06-04:00

  Revert "base: Expose Backtraces constructor and fields"
  
  This reverts commit 17db44c5b32fff82ea988fa4f1a233d1a27bdf57.
  

• bcdec657
  by Zubin Duggal at 2025-08-05T10:37:29+05:30

  compiler: Export a version of `newNameCache` that is not prone to footguns.
  `newNameCache` must be initialized with both a non-"reserved" unique tag, as well
  as a list of known key names. Failing to do so results in hard to debug unique conflicts.
  
  It is difficult for API users to tell which unique tags are safe to use. So instead of leaving
  this up to the user to decide, we now export a version of `newNameCache` which uses a guaranteed
  non-reserved unique tag. In fact, this is now the way the unique tag is initialized for all invocations
  of the compiler.
  
  The original version of `newNameCache` is now exported as `newNameCache'` for advanced users.
  
  We also deprecate `initNameCache` as it is also prone to footguns and is completely subsumed in
  functionality by `newNameCache` and `newNameCache'`.
  
  Fixes #26135 and #26055
  

• 57d3b4a8
  by Andrew Lelechenko at 2025-08-05T18:36:31-04:00

  hadrian: bump Stackage snapshot to LTS 24.2 / GHC 9.10.2
  
  In line with #25693 we should use GHC 9.10 as a boot compiler,
  while Hadrian stack.yaml was stuck on GHC 9.6.
  

• c2a78cea
  by Peng Fan at 2025-08-05T18:37:27-04:00

  NCG/LA64: implement atomic write with finer-grained DBAR hints
  
  Signed-off-by: Peng Fan <fanpeng@loongson.cn>
  

• 95231c8e
  by Teo Camarasu at 2025-08-06T08:35:58-04:00

  CODEOWNERS: add CLC as codeowner of base
  
  We also remove hvr, since I think he is no longer active

• 77df0ded
  by Andrew Lelechenko at 2025-08-06T08:36:39-04:00

  Bump submodule text to 2.1.3
  

• 8af260d0
  by Nikolaos Chatzikonstantinou at 2025-08-06T08:37:23-04:00

  docs: fix internal import in getopt examples
  
  This external-facing doc example shouldn't mention GHC internals when
  using 'fromMaybe'.
  

• 69cc16ca
  by Marc Scholten at 2025-08-06T15:51:28-04:00

  README: Add note on ghc.nix
  

• 93a2f450
  by Daniel Díaz at 2025-08-06T15:52:14-04:00

  Link to the "Strict Bindings" docs from the linear types docs
  
  Strict Bidings are relevant for the kinds of multiplicity annotations
  linear lets support.
  

• 246b7853
  by Matthew Pickering at 2025-08-07T06:58:30-04:00

  level imports: Check the level of exported identifiers
  
  The level imports specification states that exported identifiers have to
  be at level 0. This patch adds the requird level checks that all
  explicitly mentioned identifiers occur at level 0.
  
  For implicit export specifications (T(..) and module B), only level 0
  identifiers are selected for re-export.
  
  ghc-proposal: https://github.com/ghc-proposals/ghc-proposals/pull/705
  
  Fixes #26090
  

• 358bc4fc
  by fendor at 2025-08-07T06:59:12-04:00

  Bump GHC on darwin CI to 9.10.1
  

• 1903ae35
  by Matthew Pickering at 2025-08-07T12:21:10+01:00

  ipe: Place strings and metadata into specific .ipe section
  
  By placing the .ipe metadata into a specific section it can be stripped
  from the final binary if desired.
  
  ```
  objcopy --remove-section .ipe <binary>
  upx <binary>
  ```
  
  Towards #21766
  

• c80dd91c
  by Matthew Pickering at 2025-08-07T12:22:42+01:00

  ipe: Place magic word at the start of entries in the .ipe section
  
  The magic word "IPE\nIPE\n" is placed at the start of .ipe sections,
  then if the section is stripped, we can check whether the section starts
  with the magic word or not to determine whether there is metadata
  present or not.
  
  Towards #21766
  

• cab42666
  by Matthew Pickering at 2025-08-07T12:22:42+01:00

  ipe: Use stable IDs for IPE entries
  
  IPEs have historically been indexed and reported by their address.
  This makes it impossible to compare profiles between runs, since the
  addresses may change (due to ASLR) and also makes it tricky to separate
  out the IPE map from the binary.
  
  This small patch adds a stable identifier for each IPE entry.
  
  The stable identifier is a single 64 bit word. The high-bits are a
  per-module identifier and the low bits identify which entry in each
  module.
  
  1. When a node is added into the IPE buffer it is assigned a unique
     identifier from an incrementing global counter.
  2. Each entry already has an index by it's position in the
     `IpeBufferListNode`.
  
  The two are combined together by the `IPE_ENTRY_KEY` macro.
  
  Info table profiling uses the stable identifier rather than the address
  of the info table.
  
  The benefits of this change are:
  
  * Profiles from different runs can be easily compared
  * The metadata can be extracted from the binary (via the eventlog for
    example) and then stripped from the executable.
  
  Fixes #21766
  

• 2860a9a5
  by Simon Peyton Jones at 2025-08-07T20:29:18-04:00

  In TcSShortCut, typechecker plugins should get empty Givens
  
  Solving in TcShortCut mode means /ignoring the Givens/. So we
  should not pass them to typechecker plugins!
  
  Fixes #26258.
  
  This is a fixup to the earlier MR:
  
      commit 1bd12371feacc52394a0e660ef9349f9e8ee1c06
      Author: Simon Peyton Jones <simon.peytonjones@gmail.com>
      Date:   Mon Jul 21 10:04:49 2025 +0100
  
          Improve treatment of SPECIALISE pragmas -- again!
  

• 2157db2d
  by sterni at 2025-08-08T15:32:39-04:00

  hadrian: enable terminfo if --with-curses-* flags are given
  
  The GHC make build system used to support WITH_TERMINFO in ghc.mk which
  allowed controlling whether to build GHC with terminfo or not. hadrian
  has replaced this with a system where this is effectively controlled by
  the cross-compiling setting (the default WITH_TERMINFO value was bassed
  on CrossCompiling, iirc).
  
  This behavior is undesireable in some cases and there is not really a
  good way to work around it. Especially for downstream packagers,
  modifying this via UserSettings is not really feasible since such a
  source file has to be kept in sync with Settings/Default.hs manually
  since it can't import Settings.Default or any predefined Flavour
  definitions.
  
  To avoid having to add a new setting to cfg/system.config and/or a new
  configure flag (though I'm happy to implement both if required), I've
  chosen to take --with-curses-* being set explicitly as an indication
  that the user wants to have terminfo enabled. This would work for
  Nixpkgs which sets these flags [1] as well as haskell.nix [2] (which
  goes to some extreme measures [3] [4] to force terminfo in all scenarios).
  
  In general, I'm an advocate for making the GHC build be the same for
  native and cross insofar it is possible since it makes packaging GHC and
  Haskell related things while still supporting cross much less
  compilicated. A more minimal GHC with reduced dependencies should
  probably be a specific flavor, not the default.
  
  Partially addresses #26288 by forcing terminfo to be built if the user
  explicitly passes configure flags related to it. However, it isn't built
  by default when cross-compiling yet nor is there an explicit way to
  control the package being built.
  
  [1]: https://github.com/NixOS/nixpkgs/blob/3a7266fcefcb9ce353df49ba3f292d06443760bb/pkgs/development/compilers/ghc/common-hadrian.nix#L513-L515
  [2]: https://github.com/input-output-hk/haskell.nix/blob/6eaafcdf04bab7be745d1aa4f74d2cc85700042b/compiler/ghc/default.nix#L185
  [3]: https://github.com/input-output-hk/haskell.nix/blob/6eaafcdf04bab7be745d1aa4f74d2cc85700042b/compiler/ghc/default.nix#L678-L682
  [4]: https://github.com/input-output-hk/haskell.nix/blob/6eaafcdf04bab7be745d1aa4f74d2cc85700042b/compiler/ghc/default.nix#L772-L773
  

• b3c31488
  by David Feuer at 2025-08-08T15:33:21-04:00

  Add default QuasiQuoters
  
  Add `defaultQuasiQuoter` and `namedDefaultQuasiQuoter` to make it easier
  to write `QuasiQuoters` that give helpful error messages when they're
  used in inappropriate contexts.
  
  Closes #24434.
  

• 03555ed8
  by Sylvain Henry at 2025-08-10T22:20:57-04:00

  Handle non-fractional CmmFloats in Cmm's CBE (#26229)
  
  Since f8d9d016305be355f518c141f6c6d4826f2de9a2, toRational for Float and
  Double converts float's infinity and NaN into Rational's infinity and
  NaN (respectively 1%0 and 0%0).
  
  Cmm CommonBlockEliminator hashing function needs to take these values
  into account as they can appear as literals now. See added testcase.
  

• 6c956af3
  by J. Ryan Stinnett at 2025-08-10T22:21:42-04:00

  Fix extensions list in `DoAndIfThenElse` docs
  

• 6dc420b1
  by J. Ryan Stinnett at 2025-08-10T22:21:42-04:00

  Document status of `RelaxedPolyRec` extension
  
  This adds a brief extension page explaining the status of the
  `RelaxedPolyRec` extension. The behaviour of this mode is already
  explained elsewhere, so this page is mainly for completeness so that
  various lists of extensions have somewhere to point to for this flag.
  
  Fixes #18630
  

• 18036d52
  by Simon Peyton Jones at 2025-08-11T11:31:20-04:00

  Take more care in zonkEqTypes on AppTy/AppTy
  
  This patch fixes #26256.
  
  See Note [zonkEqTypes and the PKTI] in GHC.Tc.Solver.Equality
  

• c8d76a29
  by Zubin Duggal at 2025-08-11T11:32:02-04:00

  ci: upgrade bootstrap compiler on windows to 9.10.1
  

• 34fc50c1
  by Ben Gamari at 2025-08-11T13:36:25-04:00

  Kill IOPort#
  
  This type is unnecessary, having been superceded by `MVar` and a rework
  of WinIO's blocking logic.
  
  See #20947.
  
  See https://github.com/haskell/core-libraries-committee/issues/213.
  

• 56b32c5a
  by sheaf at 2025-08-12T10:00:19-04:00

  Improve deep subsumption
  
  This commit improves the DeepSubsumption sub-typing implementation
  in GHC.Tc.Utils.Unify.tc_sub_type_deep by being less eager to fall back
  to unification.
  
  For example, we now are properly able to prove the subtyping relationship
  
    ((∀ a. a->a) -> Int) -> Bool  <=  β[tau] Bool
  
  for an unfilled metavariable β. In this case (with an AppTy on the right),
  we used to fall back to unification. No longer: now, given that the LHS
  is a FunTy and that the RHS is a deep rho type (does not need any instantiation),
  we try to make the RHS into a FunTy, viz.
  
    β := (->) γ
  
  We can then continue using covariance & contravariance of the function
  arrow, which allows us to prove the subtyping relationship, instead of
  trying to unify which would cause us to error out with:
  
    Couldn't match expected type ‘β’ with actual type ‘(->) ((∀ a. a -> a) -> Int)
  
  See Note [FunTy vs non-FunTy case in tc_sub_type_deep] in GHC.Tc.Utils.Unify.
  
  The other main improvement in this patch concerns type inference.
  The main subsumption logic happens (before & after this patch) in
  GHC.Tc.Gen.App.checkResultTy. However, before this patch, all of the
  DeepSubsumption logic only kicked in in 'check' mode, not in 'infer' mode.
  
  This patch adds deep instantiation in the 'infer' mode of checkResultTy
  when we are doing deep subsumption, which allows us to accept programs
  such as:
  
    f :: Int -> (forall a. a->a)
    g :: Int -> Bool -> Bool
  
    test1 b =
      case b of
        True  -> f
        False -> g
    test2 b =
      case b of
        True  -> g
        False -> f
  
  See Note [Deeply instantiate in checkResultTy when inferring].
  
  Finally, we add representation-polymorphism checks to ensure that the
  lambda abstractions we introduce when doing subsumption obey the
  representation polymorphism invariants of Note [Representation polymorphism invariants]
  in GHC.Core. See Note [FunTy vs FunTy case in tc_sub_type_deep].
  This is accompanied by a courtesy change to `(<.>) :: HsWrapper -> HsWrapper -> HsWrapper`,
  adding the equation:
  
    WpCast c1 <.> WpCast c2 = WpCast (c1 `mkTransCo` c2)
  
  This is useful because mkWpFun does not introduce an eta-expansion when
  both of the argument & result wrappers are casts; so this change allows
  us to avoid introducing lambda abstractions when casts suffice.
  
  Fixes #26225
  

• d175aff8
  by Sylvain Henry at 2025-08-12T10:01:31-04:00

  Add regression test for #18619
  

• a3983a26
  by Sylvain Henry at 2025-08-12T10:02:20-04:00

  RTS: remove some TSAN annotations (#20464)
  
  Use RELAXED_LOAD_ALWAYS macro instead.
  

• 0434af81
  by Ben Gamari at 2025-08-12T10:03:02-04:00

  Bump time submodule to 1.15
  
  Also required bumps of Cabal, directory, and hpc.
  

• 62899117
  by Florian Ragwitz at 2025-08-13T21:01:34-04:00

  Extend record-selector usage ticking to all binds using a record field
  
  This extends the previous handling of ticking for RecordWildCards and
  NamedFieldPuns to all var bindings that involve record selectors.
  
  Note that certain patterns such as `Foo{foo = 42}` will currently not tick the
  `foo` selector, as ticking is triggered by `HsVar`s.
  
  Closes #26191.
  

• b37b3af7
  by Florian Ragwitz at 2025-08-13T21:01:34-04:00

  Add release notes for 9.16.1 and move description of latest HPC changes there.
  

• a5e4b7d9
  by Ben Gamari at 2025-08-13T21:02:18-04:00

  rts: Clarify rationale for undefined atomic wrappers
  
  Since c06e3f46d24ef69f3a3d794f5f604cb8c2a40cbc the RTS has declared
  various atomic operation wrappers defined by ghc-internal as undefined.
  While the rationale for this isn't clear from the commit message, I
  believe that this is necessary due to the unregisterised backend.
  Specifically, the code generator will reference these symbols when
  compiling RTS Cmm sources.
  

• 50842f83
  by Andreas Klebinger at 2025-08-13T21:03:01-04:00

  Make unexpected LLVM versions a warning rather than an error.
  
  Typically a newer LLVM version *will* work so erroring out if
  a user uses a newer LLVM version is too aggressive.
  
  Fixes #25915
  

• c91e2650
  by fendor at 2025-08-13T21:03:43-04:00

  Store `StackTrace` and `StackSnapshot` in `Backtraces`
  
  Instead of decoding the stack traces when collecting the `Backtraces`,
  defer this decoding until actually showing the `Backtraces`.
  This allows users to customise how `Backtraces` are displayed by
  using a custom implementation of `displayExceptionWithInfo`, overwriting
  the default implementation for `Backtraces` (`displayBacktraces`).
  

• dee28cdd
  by fendor at 2025-08-13T21:03:43-04:00

  Allow users to customise the collection of exception annotations
  
  Add a global `CollectExceptionAnnotationMechanism` which determines how
  `ExceptionAnnotation`s are collected upon throwing an `Exception`.
  
  This API is exposed via `ghc-experimental`.
  
  By overriding how we collect `Backtraces`, we can control how the
  `Backtraces` are displayed to the user by newtyping `Backtraces` and
  giving a different instance for `ExceptionAnnotation`.
  
  A concrete use-case for this feature is allowing us to experiment with
  alternative stack decoders, without having to modify `base`, which take
  additional information from the stack frames.
  
  This commit does not modify how `Backtraces` are currently
  collected or displayed.
  

• 66024722
  by fendor at 2025-08-13T21:03:43-04:00

  Expose Backtraces internals from ghc-experimental
  
  Additionally, expose the same API `base:Control.Exception.Backtrace`
  to make it easier to use as a drop-in replacement.
  

• a766286f
  by Reed Mullanix at 2025-08-13T21:04:36-04:00

  ghc-internal: Fix naturalAndNot for NB/NS case
  
  When the first argument to `naturalAndNot` is larger than a `Word` and the second is `Word`-sized, `naturalAndNot` will truncate the
  result:
  
  ```
  >>> naturalAndNot ((2 ^ 65) .|. (2 ^ 3)) (2 ^ 3)
  0
  ```
  
  In contrast, `naturalAndNot` does not truncate when both arguments are larger than a `Word`, so this appears to be a bug.
  Luckily, the fix is pretty easy: we just need to call `bigNatAndNotWord#` instead of truncating.
  
  Fixes #26230
  

• 3506fa7d
  by Simon Hengel at 2025-08-13T21:05:18-04:00

  Report -pgms as a deprecated flag
  
  (instead of reporting an unspecific warning)
  
  Before:
  
      on the commandline: warning:
          Object splitting was removed in GHC 8.8
  
  After:
  
      on the commandline: warning: [GHC-53692] [-Wdeprecated-flags]
          -pgms is deprecated: Object splitting was removed in GHC 8.8
  

• 51c701fe
  by Zubin Duggal at 2025-08-13T21:06:00-04:00

  testsuite: Be more permissive when filtering out GNU_PROPERTY_TYPE linker warnings
  
  The warning text is slightly different with ld.bfd.
  
  Fixes #26249
  

• dfe6f464
  by Simon Hengel at 2025-08-13T21:06:43-04:00

  Refactoring: Don't misuse `MCDiagnostic` for lint messages
  
  `MCDiagnostic` is meant to be used for compiler diagnostics.
  
  Any code that creates `MCDiagnostic` directly, without going through
  `GHC.Driver.Errors.printMessage`, side steps `-fdiagnostics-as-json`
  (see e.g. !14475, !14492 !14548).
  
  To avoid this in the future I want to control more narrowly who creates
  `MCDiagnostic` (see #24113).
  
  Some parts of the compiler use `MCDiagnostic` purely for formatting
  purposes, without creating any real compiler diagnostics.  This change
  introduces a helper function, `formatDiagnostic`, that can be used in
  such cases instead of constructing `MCDiagnostic`.
  

• a8b2fbae
  by Teo Camarasu at 2025-08-13T21:07:24-04:00

  rts: ensure MessageBlackHole.link is always a valid closure
  
  We turn a MessageBlackHole into an StgInd in wakeBlockingQueue().
  Therefore it's important that the link field, which becomes the
  indirection field, always points to a valid closure.
  
  It's unclear whether it's currently possible for the previous behaviour
  to lead to a crash, but it's good to be consistent about this invariant nonetheless.
  
  Co-authored-by: Andreas Klebinger <klebinger.andreas@gmx.at>
  

• 4021181e
  by Teo Camarasu at 2025-08-13T21:07:24-04:00

  rts: spin if we see a WHITEHOLE in messageBlackHole
  
  When a BLACKHOLE gets cancelled in raiseAsync, we indirect to a THUNK.
  GC can then shortcut this, replacing our BLACKHOLE with a fresh THUNK.
  
  This THUNK is not guaranteed to have a valid indirectee field.
  
  If at the same time, a message intended for the previous BLACKHOLE is
  processed and concurrently we BLACKHOLE the THUNK, thus temporarily
  turning it into a WHITEHOLE, we can get a segfault, since we look at the
  undefined indirectee field of the THUNK
  
  The fix is simple: spin if we see a WHITEHOLE, and it will soon be
  replaced with a valid BLACKHOLE.
  
  Resolves #26205
  

• 1107af89
  by Oleg Grenrus at 2025-08-13T21:08:06-04:00

  Allow defining HasField instances for naughty fields
  
  Resolves #26295
  
  ... as HasField solver doesn't solve for fields with "naughty"
  selectors, we could as well allow defining HasField instances for these
  fields.
  

• 020e7587
  by Sylvain Henry at 2025-08-13T21:09:00-04:00

  Fix Data.List unqualified import warning
  

• fd811ded
  by Simon Peyton Jones at 2025-08-14T17:56:47-04:00

  Make injecting implicit bindings into its own pass
  
  Previously we were injecting "impliicit bindings" (data constructor
  worker and wrappers etc)
  
    - both at the end of CoreTidy,
    - and at the start of CorePrep
  
  This is unpleasant and confusing.  This patch puts it it its own pass,
  addImplicitBinds, which runs between the two.
  
  The function `GHC.CoreToStg.AddImplicitBinds.addImplicitBinds` now takes /all/
  TyCons, not just the ones for algebraic data types.  That change ripples
  through to
       - corePrepPgm
       - doCodeGen
       - byteCodeGen
  All take [TyCon] which includes all TyCons
  

• 9bd7fcc5
  by Simon Peyton Jones at 2025-08-14T17:56:47-04:00

  Implement unary classes
  
  The big change is described exhaustively in
  
     Note [Unary class magic] in GHC.Core.TyCon
  
  Other changes
  
  * We never unbox class dictionaries in worker/wrapper.  This has been true for some
    time now, but the logic is now centralised in functions in
    GHC.Core.Opt.WorkWrap.Utils, namely `canUnboxTyCon`, and `canUnboxArg`
    See Note [Do not unbox class dictionaries] in GHC.Core.Opt.WorkWrap.Utils.
  
  * Refactored the `notWorthFloating` logic in GHc.Core.Opt.SetLevels.
    I can't remember if I actually changed any behaviour here, but if so it's
    only in a corner cases.
  
  * Fixed a bug in `GHC.Core.TyCon.isEnumerationTyCon`, which was wrongly returning
    True for (##).
  
  * Remove redundant Role argument to `liftCoSubstWithEx`.  It was always
    Representational.
  
  * I refactored evidence generation in the constraint solver:
    * Made GHC.Tc.Types.Evidence contain better abstactions for evidence
      generation.
    * I deleted the file `GHC.Tc.Types.EvTerm` and merged its (small) contents
      elsewhere. It wasn't paying its way.
    * Made evidence for implicit parameters go via a proper abstraction.
  
  * Fix inlineBoringOk; see (IB6) in Note [inlineBoringOk]
    This fixes a slowdown in `countdownEffectfulDynLocal`
    in the `effectful` library.
  
  Smaller things
  
  * Rename `isDataTyCon` to `isBoxedDataTyCon`.
  * GHC.Core.Corecion.liftCoSubstWithEx was only called with Representational role,
    so I baked that into the function and removed the argument.
  * Get rid of `GHC.Core.TyCon.tyConSingleAlgDataCon_maybe` in favour of calling
    `not isNewTyCon` at the call sites; more explicit.
  * Refatored `GHC.Core.TyCon.isInjectiveTyCon`; but I don't think I changed its
    behaviour
  * Moved `decomposeIPPred` to GHC.Core.Predicate
  
  Compile time performance changes:
    geo. mean        +0.1%
      minimum        -6.8%
      maximum       +14.4%
  
  The +14% one is in T21839c, where it seems that a bit more inlining
  is taking place.  That seems acceptable; and the average change is small
  
  Metric Decrease:
      LargeRecord
      T12227
      T12707
      T16577
      T21839r
      T5642
  Metric Increase:
      T15164
      T21839c
      T3294
      T5321FD
      T5321Fun
      WWRec
  

• b4075d71
  by Simon Peyton Jones at 2025-08-14T17:56:47-04:00

  Slight improvement to pre/postInlineUnconditionally
  
  Avoids an extra simplifier iteration
  

• 9e443596
  by Simon Peyton Jones at 2025-08-14T17:56:47-04:00

  Fix a long-standing assertion error in normSplitTyConApp_maybe
  

• 91310ad0
  by Simon Peyton Jones at 2025-08-14T17:56:47-04:00

  Add comment to coercion optimiser
  

• 5b841d82
  by Teo Camarasu at 2025-08-14T17:57:56-04:00

  template-haskell: move some identifiers from ghc-internal to template-haskell
  
  These identifiers are not used internally by the compiler. Therefore we
  have no reason for them to be in ghc-internal.
  
  By moving them to template-haskell, we benefit from it being easier to
  change them and we avoid having to build them in stage0.
  
  Resolves #26048
  

• 33e2c7e5
  by Teo Camarasu at 2025-08-14T17:57:56-04:00

  template-haskell: transfer $infix note to public module
  
  This Haddock note should be in the public facing module
  

• 2a411fc4
  by Sylvain Henry at 2025-08-14T17:59:09-04:00

  JS: export HEAP8 symbol (#26290)
  
  Newer Emscripten requires this.
  

• 248f78ca
  by Ben Gamari at 2025-08-14T17:59:51-04:00

  users-guide: Drop the THREAD_RUNNABLE event
  
  As of f361281c89fbce42865d8b8b27b0957205366186 it is no longer emitted.

• 706d33e3
  by Recursion Ninja at 2025-08-15T04:12:12-04:00

  Resolving issues #20645 and #26109
  
  Correctly sign extending and casting smaller bit width types for LLVM operations:
  
    - bitReverse8#
    - bitReverse16#
    - bitReverse32#
    - byteSwap16#
    - byteSwap32#
    - pdep8#
    - pdep16#
    - pext8#
    - pext16#
  

• 1cdc6f46
  by Cheng Shao at 2025-08-15T04:12:56-04:00

  hadrian: enforce have_llvm=False for wasm32/js
  
  This patch fixes hadrian to always pass have_llvm=False to the
  testsuite driver for wasm32/js targets. These targets don't really
  support the LLVM backend, and the optllvm test way doesn't work. We
  used to special-case wasm32/js to avoid auto-adding optllvm way in
  testsuite/config/ghc, but this is still problematic if someone writes
  a new LLVM-related test and uses something like when(have_llvm(),
  extra_ways(["optllvm"])). So better just enforce have_llvm=False for
  these targets here.
  

• ca03226d
  by Ben Gamari at 2025-08-18T13:43:20+00:00

  configure: Allow use of LLVM 20

• 783cd7d6
  by Cheng Shao at 2025-08-18T20:13:14-04:00

  compiler: use `UniqMap` instead of `Map` for `BCEnv` in bytecode compiler
  
  The bytecode compiler maintains a `BCEnv` which was previously `Map Id
  StackDepth`. Given `Id` is `Uniquable`, we might as well use `UniqMap`
  here as a more efficient data structure, hence this patch.
  
  Co-authored-by: Codex <codex@openai.com>
  

• 58e46da9
  by fendor at 2025-08-18T20:13:56-04:00

  rts: Strip lower three bits when hashing Word instead of lower eight bits
  

• 45dbfa23
  by Cheng Shao at 2025-08-18T20:14:37-04:00

  libffi: update to 3.5.2
  
  Bumps libffi submodule.
  

• 54be78ef
  by Ben Gamari at 2025-08-19T16:28:05-04:00

  testsuite: Fix T20006b
  
  This test is supposed to fail for non-threaded ways yet it
  was previously marked as only failing in `normal`.
  Fix this.

• f4bac607
  by Simon Peyton Jones at 2025-08-19T16:28:47-04:00

  Take yet more care with reporting redundant constraints
  
  This small patch fixes #25992, which relates to reporting redundant
  constraints on default-method declarations.
  
  See (TRC5) in Note [Tracking redundant constraints]
  

• ab130fec
  by fendor at 2025-08-19T16:29:29-04:00

  Bump dependencies of hadrian-bootstrap-gen to use GHC 9.6.7
  

• 6d02ac6f
  by fendor at 2025-08-19T16:29:29-04:00

  Bump required GHC version for test-bootstrap jobs to 9.10.1
  
  Include test-bootstrap job for GHC 9.12.2.
  
  Update hadrian bootstrap plans use GHC 9.10 and 9.12
  
  Remove older GHC bootstrap configurations.
  We require at least GHC 9.10.1 to build GHC.
  
  Adds plans for:
  
  * 9.10.1
  * 9.10.2
  * 9.12.1
  * 9.12.2
  

• 9e857171
  by Brandon Chinn at 2025-08-20T11:47:46-04:00

  Don't warn unused-imports with used generated imports
  
  Fixes #21730
  
  * The old notion of "implicit" import has been renamed to "generated". See Note [Generated imports] in GHC.Hs.ImpExp.
  
  * ImportMap now keeps track of generated and user-written imports separately. This avoids the fake SrcSpan we used to give the implicit Prelude import, and the hack that went with it.
  
  * -ddump-minimal-imports now considers generated imports (but still only
    warns on + prints user-written imports)
  
  * bestImport considers generated imports to take priority over user-written imports.
  

• 9fb3bad4
  by Ben Gamari at 2025-08-20T11:48:31-04:00

  mailmap: Use ben@well-typed.com more liberally
  
  Nearly all of this work was done while working for Well-Typed.
  

• 774fec37
  by Ben Gamari at 2025-08-20T11:49:15-04:00

  Add primop to annotate the call stack with arbitrary data
  
  We introduce a new primop `annotateStack#` which allows us to push
  arbitrary data onto the call-stack.
  This allows us to extract the data later when decoding the stack, for
  example when an exception is thrown, showing more information to the
  user without having to annotate the full call-stack with `HasCallStack`
  constraints.
  
  A new stack frame value is introduced `AnnFrame`, which consists of
  nothing but a generic payload.
  
  The primop has a small wrapper API that allows users to annotate their
  call-stack in programs.
  There is a pure API and an IO-based one. The former is a little bit
  dubious, as it affects the evaluation of a program, so use with care.
  The latter is "safe", as it doesn't change the evaluation of the
  program.
  
  The stack annotation mechanism is similarly implemented to the
  `ExceptionAnnotation` and `Exception`, there is a typeclass to indicate
  something can be pushed onto the call-stack and all values are wrapped
  in the existential `SomeStackAnnotation`, which recover the type of the
  annotation payload.
  
  There is currently no builtin way to show the stack annotations when
  `Backtraces` are displayed (i.e., when showing stack traces to the user),
  which we will address in a follow-up MR.
  
  -------------------------
  Metric Increase:
      ghc_experimental_so
  -------------------------
  
  We increase the size of the package, so this is not unreasonable.
  
  Co-Authored-By: fendor <fendor@posteo.de>
  Co-Authored-By: Ben Gamari <bgamari.foss@gmail.com>
  

• fdfa3892
  by Ben Gamari at 2025-08-20T11:49:57-04:00

  testsuite: Add regression test for #24606
  

• 39b2e382
  by Cheng Shao at 2025-08-20T11:50:40-04:00

  compiler: only use `Name` instead of `Id` in `SptEntry`
  
  As a part of #26298, this patch refactors `SptEntry` to only carry a
  `Name` instead of `Id`: we do not care about extra information like
  caffyness or type at all in any static pointer related codegen logic.
  This is necessary to make `SptEntry` serializable, as a part of the
  grand plan of serializable bytecode.
  
  Co-authored-by: Codex <codex@openai.com>
  

• 276f8ea8
  by Vekhir -- at 2025-08-20T11:51:35-04:00

  Bump Cabal dependency

• 0b9c7437
  by Zubin Duggal at 2025-08-20T11:52:18-04:00

  ci: Teach ci.sh to fetch FreeBSD artifacts from ghcup unofficial bindists and bootstrap compiler on FreeBSD to 9.10.1
  
  Also refactor fetch_ghc logic in ci.sh, renaming the GHC_VERSION enviorment configuration variable to FETCH_GHC_VERSION,
  making it clear that it is intended for use on platforms like Windows and FreeBSD where we don't want to use the GHC
  excecutable from the platform environment and instead need to download and install GHC-$FETCH_GHC_VERSION from a release
  bindist.
  
  Fixes #26296
  

• b2914797
  by Cheng Shao at 2025-08-20T11:53:00-04:00

  driver: use UniqSet for hiddenModules in DynFlags/FinderOpts
  
  This patch replaces Set ModuleName with UniqSet ModuleName in
  DynFlags.hiddenModules and FinderOpts.finder_hiddenModules for
  improved efficiency.
  
  Co-authored-by: Codex <codex@openai.com>
  

• 0335d899
  by Cheng Shao at 2025-08-20T11:53:00-04:00

  driver: use UniqMap ModuleName in the finder
  
  This patch replaces Map ModuleName with UniqMap ModuleName in the
  finder for improved efficiency.
  
  Co-authored-by: Codex <codex@openai.com>
  

• 91f4faaa
  by Cheng Shao at 2025-08-20T11:53:43-04:00

  configure: check python3 version and require minimal 3.7
  
  Since !9515, the testsuite driver requires python3 version to be at
  least 3.7, though this has never been checked by configure logic. This
  patch implements the version check. Fixes #23234.
  
  Co-authored-by: Codex <codex@openai.com>
  

• df4ee9b4
  by Cheng Shao at 2025-08-20T11:54:25-04:00

  compiler: use zero cost coerce in GHC.CmmToAsm.CFG.loopInfo
  
  This patch refactors GHC.CmmToAsm.CFG.loopInfo to use zero cost coerce
  and thus addresses the TODO. For coerce to work, constructors of
  Label/LabelMap/LabelSet from GHC.Cmm.Dataflow.Label are exposed,
  though I believe it's a worthy tradeoff to avoid unnecessary runtime
  cost without using unsafeCoerce, since the latter could be a landmine
  for future refactoring.
  
  Co-authored-by: Codex <codex@openai.com>
  

• ccda188d
  by Simon Peyton Jones at 2025-08-20T11:55:07-04:00

  Start with empty inerts in shortcut solving
  
  When short-cut solving we were starting with an inert set that had
  unsolved Wanteds.  This caused an infinite loop (#26314), because a
  typechecker plugin kept being given that unsolved Wanted.
  
  It's better just to start with an empty inert set
  

• c8882ed7
  by Ben Gamari at 2025-08-20T11:55:49-04:00

  configure: Bump minimal bootstrap GHC version to 9.8

• f0a19d74
  by fendor at 2025-08-20T19:55:00-04:00

  Remove deprecated functions from the ghci package
  

• ebeb991b
  by fendor at 2025-08-20T19:55:00-04:00

  base: Remove unstable heap representation details from GHC.Exts
  

• e368e247
  by Rodrigo Mesquita at 2025-08-20T19:55:42-04:00

  bytecode: Use 32bits for breakpoint index
  
  Fixes #26325
  

• 42724462
  by Simon Hengel at 2025-08-21T17:52:11-04:00

  Serialize wired-in names as external names when creating HIE files
  
  Note that the domain of de-serialized names stays the same.
  Specifically, for known-key names, before `lookupKnownKeyName` was used,
  while now this is handled by `lookupOrigNameCache` which captures the
  same range provided that the OrigNameCache has been initialized with
  `knownKeyNames` (which is the case by default).
  
  (fixes #26238)
  

• 6a43f8ec
  by Cheng Shao at 2025-08-21T17:52:52-04:00

  compiler: fix closure C type in SPT init code
  
  This patch fixes the closure C type in SPT init code to StgClosure,
  instead of the previously incorrect StgPtr. Having an incorrect C type
  makes SPT init code not compatible with other foreign stub generation
  logic, which may also emit their own extern declarations for the same
  closure symbols and thus will clash with the incorrect prototypes in
  SPT init code.
  

• 5b5d9d47
  by Ben Gamari at 2025-08-25T14:29:35-04:00

  Revert "STM: don't create a transaction in the rhs of catchRetry# (#26028)"
  
  This reverts commit 0a5836891ca29836a24c306d2a364c2e4b5377fd

• 10f06163
  by Cheng Shao at 2025-08-25T14:30:16-04:00

  wasm: ensure setKeepCAFs() is called in ghci
  
  This patch is a critical bugfix for #26106, see comment and linked
  issue for details.
  

• bedc1004
  by Cheng Shao at 2025-08-26T09:31:18-04:00

  compiler: use zero cost coerce in hoopl setElems/mapToList
  
  This patch is a follow-up of !14680 and changes setElems/mapToList in
  GHC/Cmm/Dataflow/Label to use coerce instead of mapping mkHooplLabel
  over the keys.
  

• 13250d97
  by Ryan Scott at 2025-08-26T09:31:59-04:00

  Reject infix promoted data constructors without DataKinds
  
  In the rename, make sure to apply the same `DataKinds` checks for both
  `HsTyVar` (for prefix promoted data constructors) and `HsOpTy` (for infix
  promoted data constructors) alike.
  
  Fixes #26318.
  

• 37655c46
  by Teo Camarasu at 2025-08-26T15:24:51-04:00

  tests: disable T22859 under LLVM
  
  This test was failing under the LLVM backend since the allocations
  differ from the NCG.
  
  Resolves #26282
  

• 2cbba9d6
  by Teo Camarasu at 2025-08-26T15:25:33-04:00

  base-exports: update version numbers
  
  As the version of the compiler has been bumped, a lot of the embedded
  version numbers will need to be updated if we ever run this test with
  `--test-accept` so let's just update them now, and keep future diffs
  clean.
  

• f9f2ffcf
  by Alexandre Esteves at 2025-08-27T07:19:14-04:00

  Import new name for 'utimbuf' on windows to fix #26337
  
  Fixes an `-Wincompatible-pointer-types` instance that turns into an error on
  recent toolchains and surfaced as such on nixpkgs when doing linux->ucrt cross.
  
  This long-standing warning has been present at least since 9.4:
  
  ```
  C:\GitLabRunner\builds\0\1709189\tmp\ghc16652_0\ghc_4.c:26:115: error:
       warning: incompatible pointer types passing 'struct utimbuf *' to parameter of type 'struct _utimbuf *' [-Wincompatible-pointer-types]
     |
  26 | HsInt32 ghczuwrapperZC9ZCbaseZCSystemziPosixziInternalsZCzuutime(char* a1, struct utimbuf* a2) {return _utime(a1, a2);}
  
     |                                                                                                                   ^
  HsInt32 ghczuwrapperZC9ZCbaseZCSystemziPosixziInternalsZCzuutime(char* a1, struct utimbuf* a2) {return _utime(a1, a2);}
                                                                                                                    ^~
  
  C:\GitLabRunner\builds\0\1709189\_build\stage0\lib\..\..\mingw\x86_64-w64-mingw32\include\sys\utime.h:109:72: error:
       note: passing argument to parameter '_Utimbuf' here
      |
  109 | __CRT_INLINE int __cdecl _utime(const char *_Filename,struct _utimbuf *_Utimbuf) {
      |                                                                        ^
  __CRT_INLINE int __cdecl _utime(const char *_Filename,struct _utimbuf *_Utimbuf) {
  ```
  

• ae89f000
  by Hassan Al-Awwadi at 2025-08-27T07:19:56-04:00

  Adds the fucnction addDependentDirectory to Q, resolving issue #26148.
  
  This function adds a new directory to the list of things a module depends upon. That means that when the contents of the directory change, the recompilation checker will notice this and the module will be recompiled. Documentation has also been added for addDependentFunction and addDependentDirectory in the user guide.
  

• 00478944
  by Simon Peyton Jones at 2025-08-27T16:48:30+01:00

  Comments only
  

• a7884589
  by Simon Peyton Jones at 2025-08-28T11:08:23+01:00

  Type-family occurs check in unification
  
  The occurs check in `GHC.Core.Unify.uVarOrFam` was inadequate in dealing
  with type families.
  
  Better now.  See Note [The occurs check in the Core unifier].
  
  As I did this I realised that the whole apartness thing is trickier than I
  thought: see the new Note [Shortcomings of the apartness test]
  

• 8adfc222
  by sheaf at 2025-08-28T19:47:17-04:00

  Fix orientation in HsWrapper composition (<.>)
  
  This commit fixes the order in which WpCast HsWrappers are composed,
  fixing a bug introduced in commit 56b32c5a2d5d7cad89a12f4d74dc940e086069d1.
  
  Fixes #26350
  

• eb2ab1e2
  by Oleg Grenrus at 2025-08-29T11:00:53-04:00

  Generalise thNameToGhcName by adding HasHscEnv
  
  There were multiple single monad-specific `getHscEnv` across codebase.
  HasHscEnv is modelled on HasDynFlags.
  
  My first idea was to simply add thNameToGhcNameHsc and
  thNameToGhcNameTc, but those would been exactly the same
  as thNameToGhcName already.
  
  Also add an usage example to thNameToGhcName and mention that it's
  recommended way of looking up names in GHC plugins
  

• 2d575a7f
  by fendor at 2025-08-29T11:01:36-04:00

  configure: Bump minimal bootstrap GHC version to 9.10
  

• 716274a5
  by Simon Peyton Jones at 2025-08-29T17:27:12-04:00

  Fix deep subsumption again
  
  This commit fixed #26255:
  
      commit 56b32c5a2d5d7cad89a12f4d74dc940e086069d1
      Author: sheaf <sam.derbyshire@gmail.com>
      Date:   Mon Aug 11 15:50:47 2025 +0200
  
          Improve deep subsumption
  
          This commit improves the DeepSubsumption sub-typing implementation
          in GHC.Tc.Utils.Unify.tc_sub_type_deep by being less eager to fall back
          to unification.
  
  But alas it still wasn't quite right for view patterns: #26331
  
  This MR does a generalisation to fix it.  A bit of a sledgehammer to crack
  a nut, but nice.
  
  * Add a field `ir_inst :: InferInstFlag` to `InferResult`, where
    ```
    data InferInstFlag = IIF_Sigma | IIF_ShallowRho | IIF_DeepRho
    ```
  
  * The flag says exactly how much `fillInferResult` should instantiate
    before filling the hole.
  
  * We can also use this to replace the previous very ad-hoc `tcInferSigma`
    that was used to implement GHCi's `:type` command.
  

• 27206c5e
  by sheaf at 2025-08-29T17:28:14-04:00

  Back-compat for TH SpecialiseP data-con of Pragma
  
  This commit improves the backwards-compatibility story for the
  SpecialiseP constructor of the Template Haskell 'Pragma' datatype.
  
  Instead of keeping the constructor but deprecating it, this commit makes
  it into a bundled pattern synonym of the Pragma datatype. We no longer
  deprecate it; it's useful for handling old-form specialise pragmas.
  

• 26dbcf61
  by fendor at 2025-08-30T05:10:08-04:00

  Move stack decoding logic from ghc-heap to ghc-internal
  
  The stack decoding logic in `ghc-heap` is more sophisticated than the one
  currently employed in `CloneStack`. We want to use the stack decoding
  implementation from `ghc-heap` in `base`.
  We cannot simply depend on `ghc-heap` in `base` due do bootstrapping
  issues.
  Thus, we move the code that is necessary to implement stack decoding to
  `ghc-internal`. This is the right location, as we don't want to add a
  new API to `base`.
  
  Moving the stack decoding logic and re-exposing it in ghc-heap is
  insufficient, though, as we have a dependency cycle between.
  
  * ghc-heap depends on stage1:ghc-internal
  * stage0:ghc depends on stage0:ghc-heap
  
  To fix this, we remove ghc-heap from the set of `stage0` dependencies.
  
  This is not entirely straight-forward, as a couple of boot dependencies,
  such as `ghci` depend on `ghc-heap`.
  Luckily, the boot compiler of GHC is now >=9.10, so we can migrate `ghci`
  to use `ghc-internal` instead of `ghc-heap`, which already exports the
  relevant modules.
  
  However, we cannot 100% remove ghc's dependency on `ghc-heap`, since
  when we compile `stage0:ghc`, `stage1:ghc-internal` is not yet
  available.
  Thus, when we compile with the boot-compiler, we still depend on an
  older version of `ghc-heap`, and only use the modules from `ghc-internal`,
  if the `ghc-internal` version is recent enough.
  
  -------------------------
  Metric Increase:
      T24602_perf_size
      T25046_perf_size_gzip
      T25046_perf_size_unicode
      T25046_perf_size_unicode_gzip
      size_hello_artifact
      size_hello_artifact_gzip
      size_hello_unicode
      size_hello_unicode_gzip
  -------------------------
  
  These metric increases are unfortunate, they are most likely caused by
  the larger (literally in terms of lines of code) stack decoder implementation
  that are now linked into hello-word binaries.
  
  On linux, it is almost a 10% increase, which is considerable.
  

• bd80bb70
  by fendor at 2025-08-30T05:10:08-04:00

  Implement `decode` in terms of `decodeStackWithIpe`
  
  Uses the more efficient stack decoder implementation.
  

• 24441165
  by fendor at 2025-08-30T05:10:08-04:00

  Remove stg_decodeStackzh
  

• fb9cc882
  by Simon Peyton Jones at 2025-08-30T05:10:51-04:00

  Fix a long standing bug in the coercion optimiser
  
  We were mis-optimising ForAllCo, leading to #26345
  
  Part of the poblem was the tricky tower of abstractions leading to
  the dreadful
     GHC.Core.TyCo.Subst.substForAllCoTyVarBndrUsing
  This function was serving two masters: regular substitution, but also
  coercion optimsation.  So tricky was it that it did so wrong.
  
  In this MR I locate all the fancy footwork for coercion optimisation
  in GHC.Core.Coercion.Opt, where it belongs.   That leaves substitution
  free to be much simpler.
  

• 6c78de2d
  by Sylvain Henry at 2025-09-01T08:46:19-04:00

  Driver: substitute virtual Prim module in --make mode too
  
  When we build ghc-internal with --make (e.g. with cabal-install), we
  need to be careful to substitute the virtual interface file for
  GHC.Internal.Prim:
  - after code generation (we generate code for an empty module, so we get
    an empty interface)
  - when we try to reload its .hi file
  

• 26e0db16
  by fendor at 2025-09-01T08:47:01-04:00

  Expose Stack Annotation frames in IPE backtraces by default
  
  When decoding the Haskell-native call stack and displaying the IPE information
  for the stack frames, we print the `StackAnnotation` of the `AnnFrame` by default.
  
  This means, when an exception is thrown, any intermediate stack annotations will
  be displayed in the `IPE Backtrace`.
  
  Example backtrace:
  ```
  Exception: ghc-internal:GHC.Internal.Exception.ErrorCall:
  
  Oh no!
  
  IPE backtrace:
    annotateCallStackIO, called at app/Main.hs:48:10 in backtrace-0.1.0.0-inplace-server:Main
    annotateCallStackIO, called at app/Main.hs:46:13 in backtrace-0.1.0.0-inplace-server:Main
    Main.handler (app/Main.hs:(46,1)-(49,30))
    Main.liftIO (src/Servant/Server/Internal/Handler.hs:30:36-42)
    Servant.Server.Internal.Delayed.runHandler' (src/Servant/Server/Internal/Handler.hs:27:31-41)
    Control.Monad.Trans.Resource.runResourceT (./Control/Monad/Trans/Resource.hs:(192,14)-(197,18))
    Network.Wai.Handler.Warp.HTTP1.processRequest (./Network/Wai/Handler/Warp/HTTP1.hs:195:20-22)
    Network.Wai.Handler.Warp.HTTP1.processRequest (./Network/Wai/Handler/Warp/HTTP1.hs:(195,5)-(203,31))
    Network.Wai.Handler.Warp.HTTP1.http1server.loop (./Network/Wai/Handler/Warp/HTTP1.hs:(141,9)-(157,42))
  HasCallStack backtrace:
    error, called at app/Main.hs:48:32 in backtrace-0.1.0.0-inplace-server:Main
  ```
  
  The first two entries have been added by `annotateCallStackIO`, defined in `annotateCallStackIO`.
  

• a1567efd
  by Sylvain Henry at 2025-09-01T23:01:35-04:00

  RTS: rely less on Hadrian for flag setting (#25843)
  
  Hadrian used to pass -Dfoo command-line flags directly to build the rts.
  We can replace most of these flags with CPP based on cabal flags.
  It makes building boot libraries with cabal-install simpler (cf #25843).
  

• ca5b0283
  by Sergey Vinokurov at 2025-09-01T23:02:23-04:00

  Remove unnecessary irrefutable patterns from Bifunctor instances for tuples
  
  Implementation of https://github.com/haskell/core-libraries-committee/issues/339
  
  Metric Decrease:
      mhu-perf
  

• 2da84b7a
  by sheaf at 2025-09-01T23:03:23-04:00

  Only use active rules when simplifying rule RHSs
  
  When we are simplifying the RHS of a rule, we make sure to only apply
  rewrites from rules that are active throughout the original rule's
  range of active phases.
  
  For example, if a rule is always active, we only fire rules that are
  themselves always active when simplifying the RHS. Ditto for inline
  activations.
  
  This is achieved by setting the simplifier phase to a range of phases,
  using the new SimplPhaseRange constructor. Then:
  
    1. When simplifying the RHS of a rule, or of a stable unfolding,
       we set the simplifier phase to a range of phases, computed from
       the activation of the RULE/unfolding activation, using the
       function 'phaseFromActivation'.
  
       The details are explained in Note [What is active in the RHS of a RULE?]
       in GHC.Core.Opt.Simplify.Utils.
  
    2. The activation check for other rules and inlinings is then:
       does the activation of the other rule/inlining cover the whole
       phase range set in sm_phase? This continues to use the 'isActive'
       function, which now accounts for phase ranges.
  
  On the way, this commit also moves the exact-print SourceText annotation
  from the Activation datatype to the ActivationAnn type. This keeps the
  main Activation datatype free of any extra cruft.
  
  Fixes #26323
  

• 79816cc4
  by Rodrigo Mesquita at 2025-09-02T12:19:59-04:00

  cleanup: Move dehydrateCgBreakInfo to Stg2Bc
  
  This no longer has anything to do with Core.
  

• 53da94ff
  by Rodrigo Mesquita at 2025-09-02T12:19:59-04:00

  rts/Disassembler: Fix spacing of BRK_FUN
  

• 08c0cf85
  by Rodrigo Mesquita at 2025-09-02T12:19:59-04:00

  debugger: Fix bciPtr in Step-out
  
  We need to use `BCO_NEXT` to move bciPtr to ix=1, because ix=0 points to
  the instruction itself!
  
  I do not understand how this didn't crash before.
  

• e7e021fa
  by Rodrigo Mesquita at 2025-09-02T12:19:59-04:00

  debugger: Allow BRK_FUNs to head case continuation BCOs
  
  When we start executing a BCO, we may want to yield to the scheduler:
  this may be triggered by a heap/stack check, context switch, or a
  breakpoint. To yield, we need to put the stack in a state such that
  when execution is resumed we are back to where we yielded from.
  
  Previously, a BKR_FUN could only head a function BCO because we only
  knew how to construct a valid stack for yielding from one -- simply add
  `apply_interp_info` + the BCO to resume executing. This is valid because
  the stack at the start of run_BCO is headed by that BCO's arguments.
  
  However, in case continuation BCOs (as per Note [Case continuation BCOs]),
  we couldn't easily reconstruct a valid stack that could be resumed
  because we dropped too soon the stack frames regarding the value
  returned (stg_ret) and received (stg_ctoi) by that continuation.
  This is especially tricky because of the variable type and size return
  frames (e.g. pointer ret_p/ctoi_R1p vs a tuple ret_t/ctoi_t2).
  
  The trick to being able to yield from a BRK_FUN at the start of a case
  cont BCO is to stop removing the ret frame headers eagerly and instead
  keep them until the BCO starts executing. The new layout at the start of
  a case cont. BCO is described by the new Note [Stack layout when entering run_BCO].
  
  Now, we keep the ret_* and ctoi_* frames when entering run_BCO.
  A BRK_FUN is then executed if found, and the stack is yielded as-is with
  the preserved ret and ctoi frames.
  Then, a case cont BCO's instructions always SLIDE off the headers of the
  ret and ctoi frames, in StgToByteCode.doCase, turning a stack like
  
     |     ....      |
     +---------------+
     |     fv2       |
     +---------------+
     |     fv1       |
     +---------------+
     |     BCO       |
     +---------------+
     | stg_ctoi_ret_ |
     +---------------+
     |    retval     |
     +---------------+
     | stg_ret_..... |
     +---------------+
  
  into
  
     |     ....      |
     +---------------+
     |     fv2       |
     +---------------+
     |     fv1       |
     +---------------+
     |    retval     |
     +---------------+
  
  for the remainder of the BCO.
  
  Moreover, this more uniform approach of keeping the ret and ctoi frames
  means we need less ad-hoc logic concerning the variable size of
  ret_tuple vs ret_p/np frames in the code generator and interpreter:
  Always keep the return to cont. stack intact at the start of run_BCO,
  and the statically generated instructions will take care of adjusting
  it.
  
  Unlocks BRK_FUNs at the start of case cont. BCOs which will enable a
  better user-facing step-out (#26042) which is free of the bugs the
  current BRK_ALTS implementation suffers from (namely, using BRK_FUN
  rather than BRK_ALTS in a case cont. means we'll never accidentally end
  up in a breakpoint "deeper" than the continuation, because we stop at
  the case cont itself rather than on the first breakpoint we evaluate
  after it).
  

• ade3c1e6
  by Rodrigo Mesquita at 2025-09-02T12:19:59-04:00

  BRK_FUN with InternalBreakLocs for code-generation time breakpoints
  
  At the start of a case continuation BCO, place a BRK_FUN.
  This BRK_FUN uses the new "internal breakpoint location" -- allowing us
  to come up with a valid source location for this breakpoint that is not associated with a source-level tick.
  
  For case continuation BCOs, we use the last tick seen before it as the
  source location. The reasoning is described in Note [Debugger: Stepout internal break locs].
  
  Note how T26042c, which was broken because it displayed the incorrect
  behavior of the previous step out when we'd end up at a deeper level
  than the one from which we initiated step-out, is now fixed.
  
  As of this commit, BRK_ALTS is now dead code and is thus dropped.
  
  Note [Debugger: Stepout internal break locs]
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  Step-out tells the interpreter to run until the current function
  returns to where it was called from, and stop there.
  
  This is achieved by enabling the BRK_FUN found on the first RET_BCO
  frame on the stack (See [Note Debugger: Step-out]).
  
  Case continuation BCOs (which select an alternative branch) must
  therefore be headed by a BRK_FUN. An example:
  
      f x = case g x of <--- end up here
          1 -> ...
          2 -> ...
  
      g y = ... <--- step out from here
  
  - `g` will return a value to the case continuation BCO in `f`
  - The case continuation BCO will receive the value returned from g
  - Match on it and push the alternative continuation for that branch
  - And then enter that alternative.
  
  If we step-out of `g`, the first RET_BCO on the stack is the case
  continuation of `f` -- execution should stop at its start, before
  selecting an alternative. (One might ask, "why not enable the breakpoint
  in the alternative instead?", because the alternative continuation is
  only pushed to the stack *after* it is selected by the case cont. BCO)
  
  However, the case cont. BCO is not associated with any source-level
  tick, it is merely the glue code which selects alternatives which do
  have source level ticks. Therefore, we have to come up at code
  generation time with a breakpoint location ('InternalBreakLoc') to
  display to the user when it is stopped there.
  
  Our solution is to use the last tick seen just before reaching the case
  continuation. This is robust because a case continuation will thus
  always have a relevant breakpoint location:
  
      - The source location will be the last source-relevant expression
        executed before the continuation is pushed
  
      - So the source location will point to the thing you've just stepped
        out of
  
      - Doing :step-local from there will put you on the selected
        alternative (which at the source level may also be the e.g. next
        line in a do-block)
  
  Examples, using angle brackets (<<...>>) to denote the breakpoint span:
  
      f x = case <<g x>> {- step in here -} of
          1 -> ...
          2 -> ...>
  
      g y = <<...>> <--- step out from here
  
      ...
  
      f x = <<case g x of <--- end up here, whole case highlighted
          1 -> ...
          2 -> ...>>
  
      doing :step-local ...
  
      f x = case g x of
          1 -> <<...>> <--- stop in the alternative
          2 -> ...
  
  A second example based on T26042d2, where the source is a do-block IO
  action, optimised to a chain of `case expressions`.
  
      main = do
        putStrLn "hello1"
        <<f>> <--- step-in here
        putStrLn "hello3"
        putStrLn "hello4"
  
      f = do
        <<putStrLn "hello2.1">> <--- step-out from here
        putStrLn "hello2.2"
  
      ...
  
      main = do
        putStrLn "hello1"
        <<f>> <--- end up here again, the previously executed expression
        putStrLn "hello3"
        putStrLn "hello4"
  
      doing step/step-local ...
  
      main = do
        putStrLn "hello1"
        f
        <<putStrLn "hello3">> <--- straight to the next line
        putStrLn "hello4"
  
  Finishes #26042
  

• c66910c0
  by Rodrigo Mesquita at 2025-09-02T12:19:59-04:00

  debugger: Re-use the last BreakpointId whole in step-out
  
  Previously, to come up with a location to stop at for `:stepout`, we
  would store the location of the last BreakpointId surrounding the
  continuation, as described by Note [Debugger: Stepout internal break locs].
  
  However, re-using just the location from the last source breakpoint
  isn't sufficient to provide the necessary information in the break
  location. Specifically, it wouldn't bind any variables at that location.
  
  Really, there is no reason not to re-use the last breakpoint wholesale,
  and re-use all the information we had there. Step-out should behave just
  as if we had stopped at the call, but s.t. continuing will not
  re-execute the call.
  
  This commit updates the CgBreakInfo to always store a BreakpointId, be
  it the original one or the one we're emulating (for step-out).
  
  It makes variable bindings on :stepout work
  

• e4abed7b
  by sheaf at 2025-09-02T12:20:40-04:00

  Revert accidental changes to hie.yaml

• 003b715b
  by meooow25 at 2025-09-02T23:48:51+02:00

  Adjust the strictness of Data.List.iterate'
  
  * Don't force the next element in advance when generating a (:).
  * Force the first element to WHNF like every other element.
  
  Now every element in the output list is forced to WHNF when the (:)
  containing it is forced.
  
  CLC proposal:
  https://github.com/haskell/core-libraries-committee/issues/335
  

• b2f6aad0
  by Simon Hengel at 2025-09-03T04:36:10-04:00

  Refactoring: More consistently use logOutput, logInfo, fatalErrorMsg
  

• 60a16db7
  by Rodrigo Mesquita at 2025-09-03T10:55:50+01:00

  bytecode: Don't PUSH_L 0; SLIDE 1 1
  
  While looking through bytecode I noticed a quite common unfortunate
  pattern:
  
  ...
  PUSH_L 0
  SLIDE 1 1
  
  We do this often by generically constructing a tail call from a function
  atom that may be somewhere arbitrary on the stack.
  However, for the special case that the function can be found directly on
  top of the stack, as part of the arguments, it's plain redundant to push
  then slide it.
  
  In this commit we add a small optimisation to the generation of
  tailcalls in bytecode. Simply: lookahead for the function in the stack.
  If it is the first thing on the stack and it is part of the arguments
  which would be dropped as we entered the tail call, then don't push then
  slide it.
  
  In a simple example (T26042b), this already produced a drastic
  improvement in generated code (left is old, right is with this patch):
  
  ```diff
  3c3
  < 2025-07-29 10:14:02.081277 UTC
  ---
  > 2025-07-29 10:50:36.560949 UTC
  160,161c160
  <                                            PUSH_L   0
  <                                            SLIDE    1 2
  ---
  >                                            SLIDE    1 1
  164,165d162
  <                                       PUSH_L   0
  <                                       SLIDE    1 1
  175,176c172
  <                             PUSH_L   0
  <                             SLIDE    1 2
  ---
  >                             SLIDE    1 1
  179,180d174
  <                        PUSH_L   0
  <                        SLIDE    1 1
  206,207d199
  <                        PUSH_L   0
  <                        SLIDE    1 1
  210,211d201
  <                   PUSH_L   0
  <                   SLIDE    1 1
  214,215d203
  <              PUSH_L   0
  <              SLIDE    1 1
  218,219d205
  <         PUSH_L   0
  <         SLIDE    1 1
  222,223d207
  <    PUSH_L   0
  <    SLIDE    1 1
  ...
  600,601c566
  <                                                 PUSH_L   0
  <                                                 SLIDE    1 2
  ---
  >                                                 SLIDE    1 1
  604,605d568
  <                                            PUSH_L   0
  <                                            SLIDE    1 1
  632,633d594
  <                                            PUSH_L   0
  <                                            SLIDE    1 1
  636,637d596
  <                                       PUSH_L   0
  <                                       SLIDE    1 1
  640,641d598
  <                                  PUSH_L   0
  <                                  SLIDE    1 1
  644,645d600
  <                             PUSH_L   0
  <                             SLIDE    1 1
  648,649d602
  <                        PUSH_L   0
  <                        SLIDE    1 1
  652,653d604
  <                   PUSH_L   0
  <                   SLIDE    1 1
  656,657d606
  <              PUSH_L   0
  <              SLIDE    1 1
  660,661d608
  <         PUSH_L   0
  <         SLIDE    1 1
  664,665d610
  <    PUSH_L   0
  <    SLIDE    1 1
  ```
  
  I also compiled lib:Cabal to bytecode and counted the number of bytecode
  lines with `find dist-newstyle -name "*.dump-BCOs" -exec wc {} +`:
  
      with unoptimized core:
      1190689 lines (before) - 1172891 lines (now)
      = 17798 less redundant instructions (-1.5% lines)
  
      with optimized core:
      1924818 lines (before) - 1864836 lines (now)
      = 59982 less redundant instructions (-3.1% lines)
  

• 8b2c72c0
  by L0neGamer at 2025-09-04T06:32:03-04:00

  Add Control.Monad.thenM and Control.Applicative.thenA
  

• 39e1b7cb
  by Teo Camarasu at 2025-09-04T06:32:46-04:00

  ghc-internal: invert dependency of GHC.Internal.TH.Syntax on Data.Data
  
  This means that Data.Data no longer blocks building TH.Syntax, which
  allows greater parallelism in our builds.
  
  We move the Data.Data.Data instances to Data.Data. Quasi depends on
  Data.Data for one of its methods, so,
  we split the Quasi/Q, etc definition out of GHC.Internal.TH.Syntax
  into its own module. This has the added benefit of splitting up this
  quite large module.
  
  Previously TH.Syntax was a bottleneck when compiling ghc-internal. Now
  it is less of a bottle-neck and is also slightly quicker to
  compile (since it no longer contains these instances) at the cost of
  making Data.Data slightly more expensive to compile.
  TH.Lift which depends on TH.Syntax can also compile quicker and no
  longer blocks ghc-internal finishing to compile.
  
  Resolves #26217
  
  -------------------------
  Metric Decrease:
      MultiLayerModulesTH_OneShot
      T13253
      T21839c
      T24471
  Metric Increase:
      T12227
  -------------------------
  

• bdf82fd2
  by Teo Camarasu at 2025-09-04T06:32:46-04:00

  compiler: delete unused names in Builtins.Names.TH
  
  returnQ and bindQ are no longer used in the compiler.
  There was also a very old comment that referred to them that I have modernized
  

• 41a448e5
  by Ben Gamari at 2025-09-04T19:21:43-04:00

  hadrian: Pass lib & include directories to ghc `Setup configure`
  

• 46bb9a79
  by Ben Gamari at 2025-09-04T19:21:44-04:00

  rts/IPE: Fix compilation when zstd is enabled
  
  This was broken by the refactoring undertaken in
  c80dd91c0bf6ac034f0c592f16c548b9408a8481.
  
  Closes #26312.
  

• 138a6e34
  by sheaf at 2025-09-04T19:22:46-04:00

  Make mkCast assertion a bit clearer
  
  This commit changes the assertion message that gets printed when one
  calls mkCast with a coercion whose kind does not match the type of the
  inner expression. I always found the assertion message a bit confusing,
  as it didn't clearly state what exactly was the error.
  

• 9d626be1
  by sheaf at 2025-09-04T19:22:46-04:00

  Simplifier/rules: fix mistakes in Notes & comments
  

• 94b62aa7
  by Simon Peyton Jones at 2025-09-08T03:37:14-04:00

  Refactor ForAllCo
  
  This is a pure refactor, addressing #26389.
  
  It arranges that the kind coercion in a ForAllCo is a MCoercion, rather
  than a plain Coercion, thus removing redundancy in the common case.
  See (FC8) in Note [ForAllCo]
  
  It's a nice cleanup.
  

• 624afa4a
  by sheaf at 2025-09-08T03:38:05-04:00

  Use tcMkScaledFunTys in matchExpectedFunTys
  
  We should use tcMkScaledFunTys rather than mkScaledFunTys in
  GHC.Tc.Utils.Unify.matchExpectedFunTys, as the latter crashes
  when the kind of the result type is a bare metavariable.
  We know the result is always Type-like, so we don't need scaledFunTys
  to try to rediscover that from the kind.
  
  Fixes #26277
  

• 0975d2b6
  by sheaf at 2025-09-08T03:38:54-04:00

  Revert "Remove hptAllFamInstances usage during upsweep"
  
  This reverts commit 3bf6720eff5e86e673568e756161e6d6150eb440.
  

• 0cf34176
  by soulomoon at 2025-09-08T03:38:54-04:00

  Family consistency checks: add test for #26154
  
  This commit adds the test T26154, to make sure that GHC doesn't crash
  when performing type family consistency checks. This test case
  was extracted from Agda.
  
  Fixes #26154
  

• ba210d98
  by Simon Peyton Jones at 2025-09-08T16:26:36+01:00

  Report solid equality errors before custom errors
  
  This MR fixes #26255 by
  
  * Reporting solid equality errors like
       Int ~ Bool
    before "custom type errors".  See comments in `report1` in
    `reportWanteds`
  
  * Suppressing errors that arise from superclasses of
    Wanteds.  See (SCE1) in Note [Suppressing confusing errors]
  
  More details in #26255.
  

• b6249140
  by Simon Peyton Jones at 2025-09-10T10:42:38-04:00

  Fix a scoping error in Specialise
  
  This small patch fixes #26329, which triggered a scoping error.
  
  Test is in T21391, with -fpolymorphic-specialisation enabled
  

• 45305ab8
  by sheaf at 2025-09-10T10:43:29-04:00

  Make rationalTo{Float,Double} inline in phase 0
  
  We hold off on inlining these until phase 0 to allow constant-folding
  rules to fire. However, once we get to phase 0, we should inline them,
  e.g. to expose unboxing opportunities.
  
  See CLC proposal #356.
  

• 0959d4bc
  by Andreas Klebinger at 2025-09-10T10:44:12-04:00

  Add regression test for #26056
  

• dc79593d
  by sheaf at 2025-09-10T10:45:01-04:00

  Deep subsumption: unify mults without tcEqMult
  
  As seen in #26332, we may well end up with a non-reflexive multiplicity
  coercion when doing deep subsumption. We should do the same thing that
  we do without deep subsumption: unify the multiplicities normally,
  without requiring that the coercion is reflexive (which is what
  'tcEqMult' was doing).
  
  Fixes #26332
  

• 4bfe2269
  by sheaf at 2025-09-10T10:45:50-04:00

  lint-codes: fixup MSYS drive letter on Windows
  
  This change ensures that System.Directory.listDirectory doesn't trip up
  on an MSYS-style path like '/c/Foo' when trying to list all testsuite
  stdout/stderr files as required for testing coverage of GHC diagnostic
  codes in the testsuite.
  
  Fixes #25178
  

• 56540775
  by Ben Gamari at 2025-09-10T10:46:32-04:00

  gitlab-ci: Disable split sections on FreeBSD
  
  Due to #26303.
  

• 1537784b
  by Moritz Angermann at 2025-09-10T10:47:13-04:00

  Improve mach-o relocation information
  
  This change adds more information about the symbol and addresses
  we try to relocate in the linker.  This significantly helps when
  deubbging relocation issues reported by users.
  

• 4e67855b
  by Moritz Angermann at 2025-09-10T10:47:54-04:00

  test.mk expect GhcLeadingUnderscore, not LeadingUnderscore (in line with the other Ghc prefixed variables.
  

• c1cdd265
  by Moritz Angermann at 2025-09-10T10:48:35-04:00

  testsuite: Fix broken exec_signals_child.c
  
  There is no signal 0. The signal mask is 1-32.
  

• 99ac335c
  by Moritz Angermann at 2025-09-10T10:49:15-04:00

  testsuite: clarify Windows/Darwin locale rationale for skipping T6037 T2507 T8959a
  

• 0e8fa77a
  by Moritz Angermann at 2025-09-10T10:49:56-04:00

  Skip broken tests on macOS (due to leading underscore not handled properly in the expected output.)
  

• 28570c59
  by Zubin Duggal at 2025-09-10T10:50:37-04:00

  docs(sphinx): fix links to reverse flags when using the :ghc-flag:`-fno-<flag>` syntax
  
  This solution is rather hacky and I suspect there is a better way to do this but I don't know
  enough about Sphinx to do better.
  
  Fixes #26352
  

• d17257ed
  by Cheng Shao at 2025-09-10T17:01:27+02:00

  rel-eng: update alpine images to 3.22
  
  This patch is a part of #25876 and updates alpine images to 3.22,
  while still retaining 3.12 for x86_64 fully_static bindists.
  
  -------------------------
  Metric Decrease:
      MultiComponentModulesRecomp
  -------------------------
  

• db3276bb
  by Sylvain Henry at 2025-09-11T11:27:28-04:00

  T16180: indicate that the stack isn't executable
  

• 11eeeba7
  by Sylvain Henry at 2025-09-11T11:27:28-04:00

  Fix some tests (statically linked GHC vs libc)
  
  When GHC is linked statically, the stdout C global variable that GHC uses
  isn't shared with the stdout C global variable used by loaded code.
  
  As a consequence, the latter must be explicitly flushed because GHC
  won't flush it before exiting.
  

• 80a07571
  by Sylvain Henry at 2025-09-11T11:28:18-04:00

  Testsuite: fix debug_rts detection
  
  Running the testsuite without Hadrian should set config.debug_rts
  correctly too.
  

• 62ae97de
  by Duncan Coutts at 2025-09-12T13:23:33-04:00

  Handle heap allocation failure in I/O primops
  
  The current I/O managers do not use allocateMightFail, but future ones
  will. To support this properly we need to be able to return to the
  primop with a failure. We simply use a bool return value.
  
  Currently however, we will just throw an exception rather than calling
  the GC because that's what all the other primops do too.
  
  For the general issue of primops invoking GC and retrying, see
  https://gitlab.haskell.org/ghc/ghc/-/issues/24105
  

• cb9093f5
  by Duncan Coutts at 2025-09-12T13:23:33-04:00

  Move (and rename) scheduleStartSignalHandlers into RtsSignals.h
  
  Previously it was a local helper (static) function in Schedule.c.
  
  Rename it to startPendingSignalHandlers and deifine it as an inline
  header function in RtsSignals.h. So it should still be fast.
  
  Each (new style) I/O manager is going to need to do the same, so eliminating
  the duplication now makes sense.
  

• 9736d44a
  by Duncan Coutts at 2025-09-12T13:23:33-04:00

  Reduce detail in printThreadBlockage I/O blocking cases
  
  The printThreadBlockage is used in debug tracing output.
  For the cases BlockedOn{Read,Write,Delay} the output previously included
  the fd that was being waited on, and the delay target wake time.
  
  Superficially this sounds useful, but it's clearly not that useful
  because it was already wrong for the Win32 non-threaded I/O manager. In
  that situation it will print garbage (the async_result pointer, cast to
  a fd or a time).
  
  So given that it apparently never mattered that the information was
  accurate, then it's hardly a big jump to say it doesn't matter if it is
  present at all.
  
  A good reason to remove it is that otherwise we have to make a new
  API and a per-I/O manager implementation to fetch the information. And
  for some I/O manager implementations, this information is not available.
  It is not available in the win32 non-threaded I/O manager. And for some
  future Linux ones, there is no need for the fd to be stored, so storing
  it would be just extra space used for very little gain.
  
  So the simplest thing is to just remove the detail.
  

• bc0f2d5d
  by Duncan Coutts at 2025-09-12T13:23:33-04:00

  Add TimeoutQueue.{c,h} and corresponding tests
  
  A data structure used to efficiently manage a collection of timeouts.
  
  It is a priority queue based on absolute expiry time. It uses 64bit
  high-precision Time for the keys. The values are normal closures which
  allows for example using MVars for unblocking.
  
  It is common in many applications for timeouts to be created and then
  deleted or altered before they expire. Thus the choice of data structure
  for timeouts should support this efficiently. The implementation choice
  here is a leftist heap with the extra feature that it supports deleting
  arbitrary elements, provided the caller retain a pointer to the element.
  While the deleteMin operation takes O(log n) time, as in all heap
  structures, the delete operation for arbitrary elements /typically/
  takes O(1), and only O(log n) in the worst case. In practice, when
  managing thousands of timeouts it can be a factor of 10 faster to delete
  a random timeout queue element than to remove the minimum element. This
  supports the common use case.
  
  The plan is to use it in some of the RTS-side I/O managers to support
  their timer functionality. In this use case the heap value will be an
  MVar used for each timeout to unblock waiting threads.
  

• d1679c9d
  by Duncan Coutts at 2025-09-12T13:23:33-04:00

  Add ClosureTable.{c,h} and corresponding tests
  
  A table of pointers to closures on the GC heap with stable indexes.
  
  It provides O(1) alloc, free and lookup. The table can be expanded
  using a simple doubling strategy: in which case allocation is typically
  O(1) and occasionally O(n) for overall amortised O(1). No shrinking is
  used.
  
  The table itself is heap allocated, and points to other heap objects.
  As such it's necessary to use markClosureTable to ensure the table is
  used as a GC root to keep the table entries alive, and maintain proper
  pointers to them as the GC moves heap objects about.
  
  It is designed to be allocated and accesses exclusively from a single
  capability, enabling it to work without any locking. It is thus similar
  to the StablePtr table, but per-capability which removes the need for
  locking. It _should_ also provide lower GC pause times with the
  non-moving GC by spending only O(1) time in markClosureTable, vs O(n)
  for markStablePtrTable.
  
  The plan is to use it in some of the I/O managers to keep track of
  in-flight I/O operations (but not timers). This allows the tracking
  info to be kept on the (unpinned) GC heap, and shared with Haskell
  code, and by putting a pointer to the tracking information in a table,
  the index remains stable and can be passed via foreign code (like the
  kernel).
  

• 78cb8dd5
  by Duncan Coutts at 2025-09-12T13:23:33-04:00

  Add the StgAsyncIOOp closure type
  
  This is intended to be used by multiple I/O managers to help with
  tracking in-flight I/O operations.
  
  It is called asynchronous because from the point of view of the RTS we
  have many such operations in progress at once. From the point of view of
  a Haskell thread of course it can look synchronous.
  

• a2839896
  by Duncan Coutts at 2025-09-12T13:23:33-04:00

  Add StgAsyncIOOp and StgTimeoutQueue to tso->block_info
  
  These will be used by new I/O managers, for threads blocked on I/O or
  timeouts.
  

• fdc2451c
  by Duncan Coutts at 2025-09-12T13:23:33-04:00

  Add a new I/O manager based on poll()
  
  This is a proof of concept I/O manager, to show how to add new ones
  neatly, using the ClosureTable and TimeoutQueue infrastructure.
  
  It uses the old unix poll() API, so it is of course limited in
  performance by that, but it should have the benefit of wide
  compatibility. Also we neatly avoid a name clash with the existing
  select() I/O manager.
  
  Compared to the select() I/O manager:
  1. beause it uses poll() it is not limited to 1024 file descriptors
     (but it's still O(n) so don't expect great performance);
  2. it should have much faster threadDelay (when using it in lots of
     threads at once) because it's based on the new TimeoutQueue which is
     O(log n) rather than O(n).
  
  Some of the code related to timers/timouts is put into a shared module
  rts/posix/Timeout.{h,c} since it is intended to be shared with other
  similar I/O managers.
  

• 6c273b76
  by Duncan Coutts at 2025-09-12T13:23:34-04:00

  Document the I/O managers in the user guide
  
  and note the new poll I/O manager in the release notes.
  

• 824fab74
  by Duncan Coutts at 2025-09-12T13:23:34-04:00

  Use the poll() I/O manager by default
  
  That is, for the non-threaded RTS, prefer the poll I/O manager over the
  legacy select() one, if both can be enabled.
  
  This patch is primarily for CI testing, so we should probably remove
  this patch before merging. We can change defaults later after wider
  testing and feedback.
  

• 39392532
  by Luite Stegeman at 2025-09-12T13:24:16-04:00

  Support larger unboxed sums
  
  Change known constructor encoding for sums in interfaces to use
  11 bits for both the arity and the alternative (up from 8 and 6,
  respectively)
  

• 2af12e21
  by Luite Stegeman at 2025-09-12T13:24:16-04:00

  Decompose padding smallest-first in Cmm toplevel data constructors
  
  This makes each individual padding value aligned
  

• 418fa78f
  by Luite Stegeman at 2025-09-12T13:24:16-04:00

  Use slots smaller than word as tag for smaller unboxed sums
  
  This packs unboxed sums more efficiently by allowing
  Word8, Word16 and Word32 for the tag field if the number of
  constructors is small enough
  

• 8d7e912f
  by Rodrigo Mesquita at 2025-09-12T17:57:24-04:00

  ghc-toolchain: Use ByteOrder rather than new Endianness
  
  Don't introduce a duplicate datatype when the previous one is equivalent
  and already used elsewhere. This avoids unnecessary translation between
  the two.
  

• 7d378476
  by Rodrigo Mesquita at 2025-09-12T17:57:24-04:00

  Read Toolchain.Target files rather than 'settings'
  
  This commit makes GHC read `lib/targets/default.target`, a file with a
  serialized value of `ghc-toolchain`'s `GHC.Toolchain.Target`.
  
  Moreover, it removes all the now-redundant entries from `lib/settings`
  that are configured as part of a `Target` but were being written into
  `settings`.
  
  This makes it easier to support multiple targets from the same compiler
  (aka runtime retargetability). `ghc-toolchain` can be re-run many times
  standalone to produce a `Target` description for different targets, and,
  in the future, GHC will be able to pick at runtime amongst different
  `Target` files.
  
  This commit only makes it read the default `Target` configured in-tree
  or configured when installing the bindist.
  
  The remaining bits of `settings` need to be moved to `Target` in follow
  up commits, but ultimately they all should be moved since they are
  per-target relevant.
  
  Fixes #24212
  
  On Windows, the constant overhead of parsing a slightly more complex
  data structure causes some small-allocation tests to wiggle around 1 to
  2 extra MB (1-2% in these cases).
  
  -------------------------
  Metric Increase:
      MultiLayerModulesTH_OneShot
      T10421
      T10547
      T12234
      T12425
      T13035
      T18140
      T18923
      T9198
      TcPlugin_RewritePerf
  -------------------------
  

• e0780a16
  by Rodrigo Mesquita at 2025-09-12T17:57:24-04:00

  ghc-toolchain: Move TgtHasLibm to per-Target file
  
  TargetHasLibm is now part of the per-target configuration
  
  Towards #26227
  

• 8235dd8c
  by Rodrigo Mesquita at 2025-09-12T17:57:24-04:00

  ghc-toolchain: Move UseLibdw to per-Target file
  
  To support DWARF unwinding, the RTS must be built with the -f+libdw flag
  and with the -DUSE_LIBDW macro definition. These flags are passed on
  build by Hadrian when --enable-dwarf-unwinding is specified at configure
  time.
  
  Whether the RTS was built with support for DWARF is a per-target
  property, and as such, it was moved to the per-target
  GHC.Toolchain.Target.Target file.
  
  Additionally, we keep in the target file the include and library paths
  for finding libdw, since libdw should be checked at configure time (be
  it by configure, or ghc-toolchain, that libdw is properly available).
  
  Preserving the user-given include paths for libdw facilitates in the
  future building the RTS on demand for a given target (if we didn't keep
  that user input, we couldn't)
  
  Towards #26227
  

• d5ecf2e8
  by Rodrigo Mesquita at 2025-09-12T17:57:25-04:00

  ghc-toolchain: Make "Support SMP" a query on a Toolchain.Target
  
  "Support SMP" is merely a function of target, so we can represent it as
  such in `ghc-toolchain`.
  
  Hadrian queries the Target using this predicate to determine how to
  build GHC, and GHC queries the Target similarly to report under --info
  whether it "Support SMP"
  
  Towards #26227
  

• e07b031a
  by Rodrigo Mesquita at 2025-09-12T17:57:25-04:00

  ghc-toolchain: Make "tgt rts linker only supports shared libs" function on Target
  
  Just like with "Support SMP", "target RTS linker only supports shared
  libraries" is a predicate on a `Target` so we can just compute it when
  necessary from the given `Target`.
  
  Towards #26227
  

• 14123ee6
  by Simon Peyton Jones at 2025-09-12T17:58:07-04:00

  Solve forall-constraints via an implication, again
  
  In this earlier commit:
  
    commit 953fd8f1dc080f1c56e3a60b4b7157456949be29
    Author: Simon Peyton Jones <simon.peytonjones@gmail.com>
    Date:   Mon Jul 21 10:06:43 2025 +0100
  
    Solve forall-constraints immediately, or not at all
  
  I used a all-or-nothing strategy for quantified constraints
  (aka forall-constraints).  But alas that fell foul of #26315,
  and #26376.
  
  So this MR goes back to solving a quantified constraint by
  turning it into an implication; UNLESS we are simplifying
  constraints from a SPECIALISE pragma, in which case the
  all-or-nothing strategy is great.  See:
  
     Note [Solving a Wanted forall-constraint]
  
  Other stuff in this MR:
  
  * TcSMode becomes a record of flags, rather than an enumeration
    type; much nicer.
  
  * Some fancy footwork to avoid error messages worsening again
    (The above MR made them better; we want to retain that.)
    See `GHC.Tc.Errors.Ppr.pprQCOriginExtra`.
  
  -------------------------
  Metric Decrease:
      T24471
  -------------------------
  

• e6c192e2
  by Simon Peyton Jones at 2025-09-12T17:58:07-04:00

  Add a test case for #26396
  
  ...same bug ast #26315
  

• 8f3d80ff
  by Luite Stegeman at 2025-09-13T08:43:09+02:00

  Use mkVirtHeapOffsets for reconstructing terms in RTTI
  
  This makes mkVirtHeapOffsets the single source of truth for
  finding field offsets in closures.
  

• eb389338
  by Luite Stegeman at 2025-09-13T08:43:09+02:00

  Sort non-pointer fields by size for more efficient packing
  
  This sorts non-pointer fields in mkVirtHeapOffsets, always
  storing the largest field first. The relative order of
  equally sized fields remains unchanged.
  
  This reduces wasted padding/alignment space in closures with
  differently sized fields.
  

• 99b233f4
  by Alison at 2025-09-13T16:51:04-04:00

  ghc-heap: Fix race condition with profiling builds
  
  Apply the same fix from Closures.hs (64fd0fac83) to Heap.hs by adding
  empty imports to make way-dependent dependencies visible to `ghc -M`.
  
  Fixes #15197, #26407
  

• 77deaa7a
  by Cheng Shao at 2025-09-14T21:29:45-04:00

  hadrian: build in-tree gmp with -fvisibility=hidden
  
  When hadrian builds in-tree gmp, it should build the shared objects
  with -fvisibility=hidden. The gmp symbols are only used by bignum
  logic in ghc-internal and shouldn't be exported by the ghc-internal
  shared library. We should always strive to keep shared library symbol
  table lean, which benefits platforms with slow dynamic linker or even
  hard limits about how many symbols can be exported (e.g. macos dyld,
  win32 dll and wasm dyld).
  

• 42a18960
  by Cheng Shao at 2025-09-14T21:30:26-04:00

  Revert "wasm: add brotli compression for ghci browser mode"
  
  This reverts commit 731217ce68a1093b5f9e26a07d5bd2cdade2b352.
  Benchmarks show non-negligible overhead when browser runs on the same
  host, which is the majority of actual use cases.
  

• e6755b9f
  by Cheng Shao at 2025-09-14T21:30:26-04:00

  wasm: remove etag logic in ghci browser mode web server
  
  This commit removes the etag logic in dyld script's ghci browser mode
  web server. It was meant to support caching logic of wasm shared
  libraries, but even if the port is manually specified to make caching
  even relevant, for localhost the extra overhead around etag logic is
  simply not worth it according to benchmarks.
  

• ac5859b9
  by sheaf at 2025-09-16T14:58:38-04:00

  Add 'Outputable Natural' instance
  
  This commit adds an Outputable instance for the Natural natural-number type,
  as well as a "natural :: Natural -> SDoc" function that mirrors the existing
  "integer" function.
  

• d48ebc23
  by Cheng Shao at 2025-09-16T14:59:18-04:00

  autoconf: emit warning instead of error for FIND_PYTHON logic
  
  This patch makes FIND_PYTHON logic emit warning instead of error, so
  when the user doesn't expect to run the testsuite driver (especially
  when installing a bindist), python would not be mandatory. Fixes #26347.
  

• 54b5950e
  by Sylvain Henry at 2025-09-17T04:45:18-04:00

  Print fully qualified unit names in name mismatch
  
  It's more user-friendly to directly print the right thing instead of
  requiring the user to retry with the additional `-dppr-debug` flag.
  

• 403cb665
  by Ben Gamari at 2025-09-17T04:46:00-04:00

  configure: Fix consistency between distrib and source CC check
  
  Previously distrib/configure.ac did not
  include `cc`.
  
  Closes #26394.
  

• 2dcd4cb9
  by Oleg Grenrus at 2025-09-17T04:46:41-04:00

  Use isPrint in showUnique
  
  The comment say
  
  ```
  -- Avoid emitting non-printable characters in pretty uniques. See #25989.
  ```
  
  so let the code do exactly that.
  
  There are tags (at least : and 0 .. 9) which weren't in A .. z range.
  

• e5dd754b
  by Oleg Grenrus at 2025-09-17T04:46:42-04:00

  Shorten in-module links in hyperlinked source
  
  Instead of href="This.Module#ident" to just "#ident"
  

• 63189b2c
  by Oleg Grenrus at 2025-09-17T04:46:42-04:00

  Use showUnique in internalAnchorIdent
  
  Showing the key of Unique as a number is generally not a great idea.
  GHC Unique has a tag in high bits, so the raw number is unnecessarily
  big.
  
  So now we have
  
  ```html
  <a href="#l-rvgK"><span class="hs-identifier hs-var hs-var">bar</span></a>
  ```
  
  instead of
  
  ```html
  <a href="#local-6989586621679015689"><span class="hs-identifier hs-var hs-var">bar</span></a>
  ```
  
  Together with previous changes of shorter intra-module links the effect
  on compressed files is not huge, that is expected as we simply remove
  repetitive contents which pack well.
  
  ```
  12_694_206  Agda-2.9.0-docs-orig.tar.gz
  12_566_065  Agda-2.9.0-docs.tar.gz
  ```
  
  However when unpacked, the difference can be significant,
  e.g. Agda's largest module source got 5% reduction:
  
  ```
  14_230_117  Agda.Syntax.Parser.Parser.html
  13_422_109  Agda.Syntax.Parser.Parser.html
  ```
  
  The whole hyperlinked source code directory got similar reduction
  
  ```
  121M	Agda-2.9.0-docs-orig/src
  114M	Agda-2.9.0-docs/src
  ```
  
  For the reference, sources are about 2/3 of the generated haddocks
  
  ```
  178M	Agda-2.9.0-docs-old
  172M	Agda-2.9.0-docs
  ```
  
  so we get around 3.5% size reduction overall. Not bad for a small local
  changes.
  

• 6f63f57b
  by Stefan Schulze Frielinghaus at 2025-09-17T04:47:22-04:00

  rts: Fix alignment for gen_workspace #26334
  
  After a0fa4941903272c48b050d24e93eec819eff51bd bootstrap is broken on
  s390x and errors out with
  
  rts/sm/GCThread.h:207:5: error:
       error: alignment of array elements is greater than element size
        207 |     gen_workspace gens[];
            |     ^~~~~~~~~~~~~
  
  The alignment constraint is applied via the attribute to the type
  gen_workspace and leaves the underlying type struct gen_workspace_
  untouched.  On Aarch64, x86, and s390x the struct has a size of 128
  bytes.  On Aarch64 and x86 the alignments of 128 and 64 are divisors of
  the size, respectively, which is why the type is a viable member type
  for an array.  However, on s390x, the alignment is 256 and therefore is
  not a divisor of the size and hence cannot be used for arrays.
  
  Basically I see two fixes here.  Either decrease the alignment
  requirement on s390x, or by applying the alignment constraint on the
  struct itself.  The former might affect performance as noted in
  a0fa4941903272c48b050d24e93eec819eff51bd.  The latter introduces padding
  bits whenever necessary in order to ensure that
  sizeof(gen_workspace[N])==N*sizeof(gen_workspace) holds which is done by
  this patch.
  

• 06d25623
  by Cheng Shao at 2025-09-17T19:32:27-04:00

  ghci: add :shell command
  
  This patch adds a new :shell command to ghci which works similarly to
  :!, except it guarantees to run the command via sh -c. On POSIX hosts
  the behavior is identical to :!, but on Windows it uses the msys2
  shell instead of system cmd.exe shell. This is convenient when writing
  simple ghci scripts that run simple POSIX commands, and the behavior
  can be expected to be coherent on both Windows and POSIX.
  
  Co-authored-by: Codex <codex@openai.com>
  

• 186054f7
  by Cheng Shao at 2025-09-17T19:32:27-04:00

  testsuite: remove legacy :shell trick
  
  This commit makes use of the built-in :shell functionality in ghci in
  the test cases, and remove the legacy :shell trick.
  

• 0a3a4aa3
  by Cheng Shao at 2025-09-17T19:32:27-04:00

  docs: document :shell in ghci
  
  This commit documents the :shell command in ghci.
  
  Co-authored-by: Codex <codex@openai.com>
  

• a4ff12bb
  by Cheng Shao at 2025-09-17T19:33:09-04:00

  ghc-internal: fix codepages program
  
  codepages was not properly updated during the base -> ghc-internal
  migration, this commit fixes it.
  

• 7e094def
  by Cheng Shao at 2025-09-17T19:33:09-04:00

  ghc-internal: relax ucd2haskell cabal upper bounds
  
  This commit relaxes ucd2haskell cabal upper bounds to make it runnable
  via ghc 9.12/9.14.
  

• 7077c9f7
  by Cheng Shao at 2025-09-17T19:33:09-04:00

  ghc-internal: update to unicode 17.0.0
  
  This commit updates the generated code in ghc-internal to match
  unicode 17.0.0.
  

• cef8938f
  by sheaf at 2025-09-17T19:34:09-04:00

  Bad record update msg: allow out-of-scope datacons
  
  This commit ensures that, when we encounter an invalid record update
  (because no constructor exists which contains all of the record fields
  mentioned in the record update), we graciously handle the situation in
  which the constructors themselves are not in scope. In that case,
  instead of looking up the constructors in the GlobalRdrEnv, directly
  look up their GREInfo using the lookupGREInfo function.
  
  Fixes #26391
  

• a2d9d7c2
  by sheaf at 2025-09-17T19:34:09-04:00

  Improve Notes about disambiguating record updates
  
  This commit updates the notes [Disambiguating record updates] and
  [Type-directed record disambiguation], in particular adding more
  information about the deprecation status of type-directed disambiguation
  of record updates.
  

• de44e69e
  by sheaf at 2025-09-19T05:16:51-04:00

  Enable TcM plugins in initTc
  
  This commit ensures that we run typechecker plugins and defaulting
  plugins whenever we call initTc.
  
  In particular, this ensures that the pattern-match checker, which calls
  'initTcDsForSolver' which calls 'initTc', runs with typechecker plugins
  enabled. This matters for situations like:
  
    merge :: Vec n a -> Vec n a -> Vec (2 * n) a
    merge Nil Nil = Nil
    merge (a <: as) (b <: bs) = a :< (b <: merge as bs)
  
  in which we need the typechecker plugin to run in order to tell us that
  the Givens would be inconsistent in the additional equation
  
    merge (_ <: _) Nil
  
  and thus that the equation is not needed.
  
  Fixes #26395
  

• 2c378ad2
  by Cheng Shao at 2025-09-19T05:17:33-04:00

  rel-eng: update fedora image to 42
  
  This patch is a part of #25876 and updates fedora image to 42.
  

• 0a9d9ffc
  by Sylvain Henry at 2025-09-19T13:12:14-04:00

  Fix output of T14999 (#23685)
  
  Fix output of T14999 to:
  - take into account the +1 offset to DW_AT_low_pc (see Note [Info Offset])
  - always use Intel's syntax to force consistency: it was reported that
    sometimes GDB prints `jmpq` instead of `jmp` with the AT&T syntax
  

• 1480872a
  by Vladislav Zavialov at 2025-09-19T13:12:54-04:00

  Fix PREP_MAYBE_LIBRARY in prep_target_file.m4
  
  This change fixes a configure error introduced in:
  
    commit 8235dd8c4945db9cb03e3be3c388d729d576ed1e
    ghc-toolchain: Move UseLibdw to per-Target file
  
  Now the build no longer fails with:
  
    acghc-toolchain: Failed to read a valid Target value from hadrian/cfg/default.target
  

• d1d9e39e
  by Ben Gamari at 2025-09-19T18:24:52-04:00

  StgToByteCode: Don't assume that data con workers are nullary
  
  Previously StgToByteCode assumed that all data-con workers were of a
  nullary representation. This is not a valid assumption, as seen
  in #23210, where an unsaturated application of a unary data
  constructor's worker resulted in invalid bytecode. Sadly, I have not yet
  been able to reduce a minimal testcase for this.
  
  Fixes #23210.
  

• 3eeecd50
  by Ben Gamari at 2025-09-19T18:24:53-04:00

  testsuite: Mark T23146* as unbroken
  

• 2e73f342
  by sheaf at 2025-09-19T18:24:53-04:00

  Add test for #26216
  

• c2efb912
  by Sven Tennie at 2025-09-19T18:25:36-04:00

  Generate correct test header
  
  This increases convenience when copying & pasting...
  

• d2fb811e
  by Sven Tennie at 2025-09-19T18:25:36-04:00

  foundation test: Fix shift amount (#26248)
  
  Shift primops' results are only defined for shift amounts of 0 to word
  size - 1. The approach is similar to testing div-like operations (which
  have a constraint regarding zero operands.)
  
  This was partly vibe coded (https://github.com/supersven/ghc/pull/1) but
  then heavily refactored.
  

• a62ce115
  by Andreas Klebinger at 2025-09-19T18:26:18-04:00

  Tweak jspace test
  
  I've given it a longer timeout, and tweaked the test file generation
  to speed it up a bit. Hopefully that is enough to make it constentily pass.
  
  Last but not least it now also always uses three threads.
  

• 0f034942
  by Cheng Shao at 2025-09-19T18:26:59-04:00

  rts: remove obsolete CC_SUPPORTS_TLS logic
  
  This patch removes obsolete CC_SUPPORTS_TLS logic throughout the rts,
  given __thread is now uniformly supported by C toolchains of all
  platforms we currently support.
  

• ef705655
  by Cheng Shao at 2025-09-19T18:27:41-04:00

  rts: remove obsolete HAS_VISIBILITY_HIDDEN logic
  
  This patch removes obsolete HAS_VISIBILITY_HIDDEN logic throughout the
  rts, given __attribute__((visibility("hidden"))) is uniformly
  supported by C toolchains of all platforms we currently support.
  

• 9fdc1f7d
  by Cheng Shao at 2025-09-19T18:28:21-04:00

  rts: remove -O3 pragma hack in Hash.c
  
  This patch removes an obsolete gcc pragma to specify -O3 in Hash.c.
  Hadrian already passes the right flag.
  

• b8cfa8f7
  by Cheng Shao at 2025-09-19T18:29:01-04:00

  rts: remove obsolete COMPILING_WINDOWS_DLL logic
  
  This patch removes obsolete COMPILING_WINDOWS_DLL logic throughout the
  rts. They were once used for compiling to win32 DLLs, but we haven't
  been able to compile Haskell units to win32 DLLs for many years now,
  due to PE format's restriction of no more than 65536 exported symbols
  in a single DLL.
  

• bb760611
  by Cheng Shao at 2025-09-19T18:29:42-04:00

  wasm: bump browser_wasi_shim to 0.4.2
  
  This patch bumps the browser_wasi_shim dependency of wasm dyld script
  to 0.4.2.
  

• 8b0940db
  by Cheng Shao at 2025-09-20T06:48:05-04:00

  compiler: move Binary instance of Map to GHC.Utils.Binary
  
  This patch moves `Binary` instance of `Map` from `haddock-api` to
  `GHC.Utils.Binary`. This also allows us to remove a redundant instance
  defined for `NameEntityInfo`, which is a type synonym for `Map`.
  

• 4a8fed75
  by Vladislav Zavialov at 2025-09-20T06:48:47-04:00

  Fix keyword in ExplicitNamespaces error message (#26418)
  
  Consider this module header and the resulting error:
  
    {-# LANGUAGE NoExplicitNamespaces #-}
    module T26418 (data HeadC) where
  
    -- error: [GHC-47007]
    --   Illegal keyword 'type'
  
  Previously, the error message would mention 'type' (as shown above),
  even though the user wrote 'data'. This has now been fixed.
  
  The error location has also been corrected: it is now reported at the
  keyword position rather than at the position of the associated
  import/export item.
  

• 867c2675
  by Cheng Shao at 2025-09-20T06:49:28-04:00

  wasm: fix dyld handling for forward declared GOT.func items
  
  This patch fixes wasm shared linker's handling of forward declared
  GOT.func items, see linked issue for details. Also adds T26430 test to
  witness the fix. Fixes #26430.
  
  Co-authored-by: Codex <codex@openai.com>
  

• e7df6cc0
  by Simon Peyton Jones at 2025-09-23T14:34:39-04:00

  Improve pretty printer for HsExpr
  
  Given a very deeply-nested application, it just kept printing
  deeper and deeper.  This small change makes it cut off.
  
  Test is in #26330, but we also get a dramatic decrease in compile
  time for perf/compiler/InstanceMatching:
     InstanceMatching  4,086,884,584  1,181,767,232 -71.1% GOOD
  Why? Because before we got a GIGANTIC error message that took
  ages to pretty-print; now we get this much more civilised message
  (I have removed some whitespace.)
  
  Match.hs:1007:1: error:
      • No instance for ‘Show (F001 a)’ arising from a use of ‘showsPrec’
      • In the second argument of ‘showString’, namely
          ‘(showsPrec
              11 b1
           (GHC.Internal.Show.showSpace
              (showsPrec
                 11 b2
           (GHC.Internal.Show.showSpace
              (showsPrec
                 11 b3
           (GHC.Internal.Show.showSpace
              (showsPrec
                 11 b4
           (GHC.Internal.Show.showSpace
              (showsPrec
                 11 b5
           (GHC.Internal.Show.showSpace
              (showsPrec
                 11 b6
                 (GHC.Internal.Show.showSpace (showsPrec ...)))))))))))))’
  
  -----------------------
  The main payload is
  
  * At the start of `pprExpr`
  * In the defn of `pprApp`
  
  A little bit of refactoring:
  
  * It turned out that we were setting the default cut-off depth to a
    fixed value in two places, so changing one didn't change the other.
    See defaultSDocDepth and defaultSDocCols
  
  * I refactored `pprDeeperList` a bit so I could understand it better.
  
  Because the depth calculation has changed, there are lots of small
  error message wibbles.
  
  Metric Decrease:
      InstanceMatching
  

• 209f0158
  by Simon Peyton Jones at 2025-09-23T14:34:39-04:00

  Use Outputable.ellipsis rather than text "..."
  

• 64bb0e37
  by Sylvain Henry at 2025-09-23T14:35:56-04:00

  deriveConstants: automatically pass -fcommon CC flag (#26393)
  
  By mistake we tried to use deriveConstants without passing
  `--gcc-flag -fcommon` (which Hadrian does) and it failed.
  
  This patch:
  1. adds parsing support for constants stored in the .bss section (i.e.
     when -fcommon isn't passed)
  2. enables passing `-fcommon` automatically to the C compiler because
     Windows requires this for subtle reasons
  3. Documents the subtle reasons
  
  (1) isn't strictly necessary because we always do (2) but it does no
  harm and it is still useful if the CC flags ever contain -fno-common
  

• afcdf92f
  by Oleg Grenrus at 2025-09-23T14:36:41-04:00

  Don't wrap spaces in <span>s
  
  Doing similar comparison as in 63189b2ceca07edf4e179f4180ca60d470c62cb3
  
  With this change the gzipped documentation is now 2% smaller (previously 1%)
  
  12_694_206 Agda-2.9.0-docs-orig.tar.gz
  12_436_829 Agda-2.9.0-docs.tar.gz
  
  Unzipped docs are 5% smaller (previously 3%)
  
  178M	Agda-2.9.0-docs-orig
  169M	Agda-2.9.0-docs
  
  Individual hyperlinked sources are around 7-10% smaller (previously 5%)
  (`Parser` module is generated by happy and has relatively little whitespace)
  
  14_230_117 Agda.Syntax.Parser.Parser.html
  13_220_758 Agda.Syntax.Parser.Parser.html
  
  Agda's hyperlinked sources are 9% smaller now:
  
  121M	Agda-2.9.0-docs-orig/src
  110M	Agda-2.9.0-docs/src
  

• 67de53a6
  by Cheng Shao at 2025-09-23T14:37:31-04:00

  rts: remove obsolete __GNUC__ related logic
  
  This patch removes obsolete `__GNUC__` related logic, given on any
  currently supported platform and toolchain, `__GNUC__ >= 4` is
  universally true. Also pulls some other weeds and most notably, use
  `__builtin___clear_cache` for clang as well, since clang has supported
  this gcc intrinsic since 2014, see
  https://github.com/llvm/llvm-project/commit/c491a8d4577052bc6b3b4c72a7db6a7cfcbc2ed0.
  

• c4d32493
  by Sven Tennie at 2025-09-23T20:40:57-04:00

  RV64: Fix: Add missing truncation to MO_S_Shr (#26248)
  
  Sub-double word (<W64) registers need to be truncated after the
  operation.
  

• 41dce477
  by Sven Tennie at 2025-09-23T20:40:57-04:00

  RV64: Cleanup shift emitting cases/code
  
  Remove overlapping cases to make the shift logic easier to understand.
  

• 0a601c30
  by Alex Washburn at 2025-09-23T20:41:41-04:00

  Correcting LLVM linking of Intel BMI intrinsics pdep{8,16} and pext{8,16}.
  
  This patch fixes #26065.
  
  The LLVM interface does not expose bindings to:
  
    - llvm.x86.bmi.pdep.8
    - llvm.x86.bmi.pdep.16
    - llvm.x86.bmi.pext.8
    - llvm.x86.bmi.pext.16
  
  So calls are instead made to llvm.x86.bmi.{pdep,pext}.32 in these cases,
  with pre/post-operation truncation to constrain the logical value range.
  

• 89e8ff3d
  by Peng Fan at 2025-09-23T20:42:37-04:00

  NCG/LA64: Implement MO_BSwap and MO_BRev with bit-manipulation Instructions
  

• 50f6be09
  by Sylvain Henry at 2025-09-23T20:43:29-04:00

  Allow Core plugins to access unoptimized Core (#23337)
  
  Make the first simple optimization pass after desugaring a real CoreToDo
  pass. This allows CorePlugins to decide whether they want to be executed
  before or after this pass.
  

• 30ef0aac
  by Simon Hengel at 2025-09-23T20:44:12-04:00

  docs: Fix typo in scoped_type_variables.rst

• f8919262
  by Cheng Shao at 2025-09-23T20:44:54-04:00

  ghci: fix bootstrapping with 9.12.3-rc1 and above
  
  This patch fixes bootstrapping GHC with 9.12.3-rc1 and above. ghci
  defines `Binary` instance for `HalfWord` in `ghc-heap`, which is a
  proper `newtype` in 9.14 and starting from 9.12.3. Given we don't
  build `ghc-heap` in stage0, we need to fix this predicate so that it
  corresponds to the boot ghc versions that contain the right version of
  `ghc-heap`.
  

• a7f15858
  by sheaf at 2025-09-24T09:49:53-04:00

  User's guide: clarify optimisation of INLINABLE unfoldings
  
  This updates the user's guide section on INLINABLE pragmas to explain how
  the unfoldings of inlineable functions are optimised. The user's guide incorrectly
  stated that the RHS was not optimised at all, but this is not true. Instead, GHC
  is careful about phase control to optmise the RHS while retaining the guarantee
  that GHC behaves as if the original RHS had been written.

• 495886d9
  by Rodrigo Mesquita at 2025-09-24T09:50:35-04:00

  cleanup: Delete historical artifact of COMPILING_WINDOWS_DLL
  
  Namely, drop the obsolete
  - DLL_IMPORT_RTS
  - DLL_IMPORT_DATA_VAR
  - DLL_IMPORT_DATA_VARNAME
  - DLL_IMPORT_DATA_REF
  
  These macros were not doing anything and placed inconsistently
  
  Looking at the git logs reveal these macros were used to support
  dynamic libraries on Win32, a feature that was dropped
  in b8cfa8f741729ef123569fb321c4b2ab4a1a941c
  
  This allows us to get rid of the rts/DLL.h file too.
  

• 5ae89054
  by Sylvain Henry at 2025-09-24T17:07:00-04:00

  Allow disabling builtin rules (#20298)
  
  Add a way to disable built-in rules programmatically and with a debug flag.
  
  I also took the opportunity to add a debug flag to disable bignum rules,
  which was only possible programmatically (e.g. in a plugin).
  

• 135242ca
  by Rodrigo Mesquita at 2025-09-24T17:07:44-04:00

  Don't use build CFLAGS and friends as target settings
  
  In the GHC in tree configure, `CFLAGS`, `CXXFLAGS`, and similar tool
  configuration flags apply to the BUILD phase of the compiler, i.e. to
  the tools run to compile GHC itself.
  
  Notably, they should /not/ be carried over to the Target settings, i.e.
  these flags should /not/ apply to the tool which GHC invokes at runtime.
  
  Fixes #25637
  

• b418408b
  by Irene Knapp at 2025-09-25T09:47:54-04:00

  Document etymology of "bind" as the name for `>>=`
  
  It took me twenty years of contemplation to realize why it's called that.
  I therefore feel that it may not be obvious to beginners.
  

• e9c5e46f
  by Brandon Chinn at 2025-09-25T09:48:36-04:00

  Fix tabs in string gaps (#26415)
  
  Tabs in string gaps were broken in bb030d0d because previously, string gaps were manually parsed, but now it's lexed by the usual Alex grammar and post-processed after successful lexing.
  
  It broke because of a discrepancy between GHC's lexer grammar and the Haskell Report. The Haskell Report includes tabs in whitechar:
  
  whitechar  →  newline | vertab | space | tab | uniWhite
  
  $whitechar used to include tabs until 18 years ago, when it was removed in order to exclude tabs from $white_no_nl in order to warn on tabs: 6e202120. In this MR, I'm adding \t back into $whitechar, and explicitly excluding \t from the $white_no_nl+ rule ignoring all whitespace in source code, which more accurately colocates the "ignore all whitespace except tabs, which is handled in the next line" logic.
  
  As a side effect of this MR, tabs are now allowed in pragmas; currently, a pragma written as {-# \t LANGUAGE ... #-} is interpreted as the tab character being the pragma name, and GHC warns "Unrecognized pragma". With this change, tabs are ignored as whitespace, which more closely matches the Report anyway.
  

• 8bf5b309
  by Cheng Shao at 2025-09-25T09:49:18-04:00

  wasm: remove the --no-turbo-fast-api-calls hack from dynamic linker shebang
  
  This patch removes the `--no-turbo-fast-api-calls` hack from the dyld
  script shebang; it was used to workaround v8 fast call coredumps in
  nodejs and no longer needed, and comes with a performance penalty,
  hence the removal.
  

• c1cab0c3
  by Sylvain Henry at 2025-09-26T10:36:30-04:00

  Revert "Add necessary flag for js linking"
  
  This reverts commit 84f68e2231b2eddb2e1dc4e90af394ef0f2e803f.
  
  This commit didn't have the expected effect. See discussion in #26290.
  Instead we export HEAP8 and HEAPU8 from rts/js/mem.js
  

• 0a434a80
  by Sylvain Henry at 2025-09-26T10:36:30-04:00

  JS: export HEAPU8 (#26290)
  
  This is now required by newer Emscripten versions.
  

• b10296a9
  by Andreas Klebinger at 2025-09-26T10:37:11-04:00

  sizeExpr: Improve Tick handling.
  
  When determining if we scrutinize a function argument we
  now properly look through ticks. Fixes #26444.
  

• d9e2a9a7
  by mniip at 2025-09-26T16:00:50-04:00

  rts: Refactor parsing of -h flags
  
  We have a nontrivial amount of heap profiling flags available in the
  non-profiled runtime, so it makes sense to reuse the parsing code
  between the profiled and the non-profiled runtime, only restricting
  which flags are allowed.
  

• 089e45aa
  by mniip at 2025-09-26T16:00:50-04:00

  rts: Fix parsing of -h options with braces
  
  When the "filter by" -h options were introduced in
  bc210f7d267e8351ccb66972f4b3a650eb9338bb, the braces were mandatory.
  Then in 3c22fb21fb18e27ce8d941069a6915fce584a526, the braces were made
  optional. Then in d1ce35d2271ac8b79cb5e37677b1a989749e611c the brace
  syntax stopped working, and no one seems to have noticed.
  

• 423f1472
  by mniip at 2025-09-26T16:00:50-04:00

  rts: add -hT<type> and -hi<table id> heap filtering options (#26361)
  
  They are available in non-profiled builds.
  
  Along the way fixed a bug where combining -he<era> and -hr<retainer>
  would ignore whether the retainer matches or not.
  

• 4cda4785
  by mniip at 2025-09-26T16:00:50-04:00

  docs: Document -hT<type> and -hi<addr>
  

• 982ad30f
  by mniip at 2025-09-26T16:00:50-04:00

  rts: Refactor dumping the heap census
  
  Always do the printing of the total size right next to where the bucket
  label is printed. This prevents accidentally printing a label without
  the corresponding amount.
  
  Fixed a bug where exactly this happened for -hi profile and the 0x0
  (uncategorized) info table.
  
  There is now also much more symmetry between fprintf(hp_file,...) and
  the corresponding traceHeapProfSampleString.
  

• 8cbe006a
  by Cheng Shao at 2025-09-26T16:01:34-04:00

  hadrian: fix GHC.Platform.Host generation for cross stage1
  
  This patch fixes incorrectly GHC.Platform.Host generation logic for
  cross stage1 in hadrian (#26449). Also adds T26449 test case to
  witness the fix.
  
  Co-authored-by: Codex <codex@openai.com>
  

• 0ddd0fdc
  by soulomoon at 2025-09-28T19:24:10-04:00

  Remove hptAllInstances usage during upsweep
  
  Previously, during the upsweep phase when
  checking safe imports, we were loading the module
  interface with runTcInteractive, which in turn calls
  hptAllInstances. This accesses non-below modules
  from the home package table.
  
  Change the implementation of checkSafeImports
  to use initTcWithGbl and loadSysInterface to load the
  module interface, since we already have TcGblEnv at hand.
  This eliminates the unnecessary use of runTcInteractive
  and hptAllInstances during the upsweep phase.
  

• e05c496c
  by Ben Gamari at 2025-09-28T19:24:59-04:00

  base: Update changelog to reflect timing of IOPort# removal
  
  This change will make 9.14 afterall.
  

• bdc9d130
  by Cheng Shao at 2025-09-28T19:25:45-04:00

  rts: fix wasm JSFFI initialization constructor code
  
  This commit fixes wasm JSFFI initialization constructor code so that
  the constructor is self-contained and avoids invoking a fake
  __main_argc_argv function. The previous approach of reusing
  __main_void logic in wasi-libc saves a tiny bit of code, at the
  expense of link-time trouble whenever GHC links a wasm module without
  -no-hs-main, in which case the driver-generated main function would
  clash with the definition here, resulting in a linker error. It's
  simply better to avoid messing with the main function, and it would
  additionally allow linking wasm32-wasi command modules that does make
  use of synchronous JSFFI.
  

• 5d59fc8f
  by Cheng Shao at 2025-09-28T19:26:27-04:00

  rts: provide stub implementations of ExecPage functions for wasm
  
  This patch provides stub implementations of ExecPage functions for
  wasm. They are never actually invoked at runtime for any non-TNTC
  platform, yet they can cause link-time errors of missing symbols when
  the GHCi.InfoTable module gets linked into the final wasm module (e.g.
  a GHC API program).
  

• a4d664c7
  by Cheng Shao at 2025-09-29T17:29:22+02:00

  compiler/ghci: replace the LoadDLL message with LoadDLLs
  
  As a part of #25407, this commit changes the LoadDLL message to
  LoadDLLs, which takes a list of DLL paths to load and returns the list
  of remote pointer handles. The wasm dyld is refactored to take
  advantage of LoadDLLs and harvest background parallelism. On other
  platforms, LoadDLLs is based on a fallback codepath that does
  sequential loading.
  
  The driver is not actually emitting singular LoadDLLs message with
  multiple DLLs yet, this is left in subsequent commits.
  
  Co-authored-by: Codex <codex@openai.com>
  

• c7fc4bae
  by Cheng Shao at 2025-09-29T17:29:22+02:00

  driver: separate downsweep/upsweep phase in loadPackages'
  
  This commit refactors GHC.Linker.Loader.loadPackages' to be separated
  into downsweep/upsweep phases:
  
  - The downsweep phase performs dependency analysis and generates a
    list of topologically sorted packages to load
  - The upsweep phase sequentially loads these packages by calling
    loadPackage
  
  This is a necessary refactoring to make it possible to make loading of
  DLLs concurrent.
  

• ab180104
  by Cheng Shao at 2025-09-29T17:57:19+02:00

  driver: emit single LoadDLLs message to load multiple DLLs
  
  This commit refactors the driver so that it emits a single LoadDLLs
  message to load multiple DLLs in GHC.Linker.Loader.loadPackages'.
  Closes #25407.
  
  -------------------------
  Metric Increase:
      MultiLayerModulesTH_OneShot
      TcPlugin_RewritePerf
  -------------------------
  
  Co-authored-by: Codex <codex@openai.com>
  

• 9c304ec0
  by Sean D. Gillespie at 2025-09-29T19:57:07-04:00

  Fix SIZED_BIN_OP_TY_INT casts in RTS interpreter
  
  Correct `SIZED_BIN_OP_TY_INT` cast to integer. Previously, it cast
  its second operand as its parameter `ty`. This does not currently
  cause any issues, since we are only using it for bit shifts.
  
  Fixes #26287
  

• a1de535f
  by Luite Stegeman at 2025-09-30T18:40:28-04:00

  rts: Fix lost wakeups in threadPaused for threads blocked on black holes
  
  The lazy blackholing code in threadPaused could overwrite closures
  that were already eagerly blackholed, and as such wouldn't have a
  marked update frame. If the black hole was overwritten by its
  original owner, this would lead to an undetected collision, and
  the contents of any existing blocking queue being lost.
  
  This adds a check for eagerly blackholed closures and avoids
  overwriting their contents.
  
  Fixes #26324
  

• b7e21e49
  by Luite Stegeman at 2025-09-30T18:40:28-04:00

  rts: push the correct update frame in stg_AP_STACK
  
  The frame contains an eager black hole (__stg_EAGER_BLACKHOLE_info) so
  we should push an stg_bh_upd_frame_info instead of an stg_upd_frame_info.
  

• 02a7c18a
  by Cheng Shao at 2025-09-30T18:41:27-04:00

  ghci: fix lookupSymbolInDLL behavior on wasm
  
  This patch fixes lookupSymbolInDLL behavior on wasm to return Nothing
  instead of throwing. On wasm, we only have lookupSymbol, and the
  driver would attempt to call lookupSymbolInDLL first before falling
  back to lookupSymbol, so lookupSymbolInDLL needs to return Nothing
  gracefully for the fallback behavior to work.
  

• aa0ca5e3
  by Cheng Shao at 2025-09-30T18:41:27-04:00

  hadrian/compiler: enable internal-interpreter for ghc library in wasm stage1
  
  This commit enables the internal-interpreter flag for ghc library in
  wasm stage1, as well as other minor adjustments to make it actually
  possible to launch a ghc api session that makes use of the internal
  interpreter. Closes #26431 #25400.
  

• 69503668
  by Cheng Shao at 2025-09-30T18:41:27-04:00

  testsuite: add T26431 test case
  
  This commit adds T26431 to testsuite/tests/ghci-wasm which goes
  through the complete bytecode compilation/linking/running pipeline in
  wasm, so to witness that the ghc shared library in wasm have full
  support for internal-interpreter.
  

• e9445c01
  by Matthew Pickering at 2025-09-30T18:42:23-04:00

  driver: Load bytecode static pointer entries during linking
  
  Previously the entries were loaded too eagerly, during upsweep, but we
  should delay loading them until we know that the relevant bytecode
  object is demanded.
  
  Towards #25230
  

• b8307eab
  by Cheng Shao at 2025-09-30T18:43:14-04:00

  autoconf/ghc-toolchain: remove obsolete C99 check
  
  This patch removes obsolete c99 check from autoconf/ghc-toolchain. For
  all toolchain & platform combination we support, gnu11 or above is
  already supported without any -std flag required, and our RTS already
  required C11 quite a few years ago, so the C99 check is completely
  pointless.
  

• 9c293544
  by Simon Peyton Jones at 2025-10-01T09:36:10+01:00

  Fix buglet in GHC.Core.Unify.uVarOrFam
  
  We were failing to match two totally-equal types!
  
  This led to #26457.
  

• 554487a7
  by Rodrigo Mesquita at 2025-10-01T23:04:43-04:00

  cleanup: Drop obsolete comment about HsConDetails
  
  HsConDetails used to have an argument representing the type of the
  tyargs in a list:
  
      data HsConDetails tyarg arg rec
        = PrefixCon [tyarg] [arg]
  
  This datatype was shared across 3 synonyms: HsConPatDetails,
  HsConDeclH98Details, HsPatSynDetails. In the latter two cases, `tyarg`
  was instanced to `Void` meaning the list was always empty for these
  cases.
  
  In 7b84c58867edca57a45945a20a9391724db6d9e4, this was refactored such
  that HsConDetails no longer needs a type of tyargs by construction. The
  first case now represents the type arguments in the args type itself,
  with something like:
  
      ConPat "MkE" [InvisP tp1, InvisP tp2, p1, p2]
  
  So the deleted comment really is just obsolete.
  
  Fixes #26461
  

• 6992ac09
  by Cheng Shao at 2025-10-02T07:27:55-04:00

  testsuite: remove unused expected output files
  
  This patch removes unused expected output files in the testsuites on
  platforms that we no longer support.
  

• 39eaaaba
  by Ben Gamari at 2025-10-02T07:28:45-04:00

  rts: Dynamically initialize built-in closures
  
  To resolve #26166 we need to eliminate references to undefined symbols
  in the runtime system. One such source of these is the runtime's
  static references to `I#` and `C#` due the `stg_INTLIKE` and
  `stg_CHARLIKE` arrays.
  
  To avoid this we make these dynamic, initializing them during RTS
  start-up.
  

• c254c54b
  by Cheng Shao at 2025-10-02T07:29:33-04:00

  compiler: only invoke keepCAFsForGHCi if internal-interpreter is enabled
  
  This patch makes the ghc library only invoke keepCAFsForGHCi if
  internal-interpreter is enabled. For cases when it's not (e.g. the
  host build of a cross ghc), this avoids unnecessarily retaining all
  CAFs in the heap. Also fixes the type signature of c_keepCAFsForGHCi
  to match the C ABI.
  

• c9ec4d43
  by Simon Hengel at 2025-10-02T18:42:20-04:00

  Update copyright in documentation
  

• da9633a9
  by Matthew Pickering at 2025-10-02T18:43:04-04:00

  loader: Unify loadDecls and loadModuleLinkables functions
  
  These two functions nearly did the same thing. I have refactored them so
  that `loadDecls` now calls `loadModuleLinkables`.
  
  Fixes #26459
  

• 5db98d80
  by Simon Hengel at 2025-10-02T18:43:53-04:00

  Fix typo

• 1275d360
  by Matthew Pickering at 2025-10-03T06:05:56-04:00

  testsuite: Use ghci_ways to set ways in PackedDataCon/UnboxedTuples/UnliftedDataTypeInterp tests
  
  These tests reimplemented the logic from `valid_way` in order to
  determine what ways to run. It's easier to use this combination of
  `only_ways` and `extra_ways` to only run in GHCi ways and always run in
  GHCi ways.
  

• c06b534b
  by Matthew Pickering at 2025-10-03T06:06:40-04:00

  Rename interpreterBackend to bytecodeBackend
  
  This is preparation for creating bytecode files.
  
  The "interpreter" is one way in which we can run bytecode objects. It is
  more accurate to describe that the backend produces bytecode, rather
  than the means by which the code will eventually run.
  
  The "interpreterBackend" binding is left as a deprecated alias.
  

• 41bdb16f
  by Andreas Klebinger at 2025-10-06T18:04:34-04:00

  Add a perf test for #26425
  

• 1da0c700
  by Andreas Klebinger at 2025-10-06T18:05:14-04:00

  Testsuite: Silence warnings about Wx-partial in concprog001
  

• 7471eb6a
  by sheaf at 2025-10-07T21:39:43-04:00

  Improve how we detect user type errors in types
  
  This commit cleans up all the code responsible for detecting whether a
  type contains "TypeError msg" applications nested inside it. All the
  logic is now in 'userTypeError_maybe', which is always deep. Whether
  it looks inside type family applications is determined by the passed-in
  boolean flag:
  
    - When deciding whether a constraint is definitely insoluble, don't
      look inside type family applications, as they may still reduce -- in
      which case the TypeError could disappear.
    - When reporting unsolved constraints, look inside type family
      applications: they had the chance to reduce but didn't, and the
      custom type error might contain valuable information.
  
  All the details are explained in Note [Custom type errors in constraints]
  in GHC.Tc.Types.Constraint.
  
  Another benefit of this change is that it allows us to get rid of the
  deeply dodgy 'getUserTypeErrorMsg' function.
  
  This commit also improves the detection of custom type errors, for
  example in equality constraints:
  
    TypeError blah ~# rhs
  
  It used to be the case that we didn't detect the TypeError on the LHS,
  because we never considered that equality constraints could be insoluble
  due to the presence of custom type errors. Addressing this oversight
  improves detection of redundant pattern match warnings, fixing #26400.
  

• 29955267
  by Rodrigo Mesquita at 2025-10-07T21:40:25-04:00

  cleanup: Drop obsolete settings from config.mk.in
  
  These values used to be spliced into the bindist's `config.mk` s.t. when
  `make` was run, the values were read and written into the bindist installation `settings` file.
  
  However, we now carry these values to the bindist directly in the
  default.target toolchain file, and `make` writes almost nothing to
  `settings` now (see #26227)
  
  The entries deleted in this MR were already unused.
  
  Fixes #26478
  

• f7adfed2
  by ARATA Mizuki at 2025-10-08T08:37:24-04:00

  T22033 is only relevant if the word size is 64-bit
  
  Fixes #25497
  

• ff1650c9
  by Ben Gamari at 2025-10-08T08:38:07-04:00

  rts/posix: Enforce iteration limit on heap reservation logic
  
  Previously we could loop indefinitely when attempting to get an address
  space reservation for our heap. Limit the logic to 8 iterations to
  ensure we instead issue a reasonable error message.
  
  Addresses #26151.
  

• 01844557
  by Ben Gamari at 2025-10-08T08:38:07-04:00

  rts/posix: Hold on to low reservations when reserving heap
  
  Previously when the OS gave us an address space reservation in low
  memory we would immediately release it and try again. However, on some
  platforms this meant that we would get the same allocation again in the
  next iteration (since mmap's `hint` argument is just that, a hint).
  
  Instead we now hold on to low reservations until we have found a
  suitable heap reservation.
  
  Fixes #26151.
  

• b2c8d052
  by Sven Tennie at 2025-10-08T08:38:47-04:00

  Build terminfo only in upper stages in cross-builds (#26288)
  
  Currently, there's no way to provide library paths for [n]curses for
  both - build and target - in cross-builds. As stage0 is only used to
  build upper stages, it should be fine to build terminfo only for them.
  
  This re-enables building cross-compilers with terminfo.
  

• c58f9a61
  by Julian Ospald at 2025-10-08T08:39:36-04:00

  ghc-toolchain: Drop `ld.gold` from merge object command
  
  It's deprecated.
  
  Also see #25716
  

• 2b8baada
  by sheaf at 2025-10-08T18:23:37-04:00

  Improvements to 'mayLookIdentical'
  
  This commit makes significant improvements to the machinery that decides
  when we should pretty-print the "invisible bits" of a type, such as:
  
    - kind applications, e.g. '@k' in 'Proxy @k ty'
    - RuntimeReps, e.g. 'TYPE r'
    - multiplicities and linear arrows 'a %1 -> b'
  
  To do this, this commit refactors 'mayLookIdentical' to return **which**
  of the invisible bits don't match up, e.g. in
  
    (a %1 -> b) ~ (a %Many -> b)
  
  we find that the invisible bit that doesn't match up is a multiplicity,
  so we should set 'sdocLinearTypes = True' when pretty-printing, and with
  e.g.
  
    Proxy @k1 ~ Proxy @k2
  
  we find that the invisible bit that doesn't match up is an invisible
  TyCon argument, so we set 'sdocPrintExplicitKinds = True'.
  
  We leverage these changes to remove the ad-hoc treatment of linearity
  of data constructors with 'dataConDisplayType' and 'dataConNonLinearType'.
  This is now handled by the machinery of 'pprWithInvisibleBits'.
  
  Fixes #26335 #26340
  

• 129ce32d
  by sheaf at 2025-10-08T18:23:37-04:00

  Store SDoc context in SourceError
  
  This commits modifies the SourceError datatype which is used for
  throwing and then reporting exceptions by storing all the info we need
  to be able to print the SDoc, including whether we should print with
  explicit kinds, explicit runtime-reps, etc.
  
  This is done using the new datatype:
  
    data SourceErrorContext
      = SEC
          !DiagOpts
          !(DiagnosticOpts GhcMessage)
  
  Now, when we come to report an error (by handling the exception), we
  have access to the full context we need.
  
  Fixes #26387
  

• f9790ca8
  by Ben Gamari at 2025-10-08T18:24:19-04:00

  gitlab-ci: Make RELEASE_JOB an input
  
  Rather than an undocumented variable.
  

• 14281a22
  by Ben Gamari at 2025-10-11T14:06:47-04:00

  rts/nonmoving: Fix comment spelling
  

• bedd38b0
  by Ben Gamari at 2025-10-11T14:06:47-04:00

  rts/nonmoving: Use atomic operations to update bd->flags
  

• 215d6841
  by Ben Gamari at 2025-10-11T14:06:47-04:00

  nonmoving: Use get_itbl instead of explicit loads
  
  This is cleaner and also fixes unnecessary (and unsound) use of
  `volatile`.
  

• 2c94aa3a
  by Ben Gamari at 2025-10-11T14:06:47-04:00

  rts/Scav: Handle WHITEHOLEs in scavenge_one
  
  `scavenge_one`, used to scavenge mutable list entries, may encounter
  `WHITEHOLE`s when the non-moving GC is in use via two paths:
  
    1. when an MVAR is being marked concurrently
    2. when the object belongs to a chain of selectors being short-cutted.
  
  Fixes #26204.
  

• 6bd8155c
  by Matthew Pickering at 2025-10-11T14:07:29-04:00

  Add support for generating bytecode objects
  
  This commit adds the `-fwrite-byte-code` option which makes GHC emit a
  `.gbc` file which contains a serialised representation of bytecode.
  
  The bytecode can be loaded by the compiler to avoid having to
  reinterpret a module when using the bytecode interpreter (for example,
  in GHCi).
  
  There are also the new options:
  
  * -gbcdir=<DIR>: Specify the directory to place the gbc files
  * -gbcsuf=<suffix>: Specify the suffix for gbc files
  
  The option `-fbyte-code-and-object-code` now implies
  `-fwrite-byte-code`.
  
  These performance tests fail due to https://github.com/haskell/directory/issues/204
  
  -------------------------
  Metric Increase:
      MultiComponentModules
      MultiLayerModules
      MultiComponentModulesRecomp
      MultiLayerModulesRecomp
      MultiLayerModulesTH_Make
      MultiLayerModulesTH_OneShot
      T13701
  -------------------------
  
  The bytecode serialisation part was implemented by Cheng Shao
  
  Co-authored-by: Cheng Shao <terrorjack@type.dance>
  

• dc8f9599
  by Matthew Pickering at 2025-10-11T14:07:30-04:00

  Revert "Add a perf test for #26425"
  
  This test has a large memory spike currently, which makes the test
  sensitive, since if you allocate a little more or less, the precise
  location where GC happens shifts and you observe a different part of the
  spike.
  
  Andreas told me to revert the patch for now, and he will add it back
  when he fixes the memory spike.
  
  This reverts commit 41bdb16fd083110a06507248f648c507a2feb4af.
  

• e10dcd65
  by Sven Tennie at 2025-10-12T10:24:56+00:00

  T22859: Increase threadDelay for small machines
  
  The previously used thread delay led to failures on my RISC-V test
  setups.
  

• d59ef6b6
  by Hai / @BestYeen at 2025-10-14T21:51:14-04:00

  Change Alex and Happy m4 scripts to display which version was found in the system, adapt small formatting details in Happy script to be more like the Alex script again.

• c98abb6a
  by Hai / @BestYeen at 2025-10-14T21:52:08-04:00

  Update occurrences of return to pure and add a sample for redefining :m to mean :main

• 70ee825a
  by Cheng Shao at 2025-10-14T21:52:50-04:00

  testsuite: fix T3586 for non-SSE3 platforms
  
  `T3586.hs` contains `-fvia-C -optc-msse3` which I think is a
  best-effort basis to harvest the C compiler's auto vectorization
  optimizations via the C backend back when the test was added. The
  `-fvia-C` part is now a deprecated no-op because GHC can't fall back
  to the C backend on a non-unregisterised build, and `-optc-msse3`
  might actually cause the test to fail on non x86/x64 platforms, e.g.
  recent builds of wasi-sdk would report `wasm32-wasi-clang: error:
  unsupported option '-msse3' for target 'wasm32-unknown-wasi'`.
  
  So this patch cleans up this historical cruft. `-fvia-C` is removed,
  and `-optc-msse3` is only passed when cpuid contains `pni` (which
  indicates support of SSE3).
  

• 4be32153
  by Teo Camarasu at 2025-10-15T08:06:09-04:00

  Add submodules for template-haskell-lift and template-haskell-quasiquoter
  
  These two new boot libraries expose stable subsets of the
  template-haskell interface.
  
  This is an implemenation of the GHC proposal https://github.com/ghc-proposals/ghc-proposals/pull/696
  
  Work towards #25262
  

• 0c00c9c3
  by Ben Gamari at 2025-10-15T08:06:51-04:00

  rts: Eliminate uses of implicit constant arrays
  
  Folding of `const`-sized variable-length arrays to a constant-length
  array is a gnu extension which clang complains about.
  
  Closes #26502.
  

• bf902a1d
  by Fendor at 2025-10-15T16:00:59-04:00

  Refactor distinct constructor tables map construction
  
  Adds `GHC.Types.Unique.FM.alterUFM_L`, `GHC.Types.Unique.DFM.alterUDFM_L`
  `GHC.Data.Word64Map.alterLookup` to support fusion of distinct
  constructor data insertion and lookup during the construction of the `DataCon`
  map in `GHC.Stg.Debug.numberDataCon`.
  
  Co-authored-by: Fendor <fendor@posteo.de>
  Co-authored-by: Finley McIlwaine <finleymcilwaine@gmail.com>
  

• b3585ba1
  by Fendor at 2025-10-15T16:00:59-04:00

  Allow per constructor refinement of distinct-constructor-tables
  
  Introduce `-fno-distinct-constructor-tables`. A distinct constructor table
  configuration is built from the combination of flags given, in order. For
  example, to only generate distinct constructor tables for a few specific
  constructors and no others, just pass
  `-fdistinct-constructor-tables-only=C1,...,CN`.
  This flag can be supplied multiple times to extend the set of
  constructors to generate a distinct info table for.
  
  You can disable generation of distinct constructor tables for all
  configurations by passing `-fno-distinct-constructor-tables`.
  
  The various configurations of these flags is included in the `DynFlags`
  fingerprints, which should result in the expected recompilation logic.
  
  Adds a test that checks for distinct tables for various given or omitted
  constructors.
  
  Updates CountDepsAst and CountDepsParser tests to account for new dependencies.
  
  Fixes #23703
  
  Co-authored-by: Fendor <fendor@posteo.de>
  Co-authored-by: Finley McIlwaine <finleymcilwaine@gmail.com>
  

• e17dc695
  by fendor at 2025-10-15T16:01:41-04:00

  Fix typos in haddock documentation for stack annotation API
  

• f85058d3
  by Zubin Duggal at 2025-10-17T13:50:52+05:30

  compiler: Attempt to systematize Unique tags by introducing an ADT for each different tag
  
  Fixes #26264
  
  Metric Decrease:
      T9233
  

• c85c845d
  by sheaf at 2025-10-17T22:35:32-04:00

  Don't prematurely final-zonk PatSyn declarations
  
  This commit makes GHC hold off on the final zonk for pattern synonym
  declarations, in 'GHC.Tc.TyCl.PatSyn.tc_patsyn_finish'.
  This accommodates the fact that pattern synonym declarations without a
  type signature can contain unfilled metavariables, e.g. if the RHS of
  the pattern synonym involves view-patterns whose type mentions promoted
  (level 0) metavariables. Just like we do for ordinary function bindings,
  we should allow these metavariables to be settled later, instead of
  eagerly performing a final zonk-to-type.
  
  Now, the final zonking-to-type for pattern synonyms is performed in
  GHC.Tc.Module.zonkTcGblEnv.
  
  Fixes #26465
  

• ba3e5bdd
  by Rodrigo Mesquita at 2025-10-18T16:57:18-04:00

  Move code-gen aux symbols from ghc-internal to rts
  
  These symbols were all previously defined in ghc-internal and made the
  dependency structure awkward, where the rts may refer to some of these
  symbols and had to work around that circular dependency the way
  described in #26166.
  
  Moreover, the code generator will produce code that uses these symbols!
  Therefore, they should be available in the rts:
  
  PRINCIPLE: If the code generator may produce code which uses this
  symbol, then it should be defined in the rts rather than, say,
  ghc-internal.
  
  That said, the main motivation is towards fixing #26166.
  
  Towards #26166. Pre-requisite of !14892
  

• f31de2a9
  by Ben Gamari at 2025-10-18T16:57:18-04:00

  rts: Avoid static symbol references to ghc-internal
  
  This resolves #26166, a bug due to new constraints placed by Apple's
  linker on undefined references.
  
  One source of such references in the RTS is the many symbols referenced
  in ghc-internal. To mitigate #26166, we make these references dynamic,
  as described in Note [RTS/ghc-internal interface].
  
  Fixes #26166
  
  Co-authored-by: Rodrigo Mesquita <rodrigo.m.mesquita@gmail.com>
  Co-authored-by: Cheng Shao <terrorjack@type.dance>
  

• 43fdfddc
  by Ben Gamari at 2025-10-18T16:57:18-04:00

  compiler: Rename isMathFun -> isLibcFun
  
  This set includes more than just math functions.
  

• 4ed5138f
  by Ben Gamari at 2025-10-18T16:57:18-04:00

  compiler: Add libc allocator functions to libc_funs
  
  Prototypes for these are now visible from `Prim.h`, resulting in
  multiple-declaration warnings in the unregisterised job.
  

• 9a0a076b
  by Ben Gamari at 2025-10-18T16:57:18-04:00

  rts: Minimize header dependencies of Prim.h
  
  Otherwise we will end up with redundant and incompatible declarations
  resulting in warnings during the unregisterised build.
  

• 26b8a414
  by Diego Antonio Rosario Palomino at 2025-10-18T16:58:10-04:00

  Cmm Parser: Fix incorrect example in comment
  
  The Parser.y file contains a comment with an incorrect example of textual
  Cmm (used in .cmm files). This commit updates the comment to ensure it
  reflects valid textual Cmm syntax.
  
  Fixes #26313
  

• d4a9d6d6
  by ARATA Mizuki at 2025-10-19T18:43:47+09:00

  Handle implications between x86 feature flags
  
  This includes:
  
  * Multiple -msse* options can be specified
  * -mavx implies -msse4.2
  * -mavx2 implies -mavx
  * -mfma implies -mavx
  * -mavx512f implies -mavx2 and -mfma
  * -mavx512{cd,er,pf} imply -mavx512f
  
  Closes #24989
  
  Co-authored-by: sheaf <sam.derbyshire@gmail.com>
  

• c9b8465c
  by Cheng Shao at 2025-10-20T10:16:00-04:00

  wasm: workaround WebKit bug in dyld
  
  This patch works around a WebKit bug and allows dyld to run on WebKit
  based platforms as well. See added note for detailed explanation.
  
  Co-authored-by: Codex <codex@openai.com>
  

• 91b6be10
  by Julian Ospald at 2025-10-20T18:21:03-04:00

  Improve error handling in 'getPackageArchives'
  
  When the library dirs in the package conf files are not set up correctly,
  the JS linker will happily ignore such packages and not link against them,
  although they're part of the link plan.
  
  Fixes #26383
  

• 6c5269da
  by Sven Tennie at 2025-10-20T18:21:44-04:00

  Align coding style
  
  Improve readability by using the same style for all constructor calls in
  this function.
  

• 3d305889
  by Sven Tennie at 2025-10-20T18:21:44-04:00

  Reduce complexity by removing joins with mempty
  
  ldArgs, cArgs and cppArgs are all `mempty`. Thus concatenating them adds
  nothing but some complexity while reading the code.
  

• 38d65187
  by Matthew Pickering at 2025-10-21T13:12:20+01:00

  Fix stack decoding when using profiled runtime
  
  There are three fixes in this commit.
  
  * We need to replicate the `InfoTable` and `InfoTableProf`
  approach for the other stack constants (see the new Stack.ConstantsProf
  file).
  
  * Then we need to appropiately import the profiled or non-profiled
    versions.
  
  * Finally, there was an incorrect addition in `stackFrameSize`. We need
    to cast after performing addition on words.
  
  Fixes #26507
  

• 17231bfb
  by fendor at 2025-10-21T13:12:20+01:00

  Add regression test for #26507
  

• 4f5bf93b
  by Simon Peyton Jones at 2025-10-25T04:05:34-04:00

  Postscript to fix for #26255
  
  This MR has comments only
  

• 6ef22fa0
  by IC Rainbow at 2025-10-26T18:23:01-04:00

  Add SIMD primops for bitwise logical operations
  
  This adds 128-bit wide and/or/xor instructions for X86 NCG,
  with both SSE and AVX encodings.
  
  ```
  andFloatX4# :: FloatX4# -> FloatX4# -> FloatX4#     -- andps / vandps
  andDoubleX2# :: DoubleX2# -> DoubleX2# -> DoubleX2# -- andpd / vandpd
  andInt8X16# :: Int8X16# -> Int8X16# -> Int8X16#     -- pand / vpand
  ```
  
  The new primops are available on ARM when using LLVM backend.
  
  Tests added:
  - simd015 (floats and doubles)
  - simd016 (integers)
  - simd017 (words)
  
  Fixes #26417
  

• fbdc623a
  by sheaf at 2025-10-26T18:23:52-04:00

  Add hints for unsolved HasField constraints
  
  This commit adds hints and explanations for unsolved 'HasField'
  constraints.
  
  GHC will now provide additional explanations for an unsolved constraint
  of the form 'HasField fld_name rec_ty fld_ty'; the details are laid out in
  Note [Error messages for unsolved HasField constraints], but briefly:
  
    1. Provide similar name suggestions (e.g. mis-spelled field name)
       and import suggestions (record field not in scope).
       These result in actionable 'GhcHints', which is helpful to provide
       code actions in HLS.
  
    2. Explain why GHC did not solve the constraint, e.g.:
  
      - 'fld_name' is not a string literal (e.g. a type variable)
      - 'rec_ty' is a TyCon without any fields, e.g. 'Int' or 'Bool'.
      - 'fld_ty' contains existentials variables or foralls.
      - The record field is a pattern synonym field (GHC does not generate
        HasField instances for those).
      - 'HasField' is a custom 'TyCon', not actually the built-in
        'HasField' typeclass from 'GHC.Records'.
  
  On the way, we slightly refactor the mechanisms for import suggestions
  in GHC.Rename.Unbound. This is to account for the fact that, for
  'HasField', we don't care whether the field is imported qualified or
  unqualified. 'importSuggestions' was refactored, we now have
  'sameQualImportSuggestions' and 'anyQualImportSuggestions'.
  
  Fixes #18776 #22382 #26480
  

• 99d5707f
  by sheaf at 2025-10-26T18:23:52-04:00

  Rename PatSyn MatchContext to PatSynCtx to avoid punning
  

• 5dc2e9ea
  by Julian Ospald at 2025-10-27T18:17:23-04:00

  Skip uniques test if sources are not available
  

• 544b9ec9
  by Vladislav Zavialov at 2025-10-27T18:18:06-04:00

  Re-export GHC.Hs.Basic from GHC.Hs
  
  Clean up some import sections in GHC by re-exporting GHC.Hs.Basic
  from GHC.Hs.
  

• 643ce801
  by Julian Ospald at 2025-10-28T18:18:55-04:00

  rts: remove unneccesary cabal flags
  
  We perform those checks via proper autoconf macros
  instead that do the right thing and then add those
  libs to the rts buildinfo.
  

• d69ea8fe
  by Vladislav Zavialov at 2025-10-28T18:19:37-04:00

  Test case for #17705
  
  Starting with GHC 9.12 (the first release to include 5745dbd3),
  all examples in this ticket are handled as expected.
  

• 4038a28b
  by Andreas Klebinger at 2025-10-30T12:38:52-04:00

  Add a perf test for #26425
  

• f997618e
  by Andreas Klebinger at 2025-10-30T12:38:52-04:00

  OccAnal: Be stricter for better compiler perf.
  
  In particular we are now stricter:
  
  * When combining usageDetails.
  * When computing binder info.
  
  In combineUsageDetails when combining the underlying adds we compute a
  new `LocalOcc` for each entry by combining the two existing ones.
  
  Rather than wait for those entries to be forced down the road we now
  force them immediately. Speeding up T26425 by about 10% with little
  effect on the common case.
  
  We also force binders we put into the Core AST everywhere now.
  Failure to do so risks leaking the occ env used to set the binders
  OccInfo.
  
  For T26425 compiler residency went down by a factor of ~10x.
  
  Compile time also improved by a factor of ~1.6.
  
  -------------------------
  Metric Decrease:
      T18698a
      T26425
      T9233
  -------------------------
  

• 5618645b
  by Vladislav Zavialov at 2025-10-30T12:39:33-04:00

  Fix namespace specifiers in subordinate exports (#12488)
  
  This patch fixes an oversight in the `lookupChildrenExport` function that
  caused explicit namespace specifiers of subordinate export items to be
  ignored:
  
    module M (T (type A)) where   -- should be rejected
    data T = A
  
  Based on the `IEWrappedName` data type, there are 5 cases to consider:
  1. Unadorned name:   P(X)
  2. Named default:    P(default X)
  3. Pattern synonym:  P(pattern X)
  4. Type name:        P(type X)
  5. Data name:        P(data X)
  
  Case 1 is already handled correctly; cases 2 and 3 are parse errors; and
  it is cases 4 and 5 that we are concerned with in this patch.
  
  Following the precedent established in `LookupExactName`, we introduce
  a boolean flag in `LookupChildren` to control whether to look up in all
  namespaces or in a specific one. If an export item is accompanied by an
  explicit namespace specifier `type` or `data`, we restrict the lookup in
  `lookupGRE` to a specific namespace.
  
  The newly introduced diagnostic `TcRnExportedSubordinateNotFound`
  provides error messages and suggestions more tailored to this context
  than the previously used `reportUnboundName`.
  

• f75ab223
  by Peter Trommler at 2025-10-31T18:43:13-04:00

  ghc-toolchain: detect PowerPC 64 bit ABI
  
  Check preprocessor macro defined for ABI v2 and assume v1 otherwise.
  Fixes #26521
  

• d086c474
  by Peter Trommler at 2025-10-31T18:43:13-04:00

  ghc-toolchain: refactor, move lastLine to Utils
  

• 995dfe0d
  by Vladislav Zavialov at 2025-10-31T18:43:54-04:00

  Tests for -Wduplicate-exports, -Wdodgy-exports
  
  Add test cases for the previously untested diagnostics:
  
    [GHC-51876] TcRnDupeModuleExport
    [GHC-64649] TcRnNullExportedModule
  
  This also revealed a typo (incorrect capitalization of "module") in the
  warning text for TcRnDupeModuleExport, which is now fixed.
  

• f6961b02
  by Cheng Shao at 2025-11-01T00:08:01+01:00

  wasm: reformat dyld source code
  
  This commit reformats dyld source code with prettier, to avoid
  introducing unnecessary diffs in subsequent patches when they're
  formatted before committing.
  

• 0c9032a0
  by Cheng Shao at 2025-11-01T00:08:01+01:00

  wasm: simplify _initialize logic in dyld
  
  This commit simplifies how we _initialize a wasm shared library in
  dyld and removes special treatment for libc.so, see added comment for
  detailed explanation.
  

• ec1b40bd
  by Cheng Shao at 2025-11-01T00:08:01+01:00

  wasm: support running dyld fully client side in the browser
  
  This commit refactors the wasm dyld script so that it can be used to
  load and run wasm shared libraries fully client-side in the browser
  without needing a wasm32-wasi-ghci backend:
  
  - A new `DyLDBrowserHost` class is exported, which runs in the browser
    and uses the in-memory vfs without any RPC calls. This meant to be
    used to create a `rpc` object for the fully client side use cases.
  - The exported `main` function now can be used to load user-specified
    shared libraries, and the user can use the returned `DyLD` instance
    to run their own exported Haskell functions.
  - The in-browser wasi implementation is switched to
    https://github.com/haskell-wasm/browser_wasi_shim for bugfixes and
    major performance improvements not landed upstream yet.
  - When being run by deno, it now correctly switches to non-nodejs code
    paths, so it's more convenient to test dyld logic with deno.
  
  See added comments for details, as well as the added `playground001`
  test case for an example of using it to build an in-browser Haskell
  playground.
  

• 8f3e481f
  by Cheng Shao at 2025-11-01T00:08:01+01:00

  testsuite: add playground001 to test haskell playground
  
  This commit adds the playground001 test case to test the haskell
  playground in browser, see comments for details.
  

• af40606a
  by Cheng Shao at 2025-11-01T00:08:04+01:00

  Revert "testsuite: add T26431 test case"
  
  This reverts commit 695036686f8c6d78611edf3ed627608d94def6b7. T26431
  is now retired, wasm ghc internal-interpreter logic is tested by
  playground001.
  

• 86c82745
  by Vladislav Zavialov at 2025-11-01T07:24:29-04:00

  Supplant TcRnExportHiddenComponents with TcRnDodgyExports (#26534)
  
  Remove a bogus special case in lookup_ie_kids_all,
  making TcRnExportHiddenComponents obsolete.
  

• fcf6331e
  by Richard Eisenberg at 2025-11-03T08:33:05+00:00

  Refactor fundep solving
  
  This commit is a large-scale refactor of the increasingly-messy code that
  handles functional dependencies.  It has virtually no effect on what compiles
  but improves error messages a bit.  And it does the groundwork for #23162.
  
  The big picture is described in
      Note [Overview of functional dependencies in type inference]
  in GHC.Tc.Solver.FunDeps
  
  * New module GHC.Tc.Solver.FunDeps contains all the fundep-handling
    code for the constraint solver.
  
  * Fundep-equalities are solved in a nested scope; they may generate
    unifications but otherwise have no other effect.
    See GHC.Tc.Solver.FunDeps.solveFunDeps
  
    The nested needs to start from the Givens in the inert set, but
    not the Wanteds; hence a new function `resetInertCans`, used in
    `nestFunDepsTcS`.
  
  * That in turn means that fundep equalities never show up in error
    messages, so the complicated FunDepOrigin tracking can all disappear.
  
  * We need to be careful about tracking unifications, so we kick out
    constraints from the inert set after doing unifications.  Unification
    tracking has been majorly reformed: see Note [WhatUnifications] in
    GHC.Tc.Utils.Unify.
  
    A good consequence is that the hard-to-grok `resetUnificationFlag`
    has been replaced with a simpler use of
    `reportCoarseGrainUnifications`
  
  Smaller things:
  
  * Rename `FunDepEqn` to `FunDepEqns` since it contains multiple
    type equalities.
  
  Some compile time improvement
  
  Metrics: compile_time/bytes allocated
                            Baseline
                    Test       value      New value Change
  ---------------------- --------------------------------------
           T5030(normal) 173,839,232    148,115,248 -14.8% GOOD
  hard_hole_fits(normal) 286,768,048    284,015,416  -1.0%
  
               geo. mean                             -0.2%
               minimum                              -14.8%
               maximum                               +0.3%
  
  Metric Decrease:
      T5030
  

• 231adc30
  by Simon Peyton Jones at 2025-11-03T08:33:05+00:00

  QuickLook's tcInstFun should make instantiation variables directly
  
  tcInstFun must make "instantiation variables", not regular
  unification variables, when instantiating function types. That was
  previously implemented by a hack: set the /ambient/ level to QLInstTyVar.
  
  But the hack finally bit me, when I was refactoring WhatUnifications.
  And it was always wrong: see the now-expunged (TCAPP2) note.
  
  This commit does it right, by making tcInstFun call its own
  instantiation functions.  That entails a small bit of duplication,
  but the result is much, much cleaner.
  

• 39d4a24b
  by Simon Peyton Jones at 2025-11-03T08:33:05+00:00

  Build implication for constraints from (static e)
  
  This commit addresses #26466, by buiding an implication for the
  constraints arising from a (static e) form.  The implication has
  a special ic_info field of StaticFormSkol, which tells the constraint
  solver to use an empty set of Givens.
  
  See (SF3) in Note [Grand plan for static forms]
  in GHC.Iface.Tidy.StaticPtrTable
  
  This commit also reinstates an `assert` in GHC.Tc.Solver.Equality.
  
  The test `StaticPtrTypeFamily` was failing with an assertion failure,
  but it now works.
  

• 2e2aec1e
  by Simon Peyton Jones at 2025-11-03T08:33:05+00:00

  Comments about defaulting representation equalities
  

• 52a4d1da
  by Simon Peyton Jones at 2025-11-03T08:33:05+00:00

  Improve tracking of rewriter-sets
  
  This refactor substantially improves the treatment of so-called
  "rewriter-sets" in the constraint solver.
  
  The story is described in the rewritten
     Note [Wanteds rewrite Wanteds: rewriter-sets]
  in GHC.Tc.Types.Constraint
  
  Some highlights
  
  * Trace the free coercion holes of a filled CoercionHole,
    in CoercionPlusHoles.  See Note [Coercion holes] (COH5)
  
    This avoids taking having to take the free coercion variables
    of a coercion when zonking a rewrriter-set
  
  * Many knock on changes
      * Make fillCoercionHole take CoercionPlusHoles as its argument
        rather than to separate arguments.
  
      * Similarly setEqIfWanted, setWantedE, wrapUnifierAndEmit.
  
      * Be more careful about passing the correct CoHoleSet to
        `rewriteEqEvidence` and friends
  
  * Make kickOurAfterFillingCoercionHole more clever. See
    new Note [Kick out after filling a coercion hole]
  
  Smaller matters
  
  * Rename RewriterSet to CoHoleSet
  * Add special-case helper `rewriteEqEvidenceSwapOnly`
  

• 3e78e1ba
  by Simon Peyton Jones at 2025-11-03T08:33:05+00:00

  Tidy up constraint solving for foralls
  
  * In `can_eq_nc_forall` make sure to track Givens that are used
    in the nested solve step.
  
  * Tiny missing-swap bug-fix in `lookup_eq_in_qcis`
  
  * Fix some leftover mess from
        commit 14123ee646f2b9738a917b7cec30f9d3941c13de
        Author: Simon Peyton Jones <simon.peytonjones@gmail.com>
        Date:   Wed Aug 20 00:35:48 2025 +0100
        Solve forall-constraints via an implication, again
    Specifically, trySolveImplication is now dead.
  

• 973f2c25
  by Simon Peyton Jones at 2025-11-03T08:33:05+00:00

  Do not treat CoercionHoles as free variables in coercions
  
  This fixes a long-standing wart in the free-variable finder;
  now CoercionHoles are no longer treated as a "free variable"
  of a coercion.
  
  I got big and unexpected performance regressions when making
  this change.  Turned out that CallArity didn't discover that
  the free variable finder could be eta-expanded, which gave very
  poor code.
  
  So I re-used Note [The one-shot state monad trick] for Endo,
  resulting in GHC.Utils.EndoOS.  Very simple, big win.
  

• c2b8a0f9
  by Simon Peyton Jones at 2025-11-03T08:33:05+00:00

  Update debug-tracing in CallArity
  
  No effect on behaviour, and commented out anyway
  

• 9aa5ee99
  by Simon Peyton Jones at 2025-11-03T08:33:28+00:00

  Comments only -- remove dangling Note references
  

• 6683f183
  by Simon Peyton Jones at 2025-11-03T08:33:28+00:00

  Accept error message wibbles
  

• 3ba3d9f9
  by Luite Stegeman at 2025-11-04T00:59:41-05:00

  rts: fix eager black holes: record mutated closure and fix assertion
  
  This fixes two problems with handling eager black holes, introduced
  by a1de535f762bc23d4cf23a5b1853591dda12cdc9.
  
  - the closure mutation must be recorded even for eager black holes,
    since the mutator has mutated it before calling threadPaused
  
  - The assertion that an unmarked eager black hole must be owned by
    the TSO calling threadPaused is incorrect, since multiple threads
    can race to claim the black hole.
  
  fixes #26495
  

• b5508f2c
  by Rodrigo Mesquita at 2025-11-04T14:10:56+00:00

  build: Relax ghc/ghc-boot Cabal bound to 3.16
  
  Fixes #26202
  

• c5b3541f
  by Rodrigo Mesquita at 2025-11-04T14:10:56+00:00

  cabal-reinstall: Use haddock-api +in-tree-ghc
  
  Fixes #26202
  

• c6d4b945
  by Rodrigo Mesquita at 2025-11-04T14:10:56+00:00

  cabal-reinstall: Pass --strict to Happy
  
  This is necessary to make the generated Parser build successfully
  This mimics Hadrian, which always passes --strict to happy.
  
  Fixes #26202
  

• 79df1e0e
  by Rodrigo Mesquita at 2025-11-04T14:10:56+00:00

  genprimopcode: Require higher happy version
  
  I've bumped the happy version to forbid deprecated Happy versions which
  don't successfully compile.
  

• fa5d33de
  by Simon Peyton Jones at 2025-11-05T08:35:40-05:00

  Add a HsWrapper optimiser
  
  This MR addresses #26349, by introduceing optSubTypeHsWrapper.
  There is a long
  
     Note [Deep subsumption and WpSubType]
  
  in GHC.Tc.Types.Evidence that explains what is going on.
  

• ea58cae5
  by Simon Peyton Jones at 2025-11-05T08:35:40-05:00

  Improve mkWpFun_FRR
  
  This commit ensures that `mkWpFun_FRR` directly produces a `FunCo` in
  the cases where it can.
  
  (Previously called `mkWpFun` which in turn optimised to a `FunCo`, but
  that made the smarts in `mkWpFun` /essential/ rather than (as they
  should be) optional.
  

• 5cdcfaed
  by Ben Gamari at 2025-11-06T09:01:36-05:00

  compiler: Exclude units with no exposed modules from unused package check
  
  Such packages cannot be "used" in the Haskell sense of the word yet
  are nevertheless necessary as they may provide, e.g., C object code or
  link flags.
  
  Fixes #24120.
  

• 74b8397a
  by Brandon Chinn at 2025-11-06T09:02:19-05:00

  Replace deprecated argparse.FileType
  

• 36ddf988
  by Ben Gamari at 2025-11-06T09:03:01-05:00

  Bump unix submodule to 2.8.8.0
  
  Closes #26474.
  

• c32b3a29
  by fendor at 2025-11-06T09:03:43-05:00

  Fix assertion in `postStringLen` to account for \0 byte
  
  We fix the assertion to handle trailing \0 bytes in `postStringLen`.
  Before this change, the assertion looked like this:
  
      ASSERT(eb->begin + eb->size > eb->pos + len + 1);
  
  Let's assume some values to see why this is actually off by one:
  
      eb->begin = 0
      eb->size  = 1
      eb->pos   = 0
  
      len       = 1
  
  then the assertion would trigger correctly:
  
      0 + 1 > 0 + 1 + 1 => 1 > 2 => false
  
  as there is not enough space for the \0 byte (which is the trailing +1).
  However, if we change `eb->size = 2`, then we do have enough space for a
  string of length 1, but the assertion still fails:
  
      0 + 2 > 0 + 1 + 1 => 2 > 2 => false
  
  Which causes the assertion to fail if there is exactly enough space for
  the string with a trailing \0 byte.
  
  Clearly, the assertion should be `>=`!
  If we switch around the operand, it should become more obvious that `<=`
  is the correct comparison:
  
      ASSERT(eb->pos + len + 1 <= eb->begin + eb->size);
  
  This is expresses more naturally that the current position plus the
  length of the string (and the null byte) must be smaller or equal to the
  overall size of the buffer.
  
  This change also is in line with the implementation in
  `hasRoomForEvent` and `hasRoomForVariableEvent`:
  
    ```
    StgBool hasRoomForEvent(EventsBuf *eb, EventTypeNum eNum)
    {
      uint32_t size = ...;
      if (eb->pos + size > eb->begin + eb->size)
      ...
    ```
  
  the check `eb->pos + size > eb->begin + eb->size` is identical to
  `eb->pos + size <= eb->begin + eb->size` plus a negation.
  

• 3034a6f2
  by Ben Gamari at 2025-11-06T09:04:24-05:00

  Bump os-string submodule to 2.0.8
  

• 39567e85
  by Cheng Shao at 2025-11-06T09:05:06-05:00

  rts: use computed goto for instruction dispatch in the bytecode interpreter
  
  This patch uses computed goto for instruction dispatch in the bytecode
  interpreter. Previously instruction dispatch is done by a classic
  switch loop, so executing the next instruction requires two jumps: one
  to the start of the switch loop and another to the case block based on
  the instruction tag. By using computed goto, we can build a jump table
  consisted of code addresses indexed by the instruction tags
  themselves, so executing the next instruction requires only one jump,
  to the destination directly fetched from the jump table.
  
  Closes #12953.
  

• 93fc7265
  by sheaf at 2025-11-06T21:33:24-05:00

  Correct hasFixedRuntimeRep in matchExpectedFunTys
  
  This commit fixes a bug in the representation-polymormorphism check in
  GHC.Tc.Utils.Unify.matchExpectedFunTys. The problem was that we put
  the coercion resulting from hasFixedRuntimeRep in the wrong place,
  leading to the Core Lint error reported in #26528.
  
  The change is that we have to be careful when using 'mkWpFun': it
  expects **both** the expected and actual argument types to have a
  syntactically fixed RuntimeRep, as explained in Note [WpFun-FRR-INVARIANT]
  in GHC.Tc.Types.Evidence.
  
  On the way, this patch improves some of the commentary relating to
  other usages of 'mkWpFun' in the compiler, in particular in the view
  pattern case of 'tc_pat'. No functional changes, but some stylistic
  changes to make the code more readable, and make it easier to understand
  how we are upholding the WpFun-FRR-INVARIANT.
  
  Fixes #26528
  

• c052c724
  by Simon Peyton Jones at 2025-11-06T21:34:06-05:00

  Fix a horrible shadowing bug in implicit parameters
  
  Fixes #26451.  The change is in GHC.Tc.Solver.Monad.updInertDicts
  where we now do /not/ delete /Wanted/ implicit-parameeter constraints.
  
  This bug has been in GHC since 9.8!  But it's quite hard to provoke;
  I contructed a tests in T26451, but it was hard to do so.
  

• b253013e
  by Georgios Karachalias at 2025-11-07T17:21:57-05:00

  Remove the `CoreBindings` constructor from `LinkablePart`
  
  Adjust HscRecompStatus to disallow unhydrated WholeCoreBindings
  from being passed as input to getLinkDeps (which would previously
  panic in this case).
  
  Fixes #26497
  

• ac7b737e
  by Sylvain Henry at 2025-11-07T17:22:51-05:00

  Testsuite: pass ext-interp test way (#26552)
  
  Note that some tests are still marked as broken with the ext-interp way
  (see #26552 and #14335)
  

• 3c2f4bb4
  by sheaf at 2025-11-11T11:47:28-05:00

  Preserve user-written kinds in data declarations
  
  This commit ensures that we preserve the user-written kind for data
  declarations, e.g. in
  
    type T2T = Type -> Type
    type D :: T2T
    data D a where { .. }
  
  that we preserve the user-written kind of D as 'T2T', instead of
  expanding the type synonym 'T2T' during kind checking.
  
  We do this by storing 'tyConKind' separately from 'tyConResKind'. This
  means that 'tyConKind' is not necessarily equal to
  'mkTyConKind binders res_kind', as e.g. in the above example the former
  is 'T2T' while the latter is 'Type -> Type'.
  
  This is explained in Note [Preserve user-written TyCon kind] in GHC.Core.TyCon.
  
  This is particularly important for Haddock, as the kinds stored in
  interface files affect the generated documentation, and we want to
  preserve the user-written types as much as possible.
  

• 19859584
  by sheaf at 2025-11-11T11:47:28-05:00

  Store user-written datacon tvs in interface files
  
  This commit ensures we store the user-written quantified type variables
  of data constructors in interface files, e.g. in
  
    data D a where
      MkD1 :: forall x. x -> D x
      MkD2 :: forall u v. u -> v -> D v
  
  The previous behaviour was to rename the universal variables to match
  the universal variables of the data constructor. This was undesirable
  because the names that end up in interface files end up mattering for
  generated Haddock documentation; it's better to preserve the user-written
  type variables.
  
  Moreover, the universal variables may not have been user-written at all,
  e.g. in an example such as:
  
    type T2T = Type -> Type
    data G :: T2T where
      MkG :: forall x. D x
  
  Here GHC will invent the type variable name 'a' for the first binder of
  the TyCon G. We really don't want to then rename the user-written 'x'
  into the generated 'a'.
  

• 034b2056
  by sheaf at 2025-11-11T11:47:28-05:00

  DataCon univ_tvs names: pick TyCon over inferred
  
  This commit changes how we compute the names of universal type variables
  in GADT data constructors. This augments the existing logic that chose
  which type variable name to use, in GHC.Tc.TyCl.mkGADTVars. We continue
  to prefer DataCon tv names for user-written binders, but we now prefer
  TyCon tv names for inferred (non-user-written) DataCon binders.
  
  This makes a difference in examples such as:
  
    type (:~~:) :: k1 -> k2 -> Type
    data a :~~: b where
      HRefl :: a :~~: a
  
  Before this patch, we ended up giving HRefl the type:
  
    forall {k2}. forall (a :: k2). a :~~: a
  
  whereas we now give it the type:
  
    forall {k1}. forall (a :: k1). a :~~: a
  
  The important part isn't really 'k1' or 'k2', but more that the inferred
  type variable names of the DataCon can be arbitrary/unpredictable (as
  they are chosen by GHC and depend on how unification proceeds), so it's
  much better to use the more predictable TyCon type variable names.
  

• 95078d00
  by sheaf at 2025-11-11T11:47:28-05:00

  Backpack Rename: use explicit record construction
  
  This commit updates the Backpack boilerplate in GHC.Iface.Rename to
  use explicit record construction rather than record update. This makes
  sure that the code stays up to date when the underlying constructors
  change (e.g. new fields are added). The rationale is further explained
  in Note [Prefer explicit record construction].
  

• 2bf36263
  by sheaf at 2025-11-11T11:47:28-05:00

  Store # eta binders in TyCon and use for Haddock
  
  This commit stores the number of TyCon binders that were introduced by
  eta-expansion (by the function GHC.Tc.Gen.HsType.splitTyConKind).
  
  This is then used to pretty-print the TyCon as the user wrote it, e.g.
  for
  
    type Effect :: (Type -> Type) -> Type -> Type
    data State s :: Effect where {..} -- arity 3
  
  GHC will eta-expand the data declaration to
  
    data State s a b where {..}
  
  but also store in the 'TyCon' that the number of binders introduced by
  this eta expansion is 2. This allows us, in
  'Haddock.Convert.synifyTyConKindSig', to recover the original user-written
  syntax, preserving the user's intent in Haddock documentation.
  
  See Note [Inline kind signatures with GADTSyntax] in Haddock.Convert.
  

• 6c91582f
  by Matthew Pickering at 2025-11-11T11:48:12-05:00

  driver: Properly handle errors during LinkNode steps
  
  Previously we were not properly catching errors during the LinkNode step
  (see T9930fail test).
  
  This is fixed by wrapping the `LinkNode` action in `wrapAction`, the
  same handler which is used for module compilation.
  
  Fixes #26496
  

• e1e1eb32
  by Matthew Pickering at 2025-11-11T11:48:54-05:00

  driver: Remove unecessary call to hscInsertHPT
  
  This call was left-over from e9445c013fbccf9318739ca3d095a3e0a2e1be8a
  
  If you follow the functions which call `upsweep_mod`, they immediately
  add the interface to the HomePackageTable when `upsweep_mod` returns.
  

• b22777d4
  by ARATA Mizuki at 2025-11-11T11:49:44-05:00

  LLVM backend: Pass the +evex512 attribute to LLVM 18+ if -mavx512f is set
  
  The newer LLVM requires the +evex512 attribute to enable use of ZMM registers.
  LLVM exhibits a backward-compatible behavior if the cpu is `x86-64`, but not if `penryn`.
  Therefore, on macOS, where the cpu is set to `penryn`, we need to explicitly pass +evex512.
  
  Fixes #26410
  

• 6ead7d06
  by Vladislav Zavialov at 2025-11-11T11:50:26-05:00

  Comments only in GHC.Parser.PostProcess.Haddock
  
  Remove outdated Note [Register keyword location], as the issue it describes
  was addressed by commit 05eb50dff2fcc78d025e77b9418ddb369db49b9f.
  

• 43fa8be8
  by sheaf at 2025-11-11T11:51:18-05:00

  localRegistersConflict: account for assignment LHS
  
  This commit fixes a serious oversight in GHC.Cmm.Sink.conflicts,
  specifically the code that computes which local registers conflict
  between an assignment and a Cmm statement.
  
  If we have:
  
    assignment: <local_reg> = <expr>
          node: <local_reg> = <other_expr>
  
  then clearly the two conflict, because we cannot move one statement past
  the other, as they assign two different values to the same local
  register. (Recall that 'conflicts (local_reg,expr) node' is False if and
  only if the assignment 'local_reg = expr' can be safely commuted past
  the statement 'node'.)
  
  The fix is to update 'GHC.Cmm.Sink.localRegistersConflict' to take into
  account the following two situations:
  
    (1) 'node' defines the LHS local register of the assignment,
    (2) 'node' defines a local register used in the RHS of the assignment.
  
  The bug is precisely that we were previously missing condition (1).
  
  Fixes #26550
  

• 79dfcfe0
  by sheaf at 2025-11-11T11:51:18-05:00

  Update assigned register format when spilling
  
  When we come to spilling a register to put new data into it, in
  GHC.CmmToAsm.Reg.Linear.allocRegsAndSpill_spill, we need to:
  
    1. Spill the data currently in the register. That is, do a spill
       with a format that matches what's currently in the register.
    2. Update the register assignment, allocating a virtual register to
       this real register, but crucially **updating the format** of this
       assignment.
  
  Due to shadowing in the Haskell code for allocRegsAndSpill_spill, we
  were mistakenly re-using the old format. This could lead to a situation
  where:
  
    a. We were using xmm6 to store a Double#.
    b. We want to store a DoubleX2# into xmm6, so we spill the current
       content of xmm6 to the stack using a scalar move (correct).
    c. We update the register assignment, but we fail to update the format
       of the assignment, so we continue to think that xmm6 stores a
       Double# and not a DoubleX2#.
    d. Later on, we need to spill xmm6 because it is getting clobbered by
       another instruction. We then decide to only spill the lower 64 bits
       of the register, because we still think that xmm6 only stores a
       Double# and not a DoubleX2#.
  
  Fixes #26542
  

• aada5db9
  by ARATA Mizuki at 2025-11-11T11:52:07-05:00

  Fix the order of spill/reload instructions
  
  The AArch64 NCG could emit multiple instructions for a single spill/reload,
  but their order was not consistent between the definition and a use.
  
  Fixes #26537
  
  Co-authored-by: sheaf <sam.derbyshire@gmail.com>
  

• 64ec82ff
  by Andreas Klebinger at 2025-11-11T11:52:48-05:00

  Add hpc to release script
  

• 741da00c
  by Ben Gamari at 2025-11-12T03:38:20-05:00

  template-haskell: Better describe getQ semantics
  
  Clarify that the state is a type-indexed map, as suggested by #26484.

• 8b080e04
  by ARATA Mizuki at 2025-11-12T03:39:11-05:00

  Fix incorrect markups in the User's Guide
  
  * Correct markup for C--: "C-\-" in reST
  * Fix internal links
  * Fix code highlighting
  * Fix inline code: Use ``code`` rather than `code`
  * Remove extra backslashes
  
  Fixes #16812
  
  Co-authored-by: sheaf <sam.derbyshire@gmail.com>
  

• a00840ea
  by Simon Peyton Jones at 2025-11-14T15:23:56+00:00

  Make TYPE and CONSTRAINT apart again
  
  This patch finally fixes #24279.
  
  * The story started with #11715
  
  * Then #21623 articulated a plan, which made Type and Constraint
    not-apart; a horrible hack but it worked. The main patch was
       commit 778c6adca2c995cd8a1b84394d4d5ca26b915dac
       Author: Simon Peyton Jones <simonpj@microsoft.com>
       Date:   Wed Nov 9 10:33:22 2022 +0000
  
       Type vs Constraint: finally nailed
  
  * #24279 reported a bug in the above big commit; this small patch fixes it
      commit af6932d6c068361c6ae300d52e72fbe13f8e1f18
      Author: Simon Peyton Jones <simon.peytonjones@gmail.com>
      Date:   Mon Jan 8 10:49:49 2024 +0000
  
      Make TYPE and CONSTRAINT not-apart
  
      Issue #24279 showed up a bug in the logic in GHC.Core.Unify.unify_ty
      which is supposed to make TYPE and CONSTRAINT be not-apart.
  
  * Then !10479 implemented "unary classes".
  
  * That change in turn allows us to make Type and Constraint apart again,
    cleaning up the compiler and allowing a little bit more expressiveness.
  
    It fixes the original hope in #24279, namely that `Type` and `Constraint`
    should be distinct throughout.
  

• c0a1e574
  by Georgios Karachalias at 2025-11-15T05:14:31-05:00

  Report all missing modules with -M
  
  We now report all missing modules at once in GHC.Driver.Makefile.processDeps,
  as opposed to only reporting a single missing module. Fixes #26551.
  

• c9fa3449
  by Sylvain Henry at 2025-11-15T05:15:26-05:00

  JS: fix array index for registers
  
  We used to store R32 in h$regs[-1]. While it's correct in JavaScript,
  fix this to store R32 in h$regs[0] instead.
  

• 9e469909
  by Sylvain Henry at 2025-11-15T05:15:26-05:00

  JS: support more than 128 registers (#26558)
  
   The JS backend only supported 128 registers (JS variables/array slots
   used to pass function arguments). It failed in T26537 when 129
   registers were required.
  
  This commit adds support for more than 128 registers: it is now limited to
  maxBound :: Int (compiler's Int). If we ever go above this threshold the
  compiler now panics with a more descriptive message.
  
  A few built-in JS functions were assuming 128 registers and have been
  rewritten to use loops. Note that loops are only used for "high"
  registers that are stored in an array: the 31 "low" registers are still
  handled with JS global variables and with explicit switch-cases to
  maintain good performance in the most common cases (i.e. few registers
  used). Adjusting the number of low registers is now easy: just one
  constant to adjust (GHC.StgToJS.Regs.lowRegsCount).
  
  No new test added: T26537 is used as a regression test instead.
  

• 0a64a78b
  by Sven Tennie at 2025-11-15T20:31:10-05:00

  AArch64: Simplify CmmAssign and CmmStore
  
  The special handling for floats was fake: The general case is always
  used. So, the additional code path isn't needed (and only adds
  complexity for the reader.)
  

• 15b311be
  by sheaf at 2025-11-15T20:32:02-05:00

  SimpleOpt: refactor & push coercions into lambdas
  
  This commit improves the simple optimiser (in GHC.Core.SimpleOpt)
  in a couple of ways:
  
    - The logic to push coercion lambdas is shored up.
  
      The function 'pushCoercionIntoLambda' used to be called in 'finish_app',
      but this meant we could not continue to optimise the program after
      performing this transformation.
  
      Now, we call 'pushCoercionIntoLambda' as part of 'simple_app'.
      Doing so can be important when dealing with unlifted newtypes,
      as explained in  Note [Desugaring unlifted newtypes].
  
    - The code is re-structured to avoid duplication and out-of-sync
      code paths.
  
      Now, 'simple_opt_expr' defers to 'simple_app' for the 'App', 'Var',
      'Cast' and 'Lam' cases. This means all the logic for those is
      centralised in a single place (e.g. the 'go_lam' helper function).
  
      To do this, the general structure is brought a bit closer to the
      full-blown simplifier, with a notion of 'continuation'
      (see 'SimpleContItem').
  
  This commit also modifies GHC.Core.Opt.Arity.pushCoercionIntoLambda to
  apply a substitution (a slight generalisation of its existing implementation).
  

• b33284c7
  by sheaf at 2025-11-15T20:32:02-05:00

  Improve typechecking of data constructors
  
  This commit changes the way in which we perform typecheck data
  constructors, in particular how we make multiplicities line up.
  
  Now, impedance matching occurs as part of the existing subsumption
  machinery. See the revamped Note [Typechecking data constructors] in
  GHC.Tc.Gen.App, as well as Note [Polymorphisation of linear fields]
  in GHC.Core.Multiplicity.
  
  This allows us to get rid of a fair amount of hacky code that was
  added with the introduction of LinearTypes; in particular the logic of
  GHC.Tc.Gen.Head.tcInferDataCon.
  
  -------------------------
  Metric Decrease:
      T10421
      T14766
      T15164
      T15703
      T19695
      T5642
      T9630
      WWRec
  -------------------------
  

• b6faf5d0
  by sheaf at 2025-11-15T20:32:02-05:00

  Handle unsaturated rep-poly newtypes
  
  This commit allows GHC to handle unsaturated occurrences of unlifted
  newtype constructors. The plan is detailed in
  Note [Eta-expanding rep-poly unlifted newtypes]
  in GHC.Tc.Utils.Concrete: for unsaturated unlifted newtypes, we perform
  the appropriate representation-polymorphism check in tcInstFun.
  

• 682bf979
  by Mike Pilgrem at 2025-11-16T16:44:14+00:00

  Fix #26293 Valid stack.yaml for hadrian
  

• acc70c3a
  by Simon Peyton Jones at 2025-11-18T16:21:20-05:00

  Fix a bug in defaulting
  
  Addresses #26582
  
  Defaulting was doing some unification but then failing to
  iterate. Silly.
  
  I discovered that the main solver was unnecessarily iterating even
  if there was a unification for an /outer/ unification variable, so
  I fixed that too.
  

• c12fa73e
  by Simon Peyton Jones at 2025-11-19T02:55:01-05:00

  Make PmLit be in Ord, and use it in Map
  
  This MR addresses #26514, by changing from
  
      data PmAltConSet = PACS !(UniqDSet ConLike) ![PmLit]
    to
      data PmAltConSet = PACS !(UniqDSet ConLike) !(Map PmLit PmLit)
  
  This matters when doing pattern-match overlap checking, when there
  is a very large set of patterns.  For most programs it makes
  no difference at all.
  
  For the N=5000 case of the repro case in #26514, compiler
  mutator time (with `-fno-code`) goes from 1.9s to 0.43s.
  
  All for the price for an Ord instance for PmLit
  

• 41b84f40
  by sheaf at 2025-11-19T02:55:52-05:00

  Add passing tests for #26311 and #26072
  
  This commit adds two tests cases that now pass since landing the changes
  to typechecking of data constructors in b33284c7.
  
  Fixes #26072 #26311
  

• 1faa758a
  by sheaf at 2025-11-19T02:55:52-05:00

  mkCast: weaken bad cast warning for multiplicity
  
  This commit weakens the warning message emitted when constructing a bad
  cast in mkCast to ignore multiplicity.
  
  Justification: since b33284c7, GHC uses sub-multiplicity coercions to
  typecheck data constructors. The coercion optimiser is free to discard
  these coercions, both for performance reasons, and because GHC's Core
  simplifier does not (yet) preserve linearity.
  We thus weaken 'mkCast' to use 'eqTypeIgnoringMultiplicity' instead of
  'eqType', to avoid getting many spurious warnings about mismatched
  multiplicities.
  

• 55eab80d
  by Sylvain Henry at 2025-11-20T17:33:13-05:00

  Build external interpreter program on demand (#24731)
  
  This patch teaches GHC how to build the external interpreter program
  when it is missing. As long as we have the `ghci` library, doing this is
  trivial so most of this patch is refactoring for doing it sanely.
  

• 08bbc028
  by Rodrigo Mesquita at 2025-11-20T17:33:54-05:00

  Add tests for #23973 and #26565
  
  These were fixed by 4af4f0f070f83f948e49ad5d7835fd91b8d3f0e6 in !10417
  

• 6b42232c
  by sheaf at 2025-11-20T17:34:35-05:00

  Mark T26410_ffi as fragile on Windows
  
  As seen in #26595, this test intermittently fails on Windows.
  This commit marks it as fragile, until we get around to fixing it.
  

• b7b7c049
  by Andrew Lelechenko at 2025-11-21T21:04:01+00:00

  Add nubOrd / nubOrdBy to Data.List and Data.List.NonEmpty
  
  As per https://github.com/haskell/core-libraries-committee/issues/336
  

• 352d5462
  by Marc Scholten at 2025-11-22T10:33:03-05:00

  Fix haddock test runner to handle UTF-8 output
  
  xhtml 3000.4.0.0 now produces UTF-8 output instead of escaping non-ASCII characters.
  
  When using --test-accept it previously wrote files in the wrong encoding
  because they have not been decoded properly when reading the files.
  

• 48a3ed57
  by Simon Peyton Jones at 2025-11-25T15:33:54+00:00

  Add a fast-path for args=[] to occAnalApp
  
  In the common case of having not arguments, occAnalApp
  was doing redundant work.
  

• 951e5ed9
  by Simon Peyton Jones at 2025-11-25T15:33:54+00:00

  Fix a performance hole in the occurrence analyser
  
  As #26425 showed, the clever stuff in
  
     Note [Occurrence analysis for join points]
  
  does a lot of duplication of usage details.  This patch
  improved matters with a little fancy footwork.  It is
  described in the new (W4) of the same Note.
  
  Compile-time allocations go down slightly. Here are the changes
  of +/- 0.5% or more:
  
      T13253(normal)    329,369,244    326,395,544  -0.9%
  T13253-spj(normal)     66,410,496     66,095,864  -0.5%
      T15630(normal)    129,797,200    128,663,136  -0.9%
     T15630a(normal)    129,212,408    128,027,560  -0.9%
      T16577(normal)  6,756,706,896  6,723,028,512  -0.5%
      T18282(normal)    128,462,070    125,808,584  -2.1% GOOD
     T18698a(normal)    208,418,305    202,037,336  -3.1% GOOD
      T18730(optasm)    136,981,756    136,208,136  -0.6%
      T18923(normal)     58,103,088     57,745,840  -0.6%
      T19695(normal)  1,386,306,272  1,365,609,416  -1.5%
      T26425(normal)  3,344,402,957  2,457,811,664 -26.5% GOOD
       T6048(optasm)     79,763,816     79,212,760  -0.7%
       T9020(optasm)    225,278,408    223,682,440  -0.7%
       T9961(normal)    303,810,717    300,729,168  -1.0% GOOD
  
           geo. mean                                -0.5%
           minimum                                 -26.5%
           maximum                                  +0.4%
  
  Metric Decrease:
      T18282
      T18698a
      T26425
      T9961
  

• f1959dfc
  by Simon Peyton Jones at 2025-11-26T11:58:07+00:00

  Remove a quadratic-cost assertion check in mkCoreApp
  
  See the new Note [Assertion checking in mkCoreApp]
  

• 98fa0d36
  by Simon Hengel at 2025-11-27T17:54:57-05:00

  Fix typo in docs/users_guide/exts/type_families.rst
  

• 5b97e5ce
  by Simon Hengel at 2025-11-27T17:55:37-05:00

  Fix broken RankNTypes example in user's guide
  

• fa2aaa00
  by Simon Peyton Jones at 2025-11-27T17:56:18-05:00

  Switch off specialisation in ExactPrint
  
  In !15057 (where we re-introduced -fpolymoprhic-specialisation) we found
  that ExactPrint's compile time blew up by a factor of 5.  It turned out
  to be caused by bazillions of specialisations of `markAnnotated`.
  
  Since ExactPrint isn't perf-critical, it does not seem worth taking
  the performance hit, so this patch switches off specialisation in
  this one module.
  

• 1fd25987
  by Simon Peyton Jones at 2025-11-27T17:56:18-05:00

  Switch -fpolymorphic-specialisation on by default
  
  This patch addresses #23559.
  
  Now that !10479 has landed and #26329 is fixed, we can switch on
  polymorphic specialisation by default, addressing a bunch of other
  tickets listed in #23559.
  
  Metric changes:
    * CoOpt_Singleton: +4% compiler allocations: we just get more
      specialisations
  
    * info_table_map_perf: -20% decrease in compiler allocations.
      This is caused by using -fno-specialise in ExactPrint.hs
      Without that change we get a 4x blow-up in compile time;
      see !15058 for details
  
  Metric Decrease:
      info_table_map_perf
  Metric Increase:
      CoOpt_Singletons
  

• b7fe7445
  by Matthew Pickering at 2025-11-27T17:56:59-05:00

  rts: Fix a deadlock with eventlog flush interval and RTS shutdown
  
  The ghc_ticker thread attempts to flush at the eventlog tick interval, this requires
  waiting to take all capabilities.
  
  At the same time, the main thread is shutting down, the schedule is
  stopped and then we wait for the ticker thread to finish.
  
  Therefore we are deadlocked.
  
  The solution is to use `newBoundTask/exitMyTask`, so that flushing can
  cooperate with the scheduler shutdown.
  
  Fixes #26573
  

• 1d4a1229
  by sheaf at 2025-11-27T17:58:02-05:00

  SimpleOpt: don't subst in pushCoercionIntoLambda
  
  It was noticed in #26589 that the change in 15b311be was incorrect:
  the simple optimiser carries two different substitution-like pieces of
  information: 'soe_subst' (from InVar to OutExpr) and 'soe_inl'
  (from InId to InExpr). It is thus incorrect to have 'pushCoercionIntoLambda'
  apply the substitution from 'soe_subst' while discarding 'soe_inl'
  entirely, which is what was done in 15b311be.
  
  Instead, we change back pushCoercionIntoLambda to take an InScopeSet,
  and optimise the lambda before calling 'pushCoercionIntoLambda' to avoid
  mixing InExpr with OutExpr, or mixing two InExpr with different
  environments. We can then call 'soeZapSubst' without problems.
  
  Fixes #26588 #26589
  

• 7a632544
  by Ben Gamari at 2025-11-28T18:21:06+01:00

  hadrian: Place user options after package arguments
  
  This makes it easier for the user to override the default package
  arguments with `UserSettings.hs`.
  
  Fixes #25821.
  

2158 changed files:

• .gitlab-ci.yml
• .gitlab/ci.sh
• .gitlab/common.sh
• .gitlab/darwin/toolchain.nix
• .gitlab/generate-ci/gen_ci.hs
• .gitlab/jobs.yaml
• .gitlab/rel_eng/fetch-gitlab-artifacts/fetch_gitlab.py
• .gitlab/rel_eng/mk-ghcup-metadata/mk_ghcup_metadata.py
• .gitlab/rel_eng/upload_ghc_libs.py
• .gitmodules
• .mailmap
• CODEOWNERS
• README.md
• cabal.project-reinstall
• compiler/CodeGen.Platform.h
• compiler/GHC.hs
• compiler/GHC/Builtin/Names.hs
• compiler/GHC/Builtin/Names/TH.hs
• compiler/GHC/Builtin/PrimOps.hs
• compiler/GHC/Builtin/PrimOps/Ids.hs
• compiler/GHC/Builtin/Types.hs
• compiler/GHC/Builtin/Types/Literals.hs
• compiler/GHC/Builtin/Types/Prim.hs
• compiler/GHC/Builtin/Uniques.hs
• compiler/GHC/Builtin/primops.txt.pp
• compiler/GHC/ByteCode/Asm.hs
• + compiler/GHC/ByteCode/Breakpoints.hs
• compiler/GHC/ByteCode/InfoTable.hs
• compiler/GHC/ByteCode/Instr.hs
• compiler/GHC/ByteCode/Linker.hs
• + compiler/GHC/ByteCode/Serialize.hs
• compiler/GHC/ByteCode/Types.hs
• compiler/GHC/Cmm.hs
• compiler/GHC/Cmm/CLabel.hs
• compiler/GHC/Cmm/CommonBlockElim.hs
• compiler/GHC/Cmm/Dataflow/Label.hs
• compiler/GHC/Cmm/Info.hs
• compiler/GHC/Cmm/Info/Build.hs
• compiler/GHC/Cmm/MachOp.hs
• compiler/GHC/Cmm/Parser.y
• compiler/GHC/Cmm/Pipeline.hs
• compiler/GHC/Cmm/Sink.hs
• compiler/GHC/Cmm/UniqueRenamer.hs
• compiler/GHC/Cmm/Utils.hs
• compiler/GHC/CmmToAsm.hs
• compiler/GHC/CmmToAsm/AArch64/CodeGen.hs
• compiler/GHC/CmmToAsm/CFG.hs
• compiler/GHC/CmmToAsm/Config.hs
• compiler/GHC/CmmToAsm/Dwarf/Constants.hs
• + compiler/GHC/CmmToAsm/LA64.hs
• + compiler/GHC/CmmToAsm/LA64/CodeGen.hs
• + compiler/GHC/CmmToAsm/LA64/Cond.hs
• + compiler/GHC/CmmToAsm/LA64/Instr.hs
• + compiler/GHC/CmmToAsm/LA64/Ppr.hs
• + compiler/GHC/CmmToAsm/LA64/RegInfo.hs
• + compiler/GHC/CmmToAsm/LA64/Regs.hs
• compiler/GHC/CmmToAsm/PIC.hs
• compiler/GHC/CmmToAsm/PPC/Ppr.hs
• compiler/GHC/CmmToAsm/Ppr.hs
• compiler/GHC/CmmToAsm/RV64/CodeGen.hs
• compiler/GHC/CmmToAsm/Reg/Graph/TrivColorable.hs
• compiler/GHC/CmmToAsm/Reg/Linear.hs
• compiler/GHC/CmmToAsm/Reg/Linear/FreeRegs.hs
• + compiler/GHC/CmmToAsm/Reg/Linear/LA64.hs
• compiler/GHC/CmmToAsm/Reg/Liveness.hs
• compiler/GHC/CmmToAsm/Reg/Target.hs
• compiler/GHC/CmmToAsm/Wasm/FromCmm.hs
• compiler/GHC/CmmToAsm/X86/CodeGen.hs
• compiler/GHC/CmmToAsm/X86/Instr.hs
• compiler/GHC/CmmToAsm/X86/Ppr.hs
• compiler/GHC/CmmToC.hs
• compiler/GHC/CmmToLlvm/Base.hs
• compiler/GHC/CmmToLlvm/CodeGen.hs
• compiler/GHC/CmmToLlvm/Data.hs
• compiler/GHC/Core.hs
• compiler/GHC/Core/Class.hs
• compiler/GHC/Core/Coercion.hs
• compiler/GHC/Core/Coercion.hs-boot
• compiler/GHC/Core/Coercion/Opt.hs
• compiler/GHC/Core/ConLike.hs
• compiler/GHC/Core/DataCon.hs
• compiler/GHC/Core/DataCon.hs-boot
• compiler/GHC/Core/FVs.hs
• compiler/GHC/Core/FamInstEnv.hs
• compiler/GHC/Core/LateCC/OverloadedCalls.hs
• compiler/GHC/Core/Lint.hs
• compiler/GHC/Core/Make.hs
• compiler/GHC/Core/Map/Expr.hs
• compiler/GHC/Core/Multiplicity.hs
• compiler/GHC/Core/Opt/Arity.hs
• compiler/GHC/Core/Opt/CallArity.hs
• compiler/GHC/Core/Opt/ConstantFold.hs
• compiler/GHC/Core/Opt/CprAnal.hs
• compiler/GHC/Core/Opt/DmdAnal.hs
• compiler/GHC/Core/Opt/Monad.hs
• compiler/GHC/Core/Opt/OccurAnal.hs
• compiler/GHC/Core/Opt/Pipeline.hs
• compiler/GHC/Core/Opt/Pipeline/Types.hs
• compiler/GHC/Core/Opt/SetLevels.hs
• compiler/GHC/Core/Opt/Simplify.hs
• compiler/GHC/Core/Opt/Simplify/Env.hs
• compiler/GHC/Core/Opt/Simplify/Inline.hs
• compiler/GHC/Core/Opt/Simplify/Iteration.hs
• compiler/GHC/Core/Opt/Simplify/Monad.hs
• compiler/GHC/Core/Opt/Simplify/Utils.hs
• compiler/GHC/Core/Opt/SpecConstr.hs
• compiler/GHC/Core/Opt/Specialise.hs
• compiler/GHC/Core/Opt/WorkWrap.hs
• compiler/GHC/Core/Opt/WorkWrap/Utils.hs
• compiler/GHC/Core/PatSyn.hs
• compiler/GHC/Core/Ppr.hs
• compiler/GHC/Core/Predicate.hs
• compiler/GHC/Core/Reduction.hs
• compiler/GHC/Core/RoughMap.hs
• compiler/GHC/Core/Rules.hs
• compiler/GHC/Core/Rules/Config.hs
• compiler/GHC/Core/SimpleOpt.hs
• compiler/GHC/Core/Subst.hs
• compiler/GHC/Core/Tidy.hs
• compiler/GHC/Core/TyCo/Compare.hs
• compiler/GHC/Core/TyCo/FVs.hs
• compiler/GHC/Core/TyCo/Ppr.hs
• compiler/GHC/Core/TyCo/Rep.hs
• compiler/GHC/Core/TyCo/Subst.hs
• compiler/GHC/Core/TyCo/Tidy.hs
• compiler/GHC/Core/TyCon.hs
• compiler/GHC/Core/Type.hs
• compiler/GHC/Core/Unfold.hs
• compiler/GHC/Core/Unfold/Make.hs
• compiler/GHC/Core/Unify.hs
• compiler/GHC/Core/Utils.hs
• compiler/GHC/CoreToIface.hs
• compiler/GHC/CoreToStg.hs
• + compiler/GHC/CoreToStg/AddImplicitBinds.hs
• compiler/GHC/CoreToStg/Prep.hs
• compiler/GHC/Data/FlatBag.hs
• compiler/GHC/Data/IOEnv.hs
• compiler/GHC/Data/SmallArray.hs
• compiler/GHC/Data/Word64Map/Internal.hs
• compiler/GHC/Data/Word64Map/Lazy.hs
• compiler/GHC/Driver/Backend.hs
• compiler/GHC/Driver/Backend/Internal.hs
• compiler/GHC/Driver/Backpack.hs
• + compiler/GHC/Driver/ByteCode.hs
• compiler/GHC/Driver/CmdLine.hs
• compiler/GHC/Driver/CodeOutput.hs
• compiler/GHC/Driver/Config.hs
• compiler/GHC/Driver/Config/CmmToAsm.hs
• compiler/GHC/Driver/Config/Core/Lint.hs
• compiler/GHC/Driver/Config/Core/Opt/Simplify.hs
• compiler/GHC/Driver/Config/Core/Rules.hs
• compiler/GHC/Driver/Config/Finder.hs
• + compiler/GHC/Driver/Config/Interpreter.hs
• compiler/GHC/Driver/Config/Linker.hs
• compiler/GHC/Driver/Config/Stg/Debug.hs
• compiler/GHC/Driver/Downsweep.hs
• compiler/GHC/Driver/DynFlags.hs
• compiler/GHC/Driver/Env.hs
• compiler/GHC/Driver/Env/Types.hs
• compiler/GHC/Driver/Errors.hs
• compiler/GHC/Driver/Errors/Ppr.hs
• compiler/GHC/Driver/Flags.hs
• compiler/GHC/Driver/Main.hs
• compiler/GHC/Driver/Make.hs
• compiler/GHC/Driver/MakeFile.hs
• compiler/GHC/Driver/Messager.hs
• compiler/GHC/Driver/Monad.hs
• compiler/GHC/Driver/Pipeline.hs
• compiler/GHC/Driver/Pipeline/Execute.hs
• compiler/GHC/Driver/Plugins.hs
• compiler/GHC/Driver/Session.hs
• + compiler/GHC/Driver/Session/Inspect.hs
• compiler/GHC/Hs.hs
• compiler/GHC/Hs/Binds.hs
• compiler/GHC/Hs/Decls.hs
• compiler/GHC/Hs/Expr.hs
• compiler/GHC/Hs/Expr.hs-boot
• compiler/GHC/Hs/ImpExp.hs
• compiler/GHC/Hs/Instances.hs
• compiler/GHC/Hs/Pat.hs
• compiler/GHC/Hs/Syn/Type.hs
• compiler/GHC/Hs/Type.hs
• compiler/GHC/Hs/Utils.hs
• compiler/GHC/HsToCore.hs
• compiler/GHC/HsToCore/Binds.hs
• compiler/GHC/HsToCore/Breakpoints.hs
• compiler/GHC/HsToCore/Docs.hs
• compiler/GHC/HsToCore/Errors/Ppr.hs
• compiler/GHC/HsToCore/Errors/Types.hs
• compiler/GHC/HsToCore/Expr.hs
• compiler/GHC/HsToCore/Foreign/C.hs
• compiler/GHC/HsToCore/Foreign/Call.hs
• compiler/GHC/HsToCore/Foreign/JavaScript.hs
• compiler/GHC/HsToCore/Foreign/Wasm.hs
• compiler/GHC/HsToCore/Match.hs
• compiler/GHC/HsToCore/Monad.hs
• compiler/GHC/HsToCore/Pmc/Ppr.hs
• compiler/GHC/HsToCore/Pmc/Solver.hs
• compiler/GHC/HsToCore/Pmc/Solver/Types.hs
• compiler/GHC/HsToCore/Pmc/Types.hs
• compiler/GHC/HsToCore/Pmc/Utils.hs
• compiler/GHC/HsToCore/Quote.hs
• compiler/GHC/HsToCore/Ticks.hs
• compiler/GHC/HsToCore/Usage.hs
• compiler/GHC/HsToCore/Utils.hs
• compiler/GHC/Iface/Binary.hs
• compiler/GHC/Iface/Decl.hs
• compiler/GHC/Iface/Errors/Ppr.hs
• compiler/GHC/Iface/Ext/Ast.hs
• compiler/GHC/Iface/Ext/Binary.hs
• compiler/GHC/Iface/Ext/Types.hs
• compiler/GHC/Iface/Flags.hs
• compiler/GHC/Iface/Load.hs
• compiler/GHC/Iface/Make.hs
• compiler/GHC/Iface/Recomp.hs
• compiler/GHC/Iface/Recomp/Flags.hs
• compiler/GHC/Iface/Recomp/Types.hs
• compiler/GHC/Iface/Rename.hs
• compiler/GHC/Iface/Syntax.hs
• compiler/GHC/Iface/Tidy.hs
• compiler/GHC/Iface/Tidy/StaticPtrTable.hs
• compiler/GHC/Iface/Type.hs
• compiler/GHC/IfaceToCore.hs
• compiler/GHC/JS/JStg/Monad.hs
• compiler/GHC/Linker/Config.hs
• compiler/GHC/Linker/Deps.hs
• compiler/GHC/Linker/Dynamic.hs
• + compiler/GHC/Linker/Executable.hs
• − compiler/GHC/Linker/ExtraObj.hs
• compiler/GHC/Linker/Loader.hs
• compiler/GHC/Linker/MacOS.hs
• compiler/GHC/Linker/Static.hs
• compiler/GHC/Linker/Types.hs
• compiler/GHC/Linker/Windows.hs
• compiler/GHC/Llvm/Ppr.hs
• compiler/GHC/Llvm/Types.hs
• compiler/GHC/Parser.y
• compiler/GHC/Parser/Errors/Ppr.hs
• compiler/GHC/Parser/Errors/Types.hs
• compiler/GHC/Parser/Header.hs
• compiler/GHC/Parser/Lexer.x
• compiler/GHC/Parser/Lexer/String.x
• compiler/GHC/Parser/PostProcess.hs
• compiler/GHC/Parser/PostProcess/Haddock.hs
• compiler/GHC/Parser/Types.hs
• compiler/GHC/Platform.hs
• compiler/GHC/Platform/LoongArch64.hs → compiler/GHC/Platform/LA64.hs
• compiler/GHC/Platform/Reg.hs
• compiler/GHC/Platform/Regs.hs
• compiler/GHC/Plugins.hs
• compiler/GHC/Rename/Bind.hs
• compiler/GHC/Rename/Env.hs
• compiler/GHC/Rename/Expr.hs
• compiler/GHC/Rename/HsType.hs
• compiler/GHC/Rename/Module.hs
• compiler/GHC/Rename/Names.hs
• compiler/GHC/Rename/Pat.hs
• compiler/GHC/Rename/Splice.hs
• compiler/GHC/Rename/Unbound.hs
• compiler/GHC/Rename/Utils.hs
• compiler/GHC/Runtime/Context.hs
• compiler/GHC/Runtime/Debugger/Breakpoints.hs
• compiler/GHC/Runtime/Eval.hs
• compiler/GHC/Runtime/Eval/Types.hs
• compiler/GHC/Runtime/Heap/Inspect.hs
• compiler/GHC/Runtime/Interpreter.hs
• + compiler/GHC/Runtime/Interpreter/C.hs
• + compiler/GHC/Runtime/Interpreter/Init.hs
• compiler/GHC/Runtime/Interpreter/Types.hs
• compiler/GHC/Runtime/Loader.hs
• compiler/GHC/Settings.hs
• compiler/GHC/Settings/IO.hs
• compiler/GHC/Stg/BcPrep.hs
• compiler/GHC/Stg/Debug.hs
• + compiler/GHC/Stg/Debug/Types.hs
• compiler/GHC/Stg/EnforceEpt.hs
• compiler/GHC/Stg/EnforceEpt/Types.hs
• compiler/GHC/Stg/FVs.hs
• compiler/GHC/Stg/Lint.hs
• compiler/GHC/Stg/Pipeline.hs
• compiler/GHC/Stg/Unarise.hs
• compiler/GHC/StgToByteCode.hs
• compiler/GHC/StgToCmm.hs
• compiler/GHC/StgToCmm/DataCon.hs
• compiler/GHC/StgToCmm/ExtCode.hs
• compiler/GHC/StgToCmm/InfoTableProv.hs
• compiler/GHC/StgToCmm/Layout.hs
• compiler/GHC/StgToCmm/Monad.hs
• compiler/GHC/StgToCmm/Prim.hs
• compiler/GHC/StgToJS/Apply.hs
• compiler/GHC/StgToJS/CodeGen.hs
• compiler/GHC/StgToJS/Expr.hs
• compiler/GHC/StgToJS/Ids.hs
• compiler/GHC/StgToJS/Linker/Linker.hs
• compiler/GHC/StgToJS/Prim.hs
• compiler/GHC/StgToJS/Regs.hs
• compiler/GHC/StgToJS/Rts/Rts.hs
• compiler/GHC/StgToJS/Rts/Types.hs
• compiler/GHC/StgToJS/StaticPtr.hs
• compiler/GHC/SysTools/Ar.hs
• compiler/GHC/SysTools/BaseDir.hs
• compiler/GHC/SysTools/Cpp.hs
• compiler/GHC/SysTools/Process.hs
• compiler/GHC/SysTools/Tasks.hs
• compiler/GHC/Tc/Deriv.hs
• compiler/GHC/Tc/Deriv/Generate.hs
• compiler/GHC/Tc/Deriv/Generics.hs
• compiler/GHC/Tc/Deriv/Infer.hs
• compiler/GHC/Tc/Deriv/Utils.hs
• compiler/GHC/Tc/Errors.hs
• compiler/GHC/Tc/Errors/Hole.hs
• compiler/GHC/Tc/Errors/Ppr.hs
• compiler/GHC/Tc/Errors/Types.hs
• compiler/GHC/Tc/Gen/App.hs
• compiler/GHC/Tc/Gen/Bind.hs
• compiler/GHC/Tc/Gen/Export.hs
• compiler/GHC/Tc/Gen/Expr.hs
• compiler/GHC/Tc/Gen/Expr.hs-boot
• compiler/GHC/Tc/Gen/Head.hs
• compiler/GHC/Tc/Gen/HsType.hs
• compiler/GHC/Tc/Gen/Match.hs
• compiler/GHC/Tc/Gen/Pat.hs
• compiler/GHC/Tc/Gen/Sig.hs
• compiler/GHC/Tc/Gen/Splice.hs
• compiler/GHC/Tc/Gen/Splice.hs-boot
• compiler/GHC/Tc/Instance/Class.hs
• compiler/GHC/Tc/Instance/Family.hs
• compiler/GHC/Tc/Instance/FunDeps.hs
• compiler/GHC/Tc/Module.hs
• compiler/GHC/Tc/Plugin.hs
• compiler/GHC/Tc/Solver.hs
• compiler/GHC/Tc/Solver/Default.hs
• compiler/GHC/Tc/Solver/Dict.hs
• compiler/GHC/Tc/Solver/Equality.hs
• + compiler/GHC/Tc/Solver/FunDeps.hs
• compiler/GHC/Tc/Solver/InertSet.hs
• compiler/GHC/Tc/Solver/Irred.hs
• compiler/GHC/Tc/Solver/Monad.hs
• compiler/GHC/Tc/Solver/Rewrite.hs
• compiler/GHC/Tc/Solver/Solve.hs
• + compiler/GHC/Tc/Solver/Solve.hs-boot
• compiler/GHC/Tc/Solver/Types.hs
• compiler/GHC/Tc/TyCl.hs
• compiler/GHC/Tc/TyCl/Build.hs
• compiler/GHC/Tc/TyCl/Instance.hs
• compiler/GHC/Tc/TyCl/PatSyn.hs
• compiler/GHC/Tc/TyCl/Utils.hs
• compiler/GHC/Tc/Types.hs
• compiler/GHC/Tc/Types/Constraint.hs
• compiler/GHC/Tc/Types/CtLoc.hs
• compiler/GHC/Tc/Types/ErrCtxt.hs
• − compiler/GHC/Tc/Types/EvTerm.hs
• compiler/GHC/Tc/Types/Evidence.hs
• compiler/GHC/Tc/Types/Origin.hs
• compiler/GHC/Tc/Types/TH.hs
• compiler/GHC/Tc/Utils/Concrete.hs
• compiler/GHC/Tc/Utils/Instantiate.hs
• compiler/GHC/Tc/Utils/Monad.hs
• compiler/GHC/Tc/Utils/TcMType.hs
• compiler/GHC/Tc/Utils/TcType.hs
• compiler/GHC/Tc/Utils/Unify.hs
• compiler/GHC/Tc/Utils/Unify.hs-boot
• compiler/GHC/Tc/Validity.hs
• compiler/GHC/Tc/Zonk/TcType.hs
• compiler/GHC/Tc/Zonk/Type.hs
• compiler/GHC/ThToHs.hs
• compiler/GHC/Types/Basic.hs
• − compiler/GHC/Types/Breakpoint.hs
• compiler/GHC/Types/Demand.hs
• compiler/GHC/Types/Error.hs
• compiler/GHC/Types/Error/Codes.hs
• compiler/GHC/Types/Hint.hs
• compiler/GHC/Types/Hint/Ppr.hs
• compiler/GHC/Types/Id.hs
• compiler/GHC/Types/Id/Make.hs
• compiler/GHC/Types/Name/Cache.hs
• compiler/GHC/Types/Name/Ppr.hs
• compiler/GHC/Types/Name/Reader.hs
• compiler/GHC/Types/RepType.hs
• compiler/GHC/Types/SourceError.hs
• compiler/GHC/Types/SourceText.hs
• compiler/GHC/Types/SptEntry.hs
• compiler/GHC/Types/ThLevelIndex.hs
• compiler/GHC/Types/Tickish.hs
• compiler/GHC/Types/TyThing.hs
• compiler/GHC/Types/TyThing/Ppr.hs
• compiler/GHC/Types/Unique.hs
• compiler/GHC/Types/Unique/DFM.hs
• compiler/GHC/Types/Unique/DSM.hs
• compiler/GHC/Types/Unique/FM.hs
• compiler/GHC/Types/Unique/Set.hs
• compiler/GHC/Types/Unique/Supply.hs
• compiler/GHC/Types/Var.hs
• compiler/GHC/Types/Var.hs-boot
• compiler/GHC/Types/Var/Env.hs
• compiler/GHC/Unit/Env.hs
• compiler/GHC/Unit/Finder.hs
• compiler/GHC/Unit/Finder/Types.hs
• compiler/GHC/Unit/Home/Graph.hs
• compiler/GHC/Unit/Home/ModInfo.hs
• compiler/GHC/Unit/Module/Deps.hs
• compiler/GHC/Unit/Module/Graph.hs
• compiler/GHC/Unit/Module/Location.hs
• compiler/GHC/Unit/Module/ModGuts.hs
• compiler/GHC/Unit/Module/ModSummary.hs
• compiler/GHC/Unit/Module/Status.hs
• compiler/GHC/Unit/Module/WholeCoreBindings.hs
• compiler/GHC/Unit/State.hs
• compiler/GHC/Unit/Types.hs
• compiler/GHC/Utils/Binary.hs
• + compiler/GHC/Utils/EndoOS.hs
• compiler/GHC/Utils/Error.hs
• compiler/GHC/Utils/Logger.hs
• compiler/GHC/Utils/Outputable.hs
• compiler/GHC/Utils/Panic.hs
• compiler/GHC/Utils/Ppr.hs
• compiler/Language/Haskell/Syntax/Binds.hs
• compiler/Language/Haskell/Syntax/Decls.hs
• compiler/Language/Haskell/Syntax/Expr.hs
• compiler/Language/Haskell/Syntax/Extension.hs
• compiler/Language/Haskell/Syntax/ImpExp.hs
• compiler/Language/Haskell/Syntax/Pat.hs
• compiler/Setup.hs
• compiler/cbits/keepCAFsForGHCi.c
• compiler/ghc.cabal.in
• configure.ac
• distrib/configure.ac.in
• docs/users_guide/9.14.1-notes.rst → docs/users_guide/9.16.1-notes.rst
• docs/users_guide/bugs.rst
• docs/users_guide/compare-flags.py
• docs/users_guide/conf.py
• docs/users_guide/debug-info.rst
• docs/users_guide/debugging.rst
• + docs/users_guide/diagnostics-as-json-schema-1_2.json
• docs/users_guide/eventlog-formats.rst
• docs/users_guide/expected-undocumented-flags.txt
• docs/users_guide/extending_ghc.rst
• docs/users_guide/exts/arrows.rst
• docs/users_guide/exts/data_kinds.rst
• docs/users_guide/exts/derive_any_class.rst
• docs/users_guide/exts/deriving_extra.rst
• docs/users_guide/exts/deriving_inferred.rst
• docs/users_guide/exts/deriving_strategies.rst
• docs/users_guide/exts/doandifthenelse.rst
• docs/users_guide/exts/explicit_namespaces.rst
• docs/users_guide/exts/ffi.rst
• docs/users_guide/exts/gadt.rst
• docs/users_guide/exts/gadt_syntax.rst
• docs/users_guide/exts/generics.rst
• docs/users_guide/exts/linear_types.rst
• docs/users_guide/exts/overloaded_labels.rst
• docs/users_guide/exts/overloaded_strings.rst
• docs/users_guide/exts/pattern_synonyms.rst
• docs/users_guide/exts/poly_kinds.rst
• docs/users_guide/exts/pragmas.rst
• docs/users_guide/exts/primitives.rst
• docs/users_guide/exts/rank_polymorphism.rst
• docs/users_guide/exts/rebindable_syntax.rst
• + docs/users_guide/exts/relaxed_poly_rec.rst
• docs/users_guide/exts/required_type_arguments.rst
• docs/users_guide/exts/scoped_type_variables.rst
• docs/users_guide/exts/standalone_deriving.rst
• docs/users_guide/exts/strict.rst
• docs/users_guide/exts/template_haskell.rst
• docs/users_guide/exts/tuple_sections.rst
• docs/users_guide/exts/type_data.rst
• docs/users_guide/exts/type_defaulting.rst
• docs/users_guide/exts/type_families.rst
• docs/users_guide/exts/types.rst
• docs/users_guide/flags.py
• docs/users_guide/ghci.rst
• docs/users_guide/gone_wrong.rst
• docs/users_guide/hints.rst
• docs/users_guide/javascript.rst
• docs/users_guide/phases.rst
• docs/users_guide/profiling.rst
• docs/users_guide/release-notes.rst
• docs/users_guide/runtime_control.rst
• docs/users_guide/separate_compilation.rst
• docs/users_guide/using-optimisation.rst
• docs/users_guide/using-warnings.rst
• docs/users_guide/using.rst
• docs/users_guide/wasm.rst
• docs/users_guide/win32-dlls.rst
• ghc/GHCi/UI.hs
• ghc/GHCi/UI/Exception.hs
• ghc/GHCi/UI/Info.hs
• ghc/GHCi/UI/Monad.hs
• ghc/GHCi/UI/Print.hs
• ghc/Main.hs
• ghc/ghc-bin.cabal.in
• hadrian/bindist/Makefile
• hadrian/bindist/config.mk.in
• hadrian/bootstrap/generate_bootstrap_plans
• hadrian/bootstrap/hadrian-bootstrap-gen.cabal
• hadrian/bootstrap/plan-9_10_1.json
• hadrian/bootstrap/plan-9_6_5.json → hadrian/bootstrap/plan-9_10_2.json
• hadrian/bootstrap/plan-9_6_6.json → hadrian/bootstrap/plan-9_12_1.json
• hadrian/bootstrap/plan-9_6_4.json → hadrian/bootstrap/plan-9_12_2.json
• − hadrian/bootstrap/plan-9_6_1.json
• − hadrian/bootstrap/plan-9_6_2.json
• − hadrian/bootstrap/plan-9_6_3.json
• − hadrian/bootstrap/plan-9_8_1.json
• − hadrian/bootstrap/plan-9_8_2.json
• hadrian/bootstrap/plan-bootstrap-9_10_1.json
• hadrian/bootstrap/plan-bootstrap-9_6_5.json → hadrian/bootstrap/plan-bootstrap-9_10_2.json
• hadrian/bootstrap/plan-bootstrap-9_6_6.json → hadrian/bootstrap/plan-bootstrap-9_12_1.json
• hadrian/bootstrap/plan-bootstrap-9_8_1.json → hadrian/bootstrap/plan-bootstrap-9_12_2.json
• − hadrian/bootstrap/plan-bootstrap-9_6_1.json
• − hadrian/bootstrap/plan-bootstrap-9_6_2.json
• − hadrian/bootstrap/plan-bootstrap-9_6_3.json
• − hadrian/bootstrap/plan-bootstrap-9_6_4.json
• − hadrian/bootstrap/plan-bootstrap-9_8_2.json
• hadrian/bootstrap/src/Main.hs
• hadrian/cfg/default.host.target.in
• hadrian/cfg/default.target.in
• hadrian/cfg/system.config.in
• hadrian/doc/flavours.md
• hadrian/doc/user-settings.md
• hadrian/hadrian.cabal
• hadrian/src/Base.hs
• hadrian/src/Builder.hs
• hadrian/src/Context.hs
• hadrian/src/Context/Path.hs
• hadrian/src/Flavour.hs
• hadrian/src/Flavour/Type.hs
• hadrian/src/Oracles/Flag.hs
• hadrian/src/Oracles/Setting.hs
• hadrian/src/Oracles/TestSettings.hs
• hadrian/src/Packages.hs
• hadrian/src/Rules/Generate.hs
• hadrian/src/Rules/Gmp.hs
• hadrian/src/Rules/Libffi.hs
• hadrian/src/Rules/ToolArgs.hs
• hadrian/src/Settings.hs
• hadrian/src/Settings/Builders/Cabal.hs
• hadrian/src/Settings/Builders/Common.hs
• hadrian/src/Settings/Builders/DeriveConstants.hs
• hadrian/src/Settings/Builders/Ghc.hs
• hadrian/src/Settings/Builders/Hsc2Hs.hs
• hadrian/src/Settings/Builders/RunTest.hs
• hadrian/src/Settings/Default.hs
• hadrian/src/Settings/Flavours/Release.hs
• hadrian/src/Settings/Packages.hs
• hadrian/src/Settings/Program.hs
• hadrian/src/Settings/Warnings.hs
• hadrian/stack.yaml
• hadrian/stack.yaml.lock
• libffi-tarballs
• libraries/Cabal
• libraries/Win32
• libraries/array
• libraries/base/base.cabal.in
• libraries/base/changelog.md
• libraries/base/src/Control/Applicative.hs
• libraries/base/src/Control/Exception.hs
• libraries/base/src/Control/Monad.hs
• libraries/base/src/Data/Array/Byte.hs
• libraries/base/src/Data/Bifunctor.hs
• libraries/base/src/Data/Fixed.hs
• libraries/base/src/Data/List.hs
• libraries/base/src/Data/List/NonEmpty.hs
• + libraries/base/src/Data/List/NubOrdSet.hs
• libraries/base/src/GHC/Base.hs
• libraries/base/src/GHC/Exts.hs
• libraries/base/src/GHC/Generics.hs
• − libraries/base/src/GHC/IOPort.hs
• libraries/base/src/GHC/JS/Prim/Internal/Build.hs
• libraries/base/src/GHC/RTS/Flags.hs
• libraries/base/src/GHC/Stack/CloneStack.hs
• libraries/base/src/GHC/Weak/Finalize.hs
• libraries/base/src/System/Console/GetOpt.hs
• libraries/base/tests/IO/withBinaryFile002.stderr
• libraries/base/tests/IO/withFile002.stderr
• libraries/base/tests/IO/withFileBlocking002.stderr
• libraries/base/tests/all.T
• libraries/base/tests/unicode002.stdout
• libraries/base/tests/unicode003.stdout
• libraries/binary
• libraries/containers
• libraries/deepseq
• libraries/directory
• libraries/exceptions
• libraries/filepath
• libraries/ghc-bignum/changelog.md
• + libraries/ghc-boot-th/GHC/Boot/TH/Monad.hs
• libraries/ghc-boot-th/GHC/Boot/TH/Ppr.hs
• libraries/ghc-boot-th/ghc-boot-th.cabal.in
• libraries/ghc-boot/GHC/Settings/Utils.hs
• libraries/ghc-boot/Setup.hs
• libraries/ghc-boot/ghc-boot.cabal.in
• libraries/ghc-compact/GHC/Compact.hs
• libraries/ghc-compact/GHC/Compact/Serialized.hs
• libraries/ghc-compact/ghc-compact.cabal
• libraries/ghc-experimental/CHANGELOG.md
• libraries/ghc-experimental/ghc-experimental.cabal.in
• + libraries/ghc-experimental/src/GHC/Exception/Backtrace/Experimental.hs
• + libraries/ghc-experimental/src/GHC/Stack/Annotation/Experimental.hs
• + libraries/ghc-experimental/src/System/Mem/Experimental.hs
• libraries/ghc-heap/GHC/Exts/Heap.hs
• libraries/ghc-heap/GHC/Exts/Heap/ClosureTypes.hs
• libraries/ghc-heap/GHC/Exts/Heap/Closures.hs
• + libraries/ghc-heap/GHC/Exts/Heap/Constants.hs
• libraries/ghc-heap/GHC/Exts/Heap/FFIClosures_ProfilingDisabled.hsc
• libraries/ghc-heap/GHC/Exts/Heap/FFIClosures_ProfilingEnabled.hsc
• + libraries/ghc-heap/GHC/Exts/Heap/InfoTable.hs
• + libraries/ghc-heap/GHC/Exts/Heap/InfoTable/Types.hs
• + libraries/ghc-heap/GHC/Exts/Heap/InfoTableProf.hs
• libraries/ghc-heap/GHC/Exts/Heap/ProfInfo/Types.hs
• libraries/ghc-heap/GHC/Exts/Heap/Utils.hsc
• libraries/ghc-heap/GHC/Exts/Stack.hs
• + libraries/ghc-heap/GHC/Exts/Stack/Constants.hs
• libraries/ghc-heap/GHC/Exts/Stack/Decode.hs
• libraries/ghc-heap/ghc-heap.cabal.in
• libraries/ghc-heap/tests/parse_tso_flags.hs
• libraries/ghc-heap/cbits/HeapPrim.cmm → libraries/ghc-internal/cbits/HeapPrim.cmm
• + libraries/ghc-internal/cbits/RtsIface.c
• libraries/ghc-heap/cbits/Stack.cmm → libraries/ghc-internal/cbits/Stack.cmm
• libraries/ghc-internal/cbits/StackCloningDecoding.cmm
• libraries/ghc-heap/cbits/Stack_c.c → libraries/ghc-internal/cbits/Stack_c.c
• libraries/ghc-internal/codepages/MakeTable.hs
• libraries/ghc-internal/codepages/Makefile
• libraries/ghc-internal/ghc-internal.cabal.in
• + libraries/ghc-internal/include/RtsIfaceSymbols.h
• libraries/ghc-internal/jsbits/base.js
• + libraries/ghc-internal/src/GHC/Internal/AllocationLimitHandler.hs
• libraries/ghc-internal/src/GHC/Internal/Base.hs
• libraries/ghc-internal/src/GHC/Internal/Bignum/Integer.hs
• libraries/ghc-internal/src/GHC/Internal/Bignum/Natural.hs
• libraries/ghc-internal/src/GHC/Internal/ClosureTypes.hs
• libraries/ghc-internal/src/GHC/Internal/Control/Monad.hs
• libraries/ghc-internal/src/GHC/Internal/Control/Monad/Fail.hs
• libraries/ghc-internal/src/GHC/Internal/Data/Data.hs
• libraries/ghc-internal/src/GHC/Internal/Data/Maybe.hs
• libraries/ghc-internal/src/GHC/Internal/Data/OldList.hs
• libraries/ghc-internal/src/GHC/Internal/Data/Typeable/Internal.hs
• libraries/ghc-internal/src/GHC/Internal/Event/Windows.hsc
• libraries/ghc-internal/src/GHC/Internal/Event/Windows/Thread.hs
• libraries/ghc-internal/src/GHC/Internal/Exception.hs
• libraries/ghc-internal/src/GHC/Internal/Exception/Backtrace.hs
• libraries/ghc-internal/src/GHC/Internal/Exception/Backtrace.hs-boot
• libraries/ghc-internal/src/GHC/Internal/Exception/Type.hs
• libraries/ghc-internal/src/GHC/Internal/Exception/Type.hs-boot
• libraries/ghc-internal/src/GHC/Internal/Exts.hs
• libraries/ghc-internal/src/GHC/Internal/Float.hs
• + libraries/ghc-internal/src/GHC/Internal/Heap/Closures.hs
• libraries/ghc-heap/GHC/Exts/Heap/Constants.hsc → libraries/ghc-internal/src/GHC/Internal/Heap/Constants.hsc
• libraries/ghc-heap/GHC/Exts/Heap/InfoTable.hsc → libraries/ghc-internal/src/GHC/Internal/Heap/InfoTable.hsc
• libraries/ghc-heap/GHC/Exts/Heap/InfoTable/Types.hsc → libraries/ghc-internal/src/GHC/Internal/Heap/InfoTable/Types.hsc
• libraries/ghc-heap/GHC/Exts/Heap/InfoTableProf.hsc → libraries/ghc-internal/src/GHC/Internal/Heap/InfoTableProf.hsc
• + libraries/ghc-internal/src/GHC/Internal/Heap/ProfInfo/Types.hs
• libraries/ghc-internal/src/GHC/Internal/IO.hs-boot
• libraries/ghc-internal/src/GHC/Internal/IO/Buffer.hs
• libraries/ghc-internal/src/GHC/Internal/IO/Exception.hs-boot
• libraries/ghc-internal/src/GHC/Internal/IO/Windows/Handle.hsc
• − libraries/ghc-internal/src/GHC/Internal/IOPort.hs
• libraries/ghc-internal/src/GHC/Internal/List.hs
• libraries/ghc-internal/src/GHC/Internal/Prim/PtrEq.hs
• libraries/ghc-internal/src/GHC/Internal/RTS/Flags.hsc
• libraries/ghc-internal/src/GHC/Internal/Real.hs
• libraries/ghc-internal/src/GHC/Internal/ResponseFile.hs
• + libraries/ghc-internal/src/GHC/Internal/Stack/Annotation.hs
• libraries/ghc-internal/src/GHC/Internal/Stack/CloneStack.hs
• libraries/ghc-heap/GHC/Exts/Stack/Constants.hsc → libraries/ghc-internal/src/GHC/Internal/Stack/Constants.hsc
• + libraries/ghc-internal/src/GHC/Internal/Stack/ConstantsProf.hsc
• + libraries/ghc-internal/src/GHC/Internal/Stack/Decode.hs
• libraries/ghc-internal/src/GHC/Internal/System/IO.hs
• libraries/ghc-internal/src/GHC/Internal/System/Posix/Internals.hs
• libraries/ghc-internal/src/GHC/Internal/TH/Lib.hs
• libraries/ghc-internal/src/GHC/Internal/TH/Lift.hs
• + libraries/ghc-internal/src/GHC/Internal/TH/Monad.hs
• libraries/ghc-internal/src/GHC/Internal/TH/Quote.hs
• libraries/ghc-internal/src/GHC/Internal/TH/Syntax.hs
• libraries/ghc-internal/src/GHC/Internal/Type/Reflection.hs
• libraries/ghc-internal/src/GHC/Internal/TypeLits.hs
• libraries/ghc-internal/src/GHC/Internal/TypeNats.hs
• libraries/ghc-internal/src/GHC/Internal/Unicode/Char/DerivedCoreProperties.hs
• libraries/ghc-internal/src/GHC/Internal/Unicode/Char/UnicodeData/GeneralCategory.hs
• libraries/ghc-internal/src/GHC/Internal/Unicode/Char/UnicodeData/SimpleLowerCaseMapping.hs
• libraries/ghc-internal/src/GHC/Internal/Unicode/Char/UnicodeData/SimpleTitleCaseMapping.hs
• libraries/ghc-internal/src/GHC/Internal/Unicode/Char/UnicodeData/SimpleUpperCaseMapping.hs
• libraries/ghc-internal/src/GHC/Internal/Unicode/Version.hs
• + libraries/ghc-internal/tests/Makefile
• + libraries/ghc-internal/tests/all.T
• + libraries/ghc-internal/tests/backtraces/Makefile
• + libraries/ghc-internal/tests/backtraces/T14532a.hs
• + libraries/ghc-internal/tests/backtraces/T14532a.stdout
• + libraries/ghc-internal/tests/backtraces/T14532b.hs
• + libraries/ghc-internal/tests/backtraces/T14532b.stdout
• + libraries/ghc-internal/tests/backtraces/T26507.hs
• + libraries/ghc-internal/tests/backtraces/T26507.stderr
• + libraries/ghc-internal/tests/backtraces/all.T
• + libraries/ghc-internal/tests/stack-annotation/Makefile
• + libraries/ghc-internal/tests/stack-annotation/TestUtils.hs
• + libraries/ghc-internal/tests/stack-annotation/all.T
• + libraries/ghc-internal/tests/stack-annotation/ann_frame001.hs
• + libraries/ghc-internal/tests/stack-annotation/ann_frame001.stdout
• + libraries/ghc-internal/tests/stack-annotation/ann_frame002.hs
• + libraries/ghc-internal/tests/stack-annotation/ann_frame002.stdout
• + libraries/ghc-internal/tests/stack-annotation/ann_frame003.hs
• + libraries/ghc-internal/tests/stack-annotation/ann_frame003.stdout
• + libraries/ghc-internal/tests/stack-annotation/ann_frame004.hs
• + libraries/ghc-internal/tests/stack-annotation/ann_frame004.stdout
• libraries/ghc-internal/tools/ucd2haskell/ucd.sh
• libraries/ghc-internal/tools/ucd2haskell/ucd2haskell.cabal
• libraries/ghc-internal/tools/ucd2haskell/unicode_version
• libraries/ghc-prim/changelog.md
• libraries/ghc-prim/ghc-prim.cabal
• libraries/ghci/GHCi/CreateBCO.hs
• + libraries/ghci/GHCi/Debugger.hs
• libraries/ghci/GHCi/Message.hs
• libraries/ghci/GHCi/ObjLink.hs
• libraries/ghci/GHCi/Run.hs
• libraries/ghci/GHCi/TH.hs
• libraries/ghci/ghci.cabal.in
• libraries/haskeline
• libraries/hpc
• libraries/os-string
• libraries/parsec
• libraries/process
• libraries/semaphore-compat
• libraries/stm
• + libraries/template-haskell-lift
• + libraries/template-haskell-quasiquoter
• libraries/template-haskell/Language/Haskell/TH/Lib.hs
• libraries/template-haskell/Language/Haskell/TH/Quote.hs
• libraries/template-haskell/Language/Haskell/TH/Syntax.hs
• libraries/template-haskell/changelog.md
• libraries/template-haskell/template-haskell.cabal.in
• libraries/template-haskell/tests/all.T
• libraries/terminfo
• libraries/text
• libraries/time
• libraries/unix
• linters/lint-codes/LintCodes/Coverage.hs
• linters/lint-whitespace/lint-whitespace.cabal
• m4/find_ld.m4
• m4/find_python.m4
• m4/fp_check_pthreads.m4
• m4/fp_cmm_cpp_cmd_with_args.m4
• m4/fp_find_libdw.m4
• m4/fp_gcc_supports_no_pie.m4
• − m4/fp_set_cflags_c99.m4
• − m4/fp_settings.m4
• m4/fp_setup_windows_toolchain.m4
• − m4/fp_visibility_hidden.m4
• m4/fptools_alex.m4
• m4/fptools_happy.m4
• m4/ghc_toolchain.m4
• m4/prep_target_file.m4
• + m4/subst_tooldir.m4
• mk/get-win32-tarballs.py
• mk/hsc2hs.in
• + rts/AllocArray.c
• + rts/AllocArray.h
• rts/Apply.cmm
• rts/BeginPrivate.h
• + rts/BuiltinClosures.c
• + rts/BuiltinClosures.h
• rts/CloneStack.c
• rts/CloneStack.h
• rts/ClosureFlags.c
• + rts/ClosureTable.c
• + rts/ClosureTable.h
• rts/Compact.cmm
• rts/ContinuationOps.cmm
• rts/Disassembler.c
• rts/EndPrivate.h
• rts/Exception.cmm
• rts/ExecPage.c
• rts/Hash.c
• rts/Hash.h
• rts/Heap.c
• rts/IOManager.c
• rts/IOManager.h
• rts/IOManagerInternals.h
• rts/IPE.c
• rts/Interpreter.c
• rts/Interpreter.h
• rts/LdvProfile.c
• rts/Linker.c
• rts/LinkerInternals.h
• rts/Messages.c
• rts/PathUtils.c
• rts/PathUtils.h
• rts/Prelude.h
• rts/PrimOps.cmm
• rts/Printer.c
• rts/ProfHeap.c
• rts/Profiling.c
• rts/RetainerProfile.c
• rts/RetainerSet.c
• rts/RtsAPI.c
• − rts/RtsDllMain.c
• − rts/RtsDllMain.h
• rts/RtsFlags.c
• rts/RtsMessages.c
• rts/RtsSignals.h
• rts/RtsStartup.c
• rts/RtsSymbols.c
• + rts/RtsToHsIface.c
• rts/RtsUtils.c
• rts/Schedule.c
• rts/StgMiscClosures.cmm
• rts/StgStdThunks.cmm
• rts/Task.c
• rts/Task.h
• rts/ThreadLabels.c
• rts/ThreadPaused.c
• rts/Threads.c
• + rts/TimeoutQueue.c
• + rts/TimeoutQueue.h
• rts/Timer.c
• rts/Trace.c
• rts/Trace.h
• rts/TraverseHeap.c
• rts/Updates.h
• rts/Weak.c
• rts/configure.ac
• rts/eventlog/EventLog.c
• rts/eventlog/EventLog.h
• − rts/external-symbols.list.in
• rts/gen_event_types.py
• rts/include/Rts.h
• rts/include/RtsAPI.h
• rts/include/Stg.h
• rts/include/rts/Bytecodes.h
• rts/include/rts/Constants.h
• rts/include/rts/Flags.h
• rts/include/rts/IPE.h
• rts/include/rts/NonMoving.h
• rts/include/rts/OSThreads.h
• + rts/include/rts/RtsToHsIface.h
• rts/include/rts/StableName.h
• rts/include/rts/StablePtr.h
• rts/include/rts/Types.h
• rts/include/rts/prof/CCS.h
• rts/include/rts/storage/Block.h
• rts/include/rts/storage/ClosureTypes.h
• rts/include/rts/storage/Closures.h
• rts/include/rts/storage/GC.h
• rts/include/rts/storage/Heap.h
• rts/include/rts/storage/TSO.h
• − rts/include/stg/DLL.h
• rts/include/stg/MachRegs.h
• rts/include/stg/MiscClosures.h
• rts/include/stg/Prim.h
• rts/include/stg/SMP.h
• rts/js/mem.js
• rts/js/profiling.js
• rts/linker/Elf.c
• rts/linker/LoadArchive.c
• rts/linker/LoadNativeObjPosix.c
• rts/linker/MachO.c
• rts/linker/PEi386.c
• rts/linker/PEi386.h
• + rts/linker/ProddableBlocks.c
• + rts/linker/ProddableBlocks.h
• rts/posix/OSMem.c
• rts/posix/OSThreads.c
• + rts/posix/Poll.c
• + rts/posix/Poll.h
• rts/posix/Signals.c
• + rts/posix/Timeout.c
• + rts/posix/Timeout.h
• rts/posix/ticker/Pthread.c
• rts/posix/ticker/TimerFd.c
• libraries/ghc-internal/cbits/atomic.c → rts/prim/atomic.c
• libraries/ghc-internal/cbits/bitrev.c → rts/prim/bitrev.c
• libraries/ghc-internal/cbits/bswap.c → rts/prim/bswap.c
• libraries/ghc-internal/cbits/clz.c → rts/prim/clz.c
• libraries/ghc-internal/cbits/ctz.c → rts/prim/ctz.c
• libraries/ghc-internal/cbits/int64x2minmax.c → rts/prim/int64x2minmax.c
• libraries/ghc-internal/cbits/longlong.c → rts/prim/longlong.c
• libraries/ghc-internal/cbits/mulIntMayOflo.c → rts/prim/mulIntMayOflo.c
• libraries/ghc-internal/cbits/pdep.c → rts/prim/pdep.c
• libraries/ghc-internal/cbits/pext.c → rts/prim/pext.c
• libraries/ghc-internal/cbits/popcnt.c → rts/prim/popcnt.c
• libraries/ghc-internal/cbits/vectorQuotRem.c → rts/prim/vectorQuotRem.c
• libraries/ghc-internal/cbits/word2float.c → rts/prim/word2float.c
• rts/rts.buildinfo.in
• rts/rts.cabal
• rts/sm/BlockAlloc.c
• rts/sm/Compact.c
• rts/sm/Evac.c
• rts/sm/Evac.h
• rts/sm/GCTDecl.h
• rts/sm/GCThread.h
• rts/sm/NonMoving.c
• rts/sm/NonMoving.h
• rts/sm/NonMovingAllocate.c
• rts/sm/NonMovingMark.c
• rts/sm/Sanity.c
• rts/sm/Scav.c
• rts/sm/Storage.c
• rts/sm/Storage.h
• rts/wasm/JSFFI.c
• rts/wasm/scheduler.cmm
• rts/win32/AsyncWinIO.c
• rts/win32/OSThreads.c
• rts/win32/libHSghc-internal.def
• testsuite/.gitignore
• testsuite/config/ghc
• testsuite/driver/cpu_features.py
• testsuite/driver/runtests.py
• testsuite/driver/testglobals.py
• testsuite/driver/testlib.py
• testsuite/ghc-config/ghc-config.hs
• testsuite/mk/test.mk
• testsuite/tests/annotations/should_fail/annfail03.stderr
• testsuite/tests/annotations/should_fail/annfail09.stderr
• testsuite/tests/arrows/gadt/T17423.stderr
• testsuite/tests/arrows/should_compile/T21301.stderr
• testsuite/tests/backpack/cabal/bkpcabal08/bkpcabal08.stdout
• testsuite/tests/backpack/should_fail/T19244a.stderr
• testsuite/tests/backpack/should_fail/bkpfail11.stderr
• testsuite/tests/backpack/should_fail/bkpfail43.stderr
• testsuite/tests/bytecode/T22376/all.T
• + testsuite/tests/bytecode/T23973.hs
• + testsuite/tests/bytecode/T23973.script
• + testsuite/tests/bytecode/T23973.stdout
• testsuite/tests/bytecode/T24634/T24634a.stdout
• testsuite/tests/bytecode/T24634/T24634b.stdout
• + testsuite/tests/bytecode/T26216.hs
• + testsuite/tests/bytecode/T26216.script
• + testsuite/tests/bytecode/T26216.stdout
• + testsuite/tests/bytecode/T26216_aux.hs
• + testsuite/tests/bytecode/T26565.hs
• + testsuite/tests/bytecode/T26565.script
• + testsuite/tests/bytecode/T26565.stdout
• testsuite/tests/bytecode/all.T
• testsuite/tests/callarity/unittest/CallArity1.hs
• + testsuite/tests/cmm/should_run/T25601.hs
• + testsuite/tests/cmm/should_run/T25601.stdout
• + testsuite/tests/cmm/should_run/T25601a.cmm
• testsuite/tests/cmm/should_run/all.T
• testsuite/tests/codeGen/should_compile/Makefile
• testsuite/tests/codeGen/should_compile/T14999.stdout
• + testsuite/tests/codeGen/should_compile/T20298a.hs
• + testsuite/tests/codeGen/should_compile/T20298a.stderr
• + testsuite/tests/codeGen/should_compile/T20298b.hs
• + testsuite/tests/codeGen/should_compile/T20298b.stderr
• + testsuite/tests/codeGen/should_compile/T20298c.hs
• + testsuite/tests/codeGen/should_compile/T20298c.stderr
• testsuite/tests/codeGen/should_compile/T25166.stdout → testsuite/tests/codeGen/should_compile/T25166.stdout-ws-32
• + testsuite/tests/codeGen/should_compile/T25166.stdout-ws-64
• testsuite/tests/codeGen/should_compile/all.T
• testsuite/tests/codeGen/should_gen_asm/all.T
• + testsuite/tests/codeGen/should_gen_asm/mavx-should-enable-popcnt.asm
• + testsuite/tests/codeGen/should_gen_asm/mavx-should-enable-popcnt.hs
• + testsuite/tests/codeGen/should_gen_asm/msse-option-order.asm
• + testsuite/tests/codeGen/should_gen_asm/msse-option-order.hs
• testsuite/tests/codeGen/should_run/T13825-unit.hs
• testsuite/tests/codeGen/should_run/T23146/all.T
• + testsuite/tests/codeGen/should_run/T26061.hs
• + testsuite/tests/codeGen/should_run/T26061.stdout
• + testsuite/tests/codeGen/should_run/T26537.hs
• + testsuite/tests/codeGen/should_run/T26537.stdout
• testsuite/tests/codeGen/should_run/all.T
• testsuite/tests/concurrent/prog001/all.T
• testsuite/tests/core-to-stg/T24124.stderr
• testsuite/tests/corelint/LintEtaExpand.stderr
• testsuite/tests/corelint/T21115b.stderr
• testsuite/tests/count-deps/CountDepsAst.stdout
• testsuite/tests/count-deps/CountDepsParser.stdout
• testsuite/tests/cpranal/should_compile/T18174.stderr
• + testsuite/tests/cpranal/sigs/T25944.hs
• + testsuite/tests/cpranal/sigs/T25944.stderr
• testsuite/tests/cpranal/sigs/all.T
• + testsuite/tests/cross/should_run/T26449.hs
• + testsuite/tests/cross/should_run/all.T
• testsuite/tests/deSugar/should_compile/T2431.stderr
• testsuite/tests/deSugar/should_fail/DsStrictFail.stderr
• testsuite/tests/deSugar/should_run/DsDoExprFailMsg.stderr
• testsuite/tests/deSugar/should_run/DsMonadCompFailMsg.stderr
• testsuite/tests/deSugar/should_run/T20024.stderr
• testsuite/tests/deSugar/should_run/dsrun005.stderr
• testsuite/tests/deSugar/should_run/dsrun007.stderr
• testsuite/tests/deSugar/should_run/dsrun008.stderr
• testsuite/tests/default/default-fail05.stderr
• testsuite/tests/dependent/should_fail/T11334b.stderr
• testsuite/tests/dependent/should_fail/T11471.stderr
• testsuite/tests/dependent/should_fail/T13135_simple.stderr
• testsuite/tests/dependent/should_fail/T16326_Fail6.stderr
• testsuite/tests/deriving/should_compile/T14682.stderr
• testsuite/tests/deriving/should_compile/T20815.hs
• + testsuite/tests/deriving/should_compile/T26396.hs
• testsuite/tests/deriving/should_compile/all.T
• testsuite/tests/deriving/should_compile/drv-empty-data.stderr
• testsuite/tests/deriving/should_fail/T12768.stderr
• testsuite/tests/deriving/should_fail/T1496.stderr
• testsuite/tests/deriving/should_fail/T21302.stderr
• testsuite/tests/deriving/should_fail/T22696b.stderr
• testsuite/tests/deriving/should_fail/T3621.stderr
• testsuite/tests/deriving/should_fail/T5498.stderr
• testsuite/tests/deriving/should_fail/T7148.stderr
• testsuite/tests/deriving/should_fail/T7148a.stderr
• testsuite/tests/deriving/should_run/T9576.stderr
• testsuite/tests/diagnostic-codes/codes.stdout
• testsuite/tests/dmdanal/should_compile/T16029.stdout
• testsuite/tests/dmdanal/should_compile/T23398.hs
• testsuite/tests/dmdanal/should_compile/T23398.stderr
• testsuite/tests/dmdanal/sigs/T21119.stderr
• testsuite/tests/dmdanal/sigs/T21888.stderr
• testsuite/tests/driver/Makefile
• testsuite/tests/driver/T11429c.stderr
• testsuite/tests/driver/T20696/all.T
• testsuite/tests/driver/T21682.stderr
• + testsuite/tests/driver/T24120.hs
• + testsuite/tests/driver/T24731.hs
• + testsuite/tests/driver/T26551.hs
• + testsuite/tests/driver/T26551.stderr
• testsuite/tests/driver/T5313.hs
• testsuite/tests/driver/T8526/T8526.stdout
• testsuite/tests/driver/all.T
• + testsuite/tests/driver/bytecode-object/A.hs
• + testsuite/tests/driver/bytecode-object/BytecodeForeign.c
• + testsuite/tests/driver/bytecode-object/BytecodeForeign.hs
• + testsuite/tests/driver/bytecode-object/BytecodeMain.hs
• + testsuite/tests/driver/bytecode-object/BytecodeTest.hs
• + testsuite/tests/driver/bytecode-object/Makefile
• + testsuite/tests/driver/bytecode-object/all.T
• + testsuite/tests/driver/bytecode-object/bytecode_object12.stderr
• + testsuite/tests/driver/bytecode-object/bytecode_object13.stdout
• + testsuite/tests/driver/bytecode-object/bytecode_object14.stdout
• + testsuite/tests/driver/bytecode-object/bytecode_object15.stdout
• + testsuite/tests/driver/bytecode-object/bytecode_object16.stdout
• + testsuite/tests/driver/bytecode-object/bytecode_object17.stdout
• + testsuite/tests/driver/bytecode-object/bytecode_object18.stdout
• + testsuite/tests/driver/bytecode-object/bytecode_object19.script
• + testsuite/tests/driver/bytecode-object/bytecode_object19.stdout
• + testsuite/tests/driver/bytecode-object/bytecode_object25.stdout
• + testsuite/tests/driver/bytecode-object/bytecode_object4.stdout
• + testsuite/tests/driver/bytecode-object/bytecode_object5.stdout
• + testsuite/tests/driver/bytecode-object/bytecode_object6.stdout
• testsuite/tests/driver/fat-iface/T22405/T22405.stdout
• testsuite/tests/driver/fat-iface/T22405/T22405b.stdout
• testsuite/tests/driver/fat-iface/all.T
• testsuite/tests/driver/fat-iface/fat011.stderr
• testsuite/tests/driver/fat-iface/fat014.stdout
• testsuite/tests/driver/j-space/Makefile
• testsuite/tests/driver/j-space/all.T
• testsuite/tests/driver/j-space/genJspace
• testsuite/tests/driver/json.stderr
• testsuite/tests/driver/json_warn.stderr
• + testsuite/tests/driver/make-prim/GHC/Internal/Prim.hs
• + testsuite/tests/driver/make-prim/Makefile
• + testsuite/tests/driver/make-prim/Test.hs
• + testsuite/tests/driver/make-prim/Test2.hs
• + testsuite/tests/driver/make-prim/all.T
• testsuite/tests/driver/multipleHomeUnits/all.T
• testsuite/tests/driver/multipleHomeUnits/multiGHCi.stderr
• testsuite/tests/driver/recomp015/all.T
• testsuite/tests/ffi/should_run/T1288_c.c
• testsuite/tests/ffi/should_run/T1288_ghci_c.c
• testsuite/tests/ffi/should_run/T2276_c.c
• testsuite/tests/ffi/should_run/T2276_ghci_c.c
• testsuite/tests/ffi/should_run/all.T
• testsuite/tests/gadt/T12468.stderr
• testsuite/tests/generics/T10604/T10604_deriving.stderr
• + testsuite/tests/ghc-api-browser/README.md
• + testsuite/tests/ghc-api-browser/all.T
• + testsuite/tests/ghc-api-browser/index.html
• + testsuite/tests/ghc-api-browser/playground001.hs
• + testsuite/tests/ghc-api-browser/playground001.js
• + testsuite/tests/ghc-api-browser/playground001.sh
• + testsuite/tests/ghc-api-browser/playground001.stdout
• testsuite/tests/ghc-api/T10052/T10052.hs
• testsuite/tests/ghc-api/T10942.hs
• testsuite/tests/ghc-api/T20757.hs
• + testsuite/tests/ghc-api/T26120.hs
• + testsuite/tests/ghc-api/T26120.stdout
• + testsuite/tests/ghc-api/T26264.hs
• + testsuite/tests/ghc-api/T26264.stdout
• testsuite/tests/ghc-api/T6145.hs
• testsuite/tests/ghc-api/T8639_api.hs
• testsuite/tests/ghc-api/all.T
• testsuite/tests/ghc-api/annotations-literals/literals.hs
• testsuite/tests/ghc-api/annotations-literals/parsed.hs
• testsuite/tests/ghc-api/apirecomp001/myghc.hs
• testsuite/tests/ghc-api/fixed-nodes/T1.hs
• testsuite/tests/ghc-api/settings-escape/T24265.hs
• testsuite/tests/ghc-api/settings-escape/T24265.stderr
• + testsuite/tests/ghc-api/settings-escape/ghc-install-folder/lib with spaces/targets/.gitkeep
• testsuite/tests/ghc-e/should_fail/T18441fail5.stderr
• testsuite/tests/ghc-e/should_fail/T24172.stderr
• testsuite/tests/ghc-e/should_fail/T9930fail.stderr
• testsuite/tests/ghc-e/should_fail/all.T
• + testsuite/tests/ghci-wasm/Makefile
• + testsuite/tests/ghci-wasm/T26430.hs
• + testsuite/tests/ghci-wasm/T26430A.c
• + testsuite/tests/ghci-wasm/T26430B.c
• + testsuite/tests/ghci-wasm/all.T
• + testsuite/tests/ghci.debugger/scripts/T26042b.hs
• + testsuite/tests/ghci.debugger/scripts/T26042b.script
• + testsuite/tests/ghci.debugger/scripts/T26042b.stdout
• + testsuite/tests/ghci.debugger/scripts/T26042c.hs
• + testsuite/tests/ghci.debugger/scripts/T26042c.script
• + testsuite/tests/ghci.debugger/scripts/T26042c.stdout
• + testsuite/tests/ghci.debugger/scripts/T26042d.hs
• + testsuite/tests/ghci.debugger/scripts/T26042d.script
• + testsuite/tests/ghci.debugger/scripts/T26042d.stdout
• + testsuite/tests/ghci.debugger/scripts/T26042d2.hs
• + testsuite/tests/ghci.debugger/scripts/T26042d2.script
• + testsuite/tests/ghci.debugger/scripts/T26042d2.stdout
• + testsuite/tests/ghci.debugger/scripts/T26042e.hs
• + testsuite/tests/ghci.debugger/scripts/T26042e.script
• + testsuite/tests/ghci.debugger/scripts/T26042e.stdout
• + testsuite/tests/ghci.debugger/scripts/T26042f.hs
• + testsuite/tests/ghci.debugger/scripts/T26042f.script
• + testsuite/tests/ghci.debugger/scripts/T26042f1.stderr
• + testsuite/tests/ghci.debugger/scripts/T26042f1.stdout
• + testsuite/tests/ghci.debugger/scripts/T26042f2.stdout
• + testsuite/tests/ghci.debugger/scripts/T26042g.hs
• + testsuite/tests/ghci.debugger/scripts/T26042g.script
• + testsuite/tests/ghci.debugger/scripts/T26042g.stdout
• testsuite/tests/ghci.debugger/scripts/all.T
• testsuite/tests/ghci.debugger/scripts/break011.stdout
• testsuite/tests/ghci.debugger/scripts/break022/all.T
• testsuite/tests/ghci.debugger/scripts/break022/break022.script
• testsuite/tests/ghci.debugger/scripts/break023/all.T
• testsuite/tests/ghci.debugger/scripts/break023/break023.script
• testsuite/tests/ghci.debugger/scripts/break024.stdout
• + testsuite/tests/ghci.debugger/scripts/break031/Makefile
• + testsuite/tests/ghci.debugger/scripts/break031/a/A.hs
• + testsuite/tests/ghci.debugger/scripts/break031/all.T
• + testsuite/tests/ghci.debugger/scripts/break031/b/B.hs
• + testsuite/tests/ghci.debugger/scripts/break031/break031a.script
• + testsuite/tests/ghci.debugger/scripts/break031/break031a.stdout
• + testsuite/tests/ghci.debugger/scripts/break031/break031b.script
• + testsuite/tests/ghci.debugger/scripts/break031/break031b.stderr
• + testsuite/tests/ghci.debugger/scripts/break031/break031b.stdout
• + testsuite/tests/ghci.debugger/scripts/break031/unitA
• + testsuite/tests/ghci.debugger/scripts/break031/unitB
• testsuite/tests/ghci.debugger/scripts/print012.stdout
• + testsuite/tests/ghci/all.T
• + testsuite/tests/ghci/ghci-mem-primops.hs
• + testsuite/tests/ghci/ghci-mem-primops.script
• + testsuite/tests/ghci/ghci-mem-primops.stdout
• testsuite/tests/ghci/linking/dyn/T3372.hs
• + testsuite/tests/ghci/prog-mhu001/Makefile
• + testsuite/tests/ghci/prog-mhu001/all.T
• + testsuite/tests/ghci/prog-mhu001/e/E.hs
• + testsuite/tests/ghci/prog-mhu001/prog-mhu001a.script
• + testsuite/tests/ghci/prog-mhu001/prog-mhu001a.stdout
• + testsuite/tests/ghci/prog-mhu001/prog-mhu001b.script
• + testsuite/tests/ghci/prog-mhu001/prog-mhu001b.stdout
• + testsuite/tests/ghci/prog-mhu001/prog-mhu001c.script
• + testsuite/tests/ghci/prog-mhu001/prog-mhu001c.stdout
• + testsuite/tests/ghci/prog-mhu001/prog-mhu001d.script
• + testsuite/tests/ghci/prog-mhu001/prog-mhu001d.stdout
• + testsuite/tests/ghci/prog-mhu001/prog-mhu001e.script
• + testsuite/tests/ghci/prog-mhu001/prog-mhu001e.stdout
• + testsuite/tests/ghci/prog-mhu001/prog-mhu001f.script
• + testsuite/tests/ghci/prog-mhu001/prog-mhu001f.stdout
• + testsuite/tests/ghci/prog-mhu001/unitE
• + testsuite/tests/ghci/prog-mhu001/unitE-main-is
• + testsuite/tests/ghci/prog-mhu002/Makefile
• + testsuite/tests/ghci/prog-mhu002/a/A.hs
• + testsuite/tests/ghci/prog-mhu002/all.T
• + testsuite/tests/ghci/prog-mhu002/b/B.hs
• + testsuite/tests/ghci/prog-mhu002/c/C.hs
• + testsuite/tests/ghci/prog-mhu002/d/Main.hs
• + testsuite/tests/ghci/prog-mhu002/prog-mhu002a.script
• + testsuite/tests/ghci/prog-mhu002/prog-mhu002a.stderr
• + testsuite/tests/ghci/prog-mhu002/prog-mhu002a.stdout
• + testsuite/tests/ghci/prog-mhu002/prog-mhu002b.script
• + testsuite/tests/ghci/prog-mhu002/prog-mhu002b.stderr
• + testsuite/tests/ghci/prog-mhu002/prog-mhu002b.stdout
• + testsuite/tests/ghci/prog-mhu002/prog-mhu002c.script
• + testsuite/tests/ghci/prog-mhu002/prog-mhu002c.stdout
• + testsuite/tests/ghci/prog-mhu002/prog-mhu002d.script
• + testsuite/tests/ghci/prog-mhu002/prog-mhu002d.stdout
• + testsuite/tests/ghci/prog-mhu002/prog-mhu002e.script
• + testsuite/tests/ghci/prog-mhu002/prog-mhu002e.stdout
• + testsuite/tests/ghci/prog-mhu002/prog-mhu002f.script
• + testsuite/tests/ghci/prog-mhu002/prog-mhu002f.stdout
• + testsuite/tests/ghci/prog-mhu002/unitA
• + testsuite/tests/ghci/prog-mhu002/unitB
• + testsuite/tests/ghci/prog-mhu002/unitC
• + testsuite/tests/ghci/prog-mhu002/unitD
• + testsuite/tests/ghci/prog-mhu003/Makefile
• + testsuite/tests/ghci/prog-mhu003/a/A.hs
• + testsuite/tests/ghci/prog-mhu003/all.T
• + testsuite/tests/ghci/prog-mhu003/b/Foo.hs
• + testsuite/tests/ghci/prog-mhu003/c/C.hs
• + testsuite/tests/ghci/prog-mhu003/d/Foo.hs
• + testsuite/tests/ghci/prog-mhu003/prog-mhu003.script
• + testsuite/tests/ghci/prog-mhu003/prog-mhu003.stderr
• + testsuite/tests/ghci/prog-mhu003/prog-mhu003.stdout
• + testsuite/tests/ghci/prog-mhu003/unitA
• + testsuite/tests/ghci/prog-mhu003/unitB
• + testsuite/tests/ghci/prog-mhu003/unitC
• + testsuite/tests/ghci/prog-mhu003/unitD
• + testsuite/tests/ghci/prog-mhu004/Makefile
• + testsuite/tests/ghci/prog-mhu004/a/Foo.hs
• + testsuite/tests/ghci/prog-mhu004/all.T
• + testsuite/tests/ghci/prog-mhu004/b/Foo.hs
• + testsuite/tests/ghci/prog-mhu004/prog-mhu004a.script
• + testsuite/tests/ghci/prog-mhu004/prog-mhu004a.stderr
• + testsuite/tests/ghci/prog-mhu004/prog-mhu004a.stdout
• + testsuite/tests/ghci/prog-mhu004/prog-mhu004b.script
• + testsuite/tests/ghci/prog-mhu004/prog-mhu004b.stdout
• + testsuite/tests/ghci/prog-mhu004/unitA
• + testsuite/tests/ghci/prog-mhu004/unitB
• + testsuite/tests/ghci/prog-mhu005/Makefile
• + testsuite/tests/ghci/prog-mhu005/a/A.hs
• + testsuite/tests/ghci/prog-mhu005/all.T
• + testsuite/tests/ghci/prog-mhu005/b/B.hs
• + testsuite/tests/ghci/prog-mhu005/prog-mhu005a.script
• + testsuite/tests/ghci/prog-mhu005/prog-mhu005a.stderr
• + testsuite/tests/ghci/prog-mhu005/prog-mhu005a.stdout
• + testsuite/tests/ghci/prog-mhu005/unitA
• + testsuite/tests/ghci/prog-mhu005/unitB
• testsuite/tests/ghci/prog001/prog001.T
• testsuite/tests/ghci/prog001/prog001.script
• testsuite/tests/ghci/prog002/prog002.T
• testsuite/tests/ghci/prog002/prog002.script
• testsuite/tests/ghci/prog003/prog003.T
• testsuite/tests/ghci/prog003/prog003.script
• testsuite/tests/ghci/prog005/prog005.T
• testsuite/tests/ghci/prog005/prog005.script
• testsuite/tests/ghci/prog010/all.T
• testsuite/tests/ghci/prog010/ghci.prog010.script
• testsuite/tests/ghci/prog012/all.T
• testsuite/tests/ghci/prog012/prog012.script
• testsuite/tests/ghci/prog018/prog018.stdout
• + testsuite/tests/ghci/prog020/A.hs
• + testsuite/tests/ghci/prog020/B.hs
• + testsuite/tests/ghci/prog020/Makefile
• + testsuite/tests/ghci/prog020/all.T
• + testsuite/tests/ghci/prog020/ghci.prog020.script
• + testsuite/tests/ghci/prog020/ghci.prog020.stderr
• + testsuite/tests/ghci/prog020/ghci.prog020.stdout
• + testsuite/tests/ghci/prog021/A.hs
• + testsuite/tests/ghci/prog021/B.hs
• + testsuite/tests/ghci/prog021/Makefile
• + testsuite/tests/ghci/prog021/all.T
• + testsuite/tests/ghci/prog021/prog021a.script
• + testsuite/tests/ghci/prog021/prog021a.stderr
• + testsuite/tests/ghci/prog021/prog021a.stdout
• + testsuite/tests/ghci/prog021/prog021b.script
• + testsuite/tests/ghci/prog021/prog021b.stderr
• + testsuite/tests/ghci/prog021/prog021b.stdout
• + testsuite/tests/ghci/prog022/A.hs
• + testsuite/tests/ghci/prog022/B.hs
• + testsuite/tests/ghci/prog022/Makefile
• + testsuite/tests/ghci/prog022/all.T
• + testsuite/tests/ghci/prog022/ghci.prog022a.script
• + testsuite/tests/ghci/prog022/ghci.prog022a.stderr
• + testsuite/tests/ghci/prog022/ghci.prog022a.stdout
• + testsuite/tests/ghci/prog022/ghci.prog022b.script
• + testsuite/tests/ghci/prog022/ghci.prog022b.stderr
• + testsuite/tests/ghci/prog022/ghci.prog022b.stdout
• testsuite/tests/ghci/recompTHghci/all.T
• testsuite/tests/ghci/recompTHghci/recompTHghci.script
• testsuite/tests/ghci/scripts/Defer02.stderr
• testsuite/tests/ghci/scripts/T10321.stdout
• testsuite/tests/ghci/scripts/T12550.stdout
• testsuite/tests/ghci/scripts/T13869.stdout
• testsuite/tests/ghci/scripts/T13997.stdout
• testsuite/tests/ghci/scripts/T15325.stderr
• testsuite/tests/ghci/scripts/T17669.stdout
• testsuite/tests/ghci/scripts/T18330.script
• testsuite/tests/ghci/scripts/T18330.stdout
• testsuite/tests/ghci/scripts/T1914.script
• testsuite/tests/ghci/scripts/T1914.stdout
• testsuite/tests/ghci/scripts/T20217.stdout
• testsuite/tests/ghci/scripts/T20587.script
• testsuite/tests/ghci/scripts/T20587.stdout
• testsuite/tests/ghci/scripts/T21110.stderr
• testsuite/tests/ghci/scripts/T24459.stdout
• testsuite/tests/ghci/scripts/T6105.stdout
• testsuite/tests/ghci/scripts/T6106.script
• testsuite/tests/ghci/scripts/T7388.hs
• testsuite/tests/ghci/scripts/T7388.script
• testsuite/tests/ghci/scripts/T7730.stdout
• testsuite/tests/ghci/scripts/T8042.stdout
• testsuite/tests/ghci/scripts/T8042recomp.stdout
• testsuite/tests/ghci/scripts/T8353.script
• testsuite/tests/ghci/scripts/T8353.stderr
• testsuite/tests/ghci/scripts/T8959b.stderr
• testsuite/tests/ghci/scripts/all.T
• testsuite/tests/ghci/scripts/ghci021.stderr
• testsuite/tests/ghci/scripts/ghci024.stdout
• testsuite/tests/ghci/scripts/ghci024.stdout-mingw32
• testsuite/tests/ghci/scripts/ghci038.script
• testsuite/tests/ghci/scripts/ghci038.stdout
• testsuite/tests/ghci/scripts/ghci051.stderr
• testsuite/tests/ghci/scripts/ghci058.script
• testsuite/tests/ghci/scripts/ghci063.script
• testsuite/tests/ghci/scripts/ghci065.stdout
• + testsuite/tests/ghci/scripts/print-unicode-syntax.script
• + testsuite/tests/ghci/scripts/print-unicode-syntax.stderr
• + testsuite/tests/ghci/scripts/print-unicode-syntax.stdout
• − testsuite/tests/ghci/shell.hs
• testsuite/tests/ghci/should_run/PackedDataCon/packeddatacon.T
• testsuite/tests/ghci/should_run/T11825.stdout
• testsuite/tests/ghci/should_run/TopEnvIface.stdout
• testsuite/tests/ghci/should_run/UnboxedTuples/unboxedtuples.T
• testsuite/tests/ghci/should_run/UnliftedDataTypeInterp/unlifteddatatypeinterp.T
• testsuite/tests/haddock/haddock_testsuite/Makefile
• + testsuite/tests/haddock/haddock_testsuite/T26114.hs
• + testsuite/tests/haddock/haddock_testsuite/T26114.stdout
• testsuite/tests/haddock/haddock_testsuite/all.T
• testsuite/tests/haddock/should_compile_flag_haddock/T17544.stderr
• testsuite/tests/haddock/should_compile_flag_haddock/T17544_kw.hs
• testsuite/tests/haddock/should_compile_flag_haddock/T17544_kw.stderr
• + testsuite/tests/hiefile/should_run/HieGadtConSigs.hs
• + testsuite/tests/hiefile/should_run/HieGadtConSigs.stdout
• testsuite/tests/hiefile/should_run/HieQueries.stdout
• testsuite/tests/hiefile/should_run/TestUtils.hs
• testsuite/tests/hiefile/should_run/all.T
• testsuite/tests/hpc/fork/hpc_fork.stdout
• testsuite/tests/hpc/function/tough.stdout
• testsuite/tests/hpc/function2/tough2.stdout
• + testsuite/tests/hpc/recsel/Makefile
• + testsuite/tests/hpc/recsel/recsel.hs
• + testsuite/tests/hpc/recsel/recsel.stdout
• + testsuite/tests/hpc/recsel/test.T
• testsuite/tests/hpc/simple/hpc001.stdout
• testsuite/tests/impredicative/T17332.stderr
• testsuite/tests/indexed-types/should_compile/PushedInAsGivens.stderr
• testsuite/tests/indexed-types/should_compile/T12538.stderr
• testsuite/tests/indexed-types/should_compile/T2238.hs
• testsuite/tests/indexed-types/should_fail/T14369.stderr
• testsuite/tests/indexed-types/should_fail/T14887.stderr
• testsuite/tests/indexed-types/should_fail/T1897b.stderr
• testsuite/tests/indexed-types/should_fail/T21092.hs
• − testsuite/tests/indexed-types/should_fail/T21092.stderr
• + testsuite/tests/indexed-types/should_fail/T26176.hs
• + testsuite/tests/indexed-types/should_fail/T26176.stderr
• testsuite/tests/indexed-types/should_fail/T2693.stderr
• testsuite/tests/indexed-types/should_fail/T4093b.stderr
• testsuite/tests/indexed-types/should_fail/T5439.stderr
• testsuite/tests/indexed-types/should_fail/T8227.stderr
• testsuite/tests/indexed-types/should_fail/T8518.stderr
• testsuite/tests/indexed-types/should_fail/T9662.stderr
• testsuite/tests/indexed-types/should_fail/all.T
• testsuite/tests/interface-stability/base-exports.stdout
• testsuite/tests/interface-stability/base-exports.stdout-javascript-unknown-ghcjs
• testsuite/tests/interface-stability/base-exports.stdout-mingw32
• testsuite/tests/interface-stability/base-exports.stdout-ws-32
• testsuite/tests/interface-stability/ghc-experimental-exports.stdout
• testsuite/tests/interface-stability/ghc-experimental-exports.stdout-mingw32
• testsuite/tests/interface-stability/ghc-prim-exports.stdout
• testsuite/tests/interface-stability/ghc-prim-exports.stdout-mingw32
• testsuite/tests/interface-stability/template-haskell-exports.stdout
• + testsuite/tests/lib/integer/T26017.hs
• + testsuite/tests/lib/integer/T26017.stdout
• testsuite/tests/lib/integer/all.T
• testsuite/tests/lib/integer/integerRecipMod.hs
• testsuite/tests/lib/integer/integerRecipMod.stdout
• + testsuite/tests/linear/should_compile/LinearEtaExpansions.hs
• + testsuite/tests/linear/should_compile/T26332.hs
• testsuite/tests/linear/should_compile/all.T
• testsuite/tests/linear/should_fail/Linear17.stderr
• testsuite/tests/linear/should_fail/LinearLet7.stderr
• testsuite/tests/linear/should_fail/LinearTHFail.stderr
• testsuite/tests/linear/should_fail/T19361.stderr
• testsuite/tests/linear/should_fail/TypeClass.hs
• testsuite/tests/linear/should_fail/TypeClass.stderr
• testsuite/tests/linear/should_run/LinearGhci.stdout
• + testsuite/tests/linear/should_run/T26311.hs
• + testsuite/tests/linear/should_run/T26311.stdout
• testsuite/tests/linear/should_run/all.T
• testsuite/tests/linters/all.T
• testsuite/tests/linters/notes.stdout
• + testsuite/tests/llvm/should_run/T20645.hs
• + testsuite/tests/llvm/should_run/T20645.stdout
• + testsuite/tests/llvm/should_run/T26065.hs
• + testsuite/tests/llvm/should_run/T26065.stdout
• testsuite/tests/llvm/should_run/all.T
• − testsuite/tests/module/T21752.stderr
• testsuite/tests/module/T21826.stderr
• testsuite/tests/module/mod150.stderr
• testsuite/tests/module/mod151.stderr
• testsuite/tests/module/mod152.stderr
• testsuite/tests/module/mod153.stderr
• testsuite/tests/module/mod4.stderr
• testsuite/tests/numeric/should_compile/T15547.stderr
• testsuite/tests/numeric/should_compile/T16402.stderr-ws-64
• testsuite/tests/numeric/should_compile/T23907.stderr
• + testsuite/tests/numeric/should_compile/T26229.hs
• testsuite/tests/numeric/should_compile/all.T
• + testsuite/tests/numeric/should_run/T18619.hs
• + testsuite/tests/numeric/should_run/T18619.stderr
• + testsuite/tests/numeric/should_run/T26230.hs
• + testsuite/tests/numeric/should_run/T26230.stdout
• testsuite/tests/numeric/should_run/T9810.stdout
• testsuite/tests/numeric/should_run/all.T
• testsuite/tests/numeric/should_run/foundation.hs
• testsuite/tests/numeric/should_run/foundation.stdout
• testsuite/tests/overloadedrecflds/should_compile/BootFldReexport.stderr
• testsuite/tests/overloadedrecflds/should_fail/T16745.stderr
• testsuite/tests/overloadedrecflds/should_fail/T18999_NoDisambiguateRecordFields.stderr
• + testsuite/tests/overloadedrecflds/should_fail/T26391.hs
• + testsuite/tests/overloadedrecflds/should_fail/T26391.stderr
• + testsuite/tests/overloadedrecflds/should_fail/T26480.hs
• + testsuite/tests/overloadedrecflds/should_fail/T26480.stderr
• + testsuite/tests/overloadedrecflds/should_fail/T26480_aux1.hs
• + testsuite/tests/overloadedrecflds/should_fail/T26480_aux2.hs
• + testsuite/tests/overloadedrecflds/should_fail/T26480b.hs
• + testsuite/tests/overloadedrecflds/should_fail/T26480b.stderr
• testsuite/tests/overloadedrecflds/should_fail/all.T
• testsuite/tests/overloadedrecflds/should_fail/hasfieldfail01.stderr
• testsuite/tests/overloadedrecflds/should_fail/hasfieldfail02.stderr
• + testsuite/tests/overloadedrecflds/should_run/T26295.hs
• + testsuite/tests/overloadedrecflds/should_run/T26295.stdout
• testsuite/tests/overloadedrecflds/should_run/all.T
• testsuite/tests/parser/should_compile/DumpParsedAst.stderr
• testsuite/tests/parser/should_compile/DumpRenamedAst.stderr
• testsuite/tests/parser/should_compile/DumpTypecheckedAst.stderr
• testsuite/tests/parser/should_compile/T14189.stderr
• testsuite/tests/parser/should_compile/T15323.stderr
• testsuite/tests/parser/should_compile/T19082.stderr
• + testsuite/tests/parser/should_compile/T25900.hs
• + testsuite/tests/parser/should_compile/T25900.stderr
• + testsuite/tests/parser/should_compile/T25900_noext.hs
• + testsuite/tests/parser/should_compile/T25900_noext.stderr
• testsuite/tests/parser/should_compile/all.T
• testsuite/tests/parser/should_fail/RecordDotSyntaxFail10.stderr
• testsuite/tests/parser/should_fail/RecordDotSyntaxFail11.stderr
• testsuite/tests/parser/should_fail/RecordDotSyntaxFail13.stderr
• testsuite/tests/parser/should_fail/RecordDotSyntaxFail8.hs
• testsuite/tests/parser/should_fail/RecordDotSyntaxFail8.stderr
• + testsuite/tests/parser/should_fail/T12488c.hs
• + testsuite/tests/parser/should_fail/T12488c.stderr
• + testsuite/tests/parser/should_fail/T12488d.hs
• + testsuite/tests/parser/should_fail/T12488d.stderr
• testsuite/tests/parser/should_fail/T16270h.stderr
• testsuite/tests/parser/should_fail/T20654a.stderr
• + testsuite/tests/parser/should_fail/T26418.hs
• + testsuite/tests/parser/should_fail/T26418.stderr
• testsuite/tests/parser/should_fail/all.T
• + testsuite/tests/parser/should_run/T26415.hs
• + testsuite/tests/parser/should_run/T26415.stdout
• testsuite/tests/parser/should_run/all.T
• testsuite/tests/partial-sigs/should_compile/T10403.stderr
• testsuite/tests/partial-sigs/should_compile/T21719.stderr
• + testsuite/tests/partial-sigs/should_compile/T26256.hs
• + testsuite/tests/partial-sigs/should_compile/T26256.stderr
• testsuite/tests/partial-sigs/should_compile/all.T
• testsuite/tests/partial-sigs/should_fail/T10615.stderr
• testsuite/tests/partial-sigs/should_fail/T10999.stderr
• testsuite/tests/partial-sigs/should_fail/T14040a.stderr
• testsuite/tests/partial-sigs/should_fail/T14584.stderr
• testsuite/tests/partial-sigs/should_fail/T14584a.stderr
• testsuite/tests/patsyn/should_compile/ImpExp_Exp.hs
• testsuite/tests/patsyn/should_compile/T11959.hs
• testsuite/tests/patsyn/should_compile/T11959.stderr
• testsuite/tests/patsyn/should_compile/T11959Lib.hs
• testsuite/tests/patsyn/should_compile/T13350/boolean/Boolean.hs
• testsuite/tests/patsyn/should_compile/T22521.hs
• + testsuite/tests/patsyn/should_compile/T26331.hs
• + testsuite/tests/patsyn/should_compile/T26331a.hs
• + testsuite/tests/patsyn/should_compile/T26465b.hs
• + testsuite/tests/patsyn/should_compile/T26465c.hs
• + testsuite/tests/patsyn/should_compile/T26465d.hs
• + testsuite/tests/patsyn/should_compile/T26465d.stderr
• testsuite/tests/patsyn/should_compile/T9857.hs
• testsuite/tests/patsyn/should_compile/all.T
• testsuite/tests/patsyn/should_compile/export.hs
• + testsuite/tests/patsyn/should_fail/T26465.hs
• + testsuite/tests/patsyn/should_fail/T26465.stderr
• testsuite/tests/patsyn/should_fail/all.T
• testsuite/tests/patsyn/should_run/ghci.stderr
• testsuite/tests/perf/compiler/Makefile
• testsuite/tests/perf/compiler/MultiLayerModulesDefsGhci.script
• + testsuite/tests/perf/compiler/MultiLayerModulesDefsGhciWithBytecodeFiles.script
• + testsuite/tests/perf/compiler/T26425.hs
• testsuite/tests/perf/compiler/T4007.stdout
• testsuite/tests/perf/compiler/all.T
• testsuite/tests/perf/compiler/hard_hole_fits.stderr
• testsuite/tests/perf/should_run/ByteCodeAsm.hs
• + testsuite/tests/perf/should_run/SpecTyFamRun.hs
• + testsuite/tests/perf/should_run/SpecTyFamRun.stdout
• + testsuite/tests/perf/should_run/SpecTyFam_Import.hs
• testsuite/tests/perf/should_run/T3586.hs
• testsuite/tests/perf/should_run/UniqLoop.hs
• testsuite/tests/perf/should_run/all.T
• testsuite/tests/plugins/Makefile
• + testsuite/tests/plugins/T21730-plugin/Makefile
• + testsuite/tests/plugins/T21730-plugin/Setup.hs
• + testsuite/tests/plugins/T21730-plugin/T21730-plugin.cabal
• + testsuite/tests/plugins/T21730-plugin/T21730_Plugin.hs
• + testsuite/tests/plugins/T21730.hs
• testsuite/tests/plugins/all.T
• testsuite/tests/plugins/annotation-plugin/SayAnnNames.hs
• testsuite/tests/plugins/late-plugin/LatePlugin.hs
• testsuite/tests/plugins/plugins10.stdout
• testsuite/tests/plugins/simple-plugin/Simple/ReplacePlugin.hs
• testsuite/tests/pmcheck/complete_sigs/T25115a.hs
• testsuite/tests/pmcheck/should_compile/T11822.hs
• + testsuite/tests/pmcheck/should_compile/T26400.hs
• + testsuite/tests/pmcheck/should_compile/T26400.stderr
• + testsuite/tests/pmcheck/should_compile/T26400b.hs
• testsuite/tests/pmcheck/should_compile/all.T
• testsuite/tests/pmcheck/should_compile/pmcOrPats.stderr
• testsuite/tests/polykinds/T13393.stderr
• testsuite/tests/polykinds/T14172.stderr
• testsuite/tests/polykinds/T14270.hs
• testsuite/tests/polykinds/T14846.stderr
• testsuite/tests/polykinds/T6068.stdout
• testsuite/tests/primops/should_run/UnliftedIOPort.hs
• testsuite/tests/primops/should_run/all.T
• testsuite/tests/printer/Makefile
• testsuite/tests/printer/T18791.stderr
• + testsuite/tests/printer/TestLevelImports.hs
• + testsuite/tests/printer/TestNamedDefaults.hs
• testsuite/tests/printer/all.T
• − testsuite/tests/process/process010.stdout-i386-unknown-solaris2
• + testsuite/tests/profiling/should_compile/T26056.hs
• testsuite/tests/profiling/should_compile/all.T
• testsuite/tests/profiling/should_run/caller-cc/all.T
• testsuite/tests/profiling/should_run/callstack001.stdout
• testsuite/tests/quantified-constraints/T15290a.stderr
• testsuite/tests/quantified-constraints/T15359.hs
• testsuite/tests/quantified-constraints/T19690.stderr
• testsuite/tests/quantified-constraints/T19921.stderr
• testsuite/tests/quantified-constraints/T21006.stderr
• testsuite/tests/quasiquotation/T3953.stderr
• testsuite/tests/quasiquotation/T4491/test.T
• testsuite/tests/quasiquotation/T7918.hs
• testsuite/tests/quasiquotation/qq001/qq001.stderr
• testsuite/tests/quasiquotation/qq002/qq002.stderr
• testsuite/tests/quasiquotation/qq003/qq003.stderr
• testsuite/tests/quasiquotation/qq004/qq004.stderr
• + testsuite/tests/quotes/LiftErrMsg.hs
• + testsuite/tests/quotes/LiftErrMsg.stderr
• + testsuite/tests/quotes/LiftErrMsgDefer.hs
• + testsuite/tests/quotes/LiftErrMsgDefer.stderr
• + testsuite/tests/quotes/LiftErrMsgTyped.hs
• + testsuite/tests/quotes/LiftErrMsgTyped.stderr
• + testsuite/tests/quotes/QQError.hs
• + testsuite/tests/quotes/QQError.stderr
• testsuite/tests/quotes/T10384.stderr
• testsuite/tests/quotes/TH_localname.stderr
• testsuite/tests/quotes/all.T
• testsuite/tests/rebindable/DoRestrictedM.hs
• testsuite/tests/regalloc/regalloc_unit_tests.hs
• + testsuite/tests/rename/should_compile/T12488b.hs
• + testsuite/tests/rename/should_compile/T12488f.hs
• testsuite/tests/rename/should_compile/T12548.hs
• testsuite/tests/rename/should_compile/T22513d.stderr
• testsuite/tests/rename/should_compile/T22513e.stderr
• testsuite/tests/rename/should_compile/T22513f.stderr
• testsuite/tests/rename/should_compile/T22513g.stderr
• testsuite/tests/rename/should_compile/T22513h.stderr
• testsuite/tests/rename/should_compile/T22513i.stderr
• testsuite/tests/rename/should_compile/T22581d.stdout
• + testsuite/tests/rename/should_compile/T25899a.hs
• + testsuite/tests/rename/should_compile/T25899b.hs
• + testsuite/tests/rename/should_compile/T25899c.hs
• + testsuite/tests/rename/should_compile/T25899c_helper.hs
• + testsuite/tests/rename/should_compile/T25899d.script
• + testsuite/tests/rename/should_compile/T25899d.stdout
• testsuite/tests/rename/should_compile/all.T
• testsuite/tests/rename/should_compile/rn039.ghc.stderr
• + testsuite/tests/rename/should_fail/T12488a.hs
• + testsuite/tests/rename/should_fail/T12488a.stderr
• + testsuite/tests/rename/should_fail/T12488a_foo.hs
• + testsuite/tests/rename/should_fail/T12488a_foo.stderr
• + testsuite/tests/rename/should_fail/T12488e.hs
• + testsuite/tests/rename/should_fail/T12488e.stderr
• + testsuite/tests/rename/should_fail/T12488g.hs
• + testsuite/tests/rename/should_fail/T12488g.stderr
• testsuite/tests/rename/should_fail/T15487.stderr
• testsuite/tests/rename/should_fail/T18740a.stderr
• testsuite/tests/rename/should_fail/T19843h.stderr
• testsuite/tests/rename/should_fail/T22581a.stderr
• testsuite/tests/rename/should_fail/T22581b.stderr
• testsuite/tests/rename/should_fail/T25056.stderr
• testsuite/tests/rename/should_fail/T25056a.hs
• + testsuite/tests/rename/should_fail/T25899e1.hs
• + testsuite/tests/rename/should_fail/T25899e1.stderr
• + testsuite/tests/rename/should_fail/T25899e2.hs
• + testsuite/tests/rename/should_fail/T25899e2.stderr
• + testsuite/tests/rename/should_fail/T25899e3.hs
• + testsuite/tests/rename/should_fail/T25899e3.stderr
• + testsuite/tests/rename/should_fail/T25899e_helper.hs
• + testsuite/tests/rename/should_fail/T25899f.hs
• + testsuite/tests/rename/should_fail/T25899f.stderr
• + testsuite/tests/rename/should_fail/T25899f_helper.hs
• testsuite/tests/rename/should_fail/all.T
• testsuite/tests/rename/should_fail/rnfail044.stderr
• testsuite/tests/rename/should_fail/rnfail055.stderr
• + testsuite/tests/rep-poly/NoEtaRequired.hs
• testsuite/tests/rep-poly/RepPolyArgument.stderr
• testsuite/tests/rep-poly/RepPolyBackpack1.stderr
• testsuite/tests/rep-poly/RepPolyBinder.stderr
• testsuite/tests/rep-poly/RepPolyCase1.stderr
• − testsuite/tests/rep-poly/RepPolyCase2.stderr
• testsuite/tests/rep-poly/RepPolyDoBind.stderr
• testsuite/tests/rep-poly/RepPolyDoBody1.stderr
• testsuite/tests/rep-poly/RepPolyDoBody2.stderr
• testsuite/tests/rep-poly/RepPolyLeftSection2.stderr
• testsuite/tests/rep-poly/RepPolyMagic.stderr
• testsuite/tests/rep-poly/RepPolyMcBind.stderr
• testsuite/tests/rep-poly/RepPolyMcBody.stderr
• testsuite/tests/rep-poly/RepPolyMcGuard.stderr
• testsuite/tests/rep-poly/RepPolyNPlusK.stderr
• testsuite/tests/rep-poly/RepPolyPatBind.stderr
• testsuite/tests/rep-poly/RepPolyRecordUpdate.stderr
• testsuite/tests/rep-poly/RepPolyRightSection.stderr
• testsuite/tests/rep-poly/RepPolyRule1.stderr
• testsuite/tests/rep-poly/RepPolyRule3.stderr
• testsuite/tests/rep-poly/RepPolyTuple.stderr
• testsuite/tests/rep-poly/RepPolyTuple4.stderr
• testsuite/tests/rep-poly/RepPolyTupleSection.stderr
• testsuite/tests/rep-poly/RepPolyWrappedVar.stderr
• testsuite/tests/rep-poly/T11473.stderr
• testsuite/tests/rep-poly/T12709.stderr
• testsuite/tests/rep-poly/T12973.stderr
• testsuite/tests/rep-poly/T13233.stderr
• testsuite/tests/rep-poly/T13929.stderr
• testsuite/tests/rep-poly/T14561.stderr
• testsuite/tests/rep-poly/T14561b.stderr
• − testsuite/tests/rep-poly/T17021.stderr
• testsuite/tests/rep-poly/T17817.stderr
• testsuite/tests/rep-poly/T19615.stderr
• testsuite/tests/rep-poly/T19709b.stderr
• testsuite/tests/rep-poly/T20363b.stderr
• − testsuite/tests/rep-poly/T21650_a.stderr
• − testsuite/tests/rep-poly/T21650_b.stderr
• testsuite/tests/rep-poly/T21906.stderr
• testsuite/tests/rep-poly/T23903.stderr
• + testsuite/tests/rep-poly/T26072.hs
• + testsuite/tests/rep-poly/T26072b.hs
• + testsuite/tests/rep-poly/T26107.hs
• + testsuite/tests/rep-poly/T26528.hs
• testsuite/tests/rep-poly/UnliftedNewtypesCoerceFail.stderr
• testsuite/tests/rep-poly/UnliftedNewtypesLevityBinder.stderr
• testsuite/tests/rep-poly/all.T
• testsuite/tests/roles/should_compile/Roles13.stderr
• testsuite/tests/roles/should_compile/Roles14.stderr
• testsuite/tests/roles/should_compile/Roles3.stderr
• testsuite/tests/roles/should_compile/Roles4.stderr
• testsuite/tests/roles/should_fail/RolesIArray.stderr
• + testsuite/tests/rts/ClosureTable.hs
• + testsuite/tests/rts/ClosureTable_c.c
• + testsuite/tests/rts/T22859.hs
• + testsuite/tests/rts/T22859.stderr
• + testsuite/tests/rts/TestProddableBlockSet.c
• + testsuite/tests/rts/TimeoutQueue.c
• + testsuite/tests/rts/TimeoutQueue.stdout
• testsuite/tests/rts/all.T
• testsuite/tests/rts/exec_signals_child.c
• testsuite/tests/rts/flags/all.T
• + testsuite/tests/rts/ipe/distinct-tables/Main.hs
• + testsuite/tests/rts/ipe/distinct-tables/Makefile
• + testsuite/tests/rts/ipe/distinct-tables/X.hs
• + testsuite/tests/rts/ipe/distinct-tables/all.T
• + testsuite/tests/rts/ipe/distinct-tables/distinct_tables01.stdout
• + testsuite/tests/rts/ipe/distinct-tables/distinct_tables02.stdout
• + testsuite/tests/rts/ipe/distinct-tables/distinct_tables03.stdout
• + testsuite/tests/rts/ipe/distinct-tables/distinct_tables04.stdout
• + testsuite/tests/rts/ipe/distinct-tables/distinct_tables05.stdout
• + testsuite/tests/rts/ipe/distinct-tables/distinct_tables06.stdout
• + testsuite/tests/rts/ipe/distinct-tables/distinct_tables07.stdout
• + testsuite/tests/rts/ipe/distinct-tables/distinct_tables08.stdout
• + testsuite/tests/rts/ipe/distinct-tables/distinct_tables09.stdout
• + testsuite/tests/rts/ipe/distinct-tables/distinct_tables10.stdout
• + testsuite/tests/rts/ipe/distinct-tables/distinct_tables11.stdout
• + testsuite/tests/rts/ipe/distinct-tables/distinct_tables12.stdout
• + testsuite/tests/rts/ipe/distinct-tables/distinct_tables13.stdout
• testsuite/tests/rts/ipe/ipeMap.c
• testsuite/tests/rts/ipe/ipe_lib.c
• − testsuite/tests/rts/linker/T11223/T11223_link_order_a_b_2_fail.stderr-ws-32-mingw32
• testsuite/tests/rts/linker/T11223/T11223_link_order_a_b_2_fail.stderr-ws-64-mingw32
• − testsuite/tests/rts/linker/T11223/T11223_simple_duplicate_lib.stderr-ws-32-mingw32
• testsuite/tests/rts/linker/T11223/all.T
• testsuite/tests/rts/linker/T2615.hs
• − testsuite/tests/rts/outofmem.stderr-i386-apple-darwin
• − testsuite/tests/rts/outofmem.stderr-i386-unknown-mingw32
• − testsuite/tests/rts/outofmem.stderr-powerpc-apple-darwin
• testsuite/tests/safeHaskell/flags/SafeFlags17.stderr
• testsuite/tests/safeHaskell/safeLanguage/SafeLang15.stderr
• testsuite/tests/saks/should_compile/saks023.stdout
• testsuite/tests/saks/should_compile/saks034.stdout
• testsuite/tests/saks/should_compile/saks035.stdout
• testsuite/tests/showIface/Makefile
• + testsuite/tests/showIface/T26246a.hs
• + testsuite/tests/showIface/T26246a.stdout
• testsuite/tests/showIface/all.T
• + testsuite/tests/simd/should_run/T26410_ffi.hs
• + testsuite/tests/simd/should_run/T26410_ffi.stdout
• + testsuite/tests/simd/should_run/T26410_ffi_c.c
• + testsuite/tests/simd/should_run/T26410_prim.hs
• + testsuite/tests/simd/should_run/T26410_prim.stdout
• + testsuite/tests/simd/should_run/T26542.hs
• + testsuite/tests/simd/should_run/T26542.stdout
• + testsuite/tests/simd/should_run/T26550.hs
• + testsuite/tests/simd/should_run/T26550.stdout
• testsuite/tests/simd/should_run/all.T
• + testsuite/tests/simd/should_run/doublex2_shuffle.hs
• + testsuite/tests/simd/should_run/doublex2_shuffle.stdout
• + testsuite/tests/simd/should_run/doublex2_shuffle_baseline.hs
• + testsuite/tests/simd/should_run/doublex2_shuffle_baseline.stdout
• + testsuite/tests/simd/should_run/floatx4_shuffle.hs
• + testsuite/tests/simd/should_run/floatx4_shuffle.stdout
• + testsuite/tests/simd/should_run/floatx4_shuffle_baseline.hs
• + testsuite/tests/simd/should_run/floatx4_shuffle_baseline.stdout
• + testsuite/tests/simd/should_run/simd015.hs
• + testsuite/tests/simd/should_run/simd015.stdout
• + testsuite/tests/simd/should_run/simd016.hs
• + testsuite/tests/simd/should_run/simd016.stdout
• + testsuite/tests/simd/should_run/simd017.hs
• + testsuite/tests/simd/should_run/simd017.stdout
• testsuite/tests/simplCore/should_compile/DataToTagFamilyScrut.stderr
• testsuite/tests/simplCore/should_compile/DsSpecPragmas.hs
• testsuite/tests/simplCore/should_compile/DsSpecPragmas.stderr
• testsuite/tests/simplCore/should_compile/OpaqueNoCastWW.stderr
• testsuite/tests/simplCore/should_compile/T15056.stderr
• testsuite/tests/simplCore/should_compile/T15186.hs
• testsuite/tests/simplCore/should_compile/T15186A.hs
• testsuite/tests/simplCore/should_compile/T15205.stderr
• testsuite/tests/simplCore/should_compile/T15445.stderr
• testsuite/tests/simplCore/should_compile/T17366.stderr
• testsuite/tests/simplCore/should_compile/T17673.stderr
• testsuite/tests/simplCore/should_compile/T17966.stderr
• testsuite/tests/simplCore/should_compile/T18078.stderr
• testsuite/tests/simplCore/should_compile/T18995.stderr
• testsuite/tests/simplCore/should_compile/T19890.stderr
• testsuite/tests/simplCore/should_compile/T21948.stderr
• testsuite/tests/simplCore/should_compile/T21960.stderr
• testsuite/tests/simplCore/should_compile/T22309.stderr
• testsuite/tests/simplCore/should_compile/T22375DataFamily.stderr
• testsuite/tests/simplCore/should_compile/T23307.stderr
• testsuite/tests/simplCore/should_compile/T23307a.stderr
• + testsuite/tests/simplCore/should_compile/T24606.hs
• testsuite/tests/simplCore/should_compile/T24808.stderr
• testsuite/tests/simplCore/should_compile/T25389.stderr
• − testsuite/tests/simplCore/should_compile/T25713.stderr
• + testsuite/tests/simplCore/should_compile/T26051.hs
• + testsuite/tests/simplCore/should_compile/T26051.stderr
• + testsuite/tests/simplCore/should_compile/T26051_Import.hs
• + testsuite/tests/simplCore/should_compile/T26115.hs
• + testsuite/tests/simplCore/should_compile/T26115.stderr
• + testsuite/tests/simplCore/should_compile/T26116.hs
• + testsuite/tests/simplCore/should_compile/T26116.stderr
• + testsuite/tests/simplCore/should_compile/T26117.hs
• + testsuite/tests/simplCore/should_compile/T26117.stderr
• + testsuite/tests/simplCore/should_compile/T26323b.hs
• + testsuite/tests/simplCore/should_compile/T26349.hs
• + testsuite/tests/simplCore/should_compile/T26349.stderr
• + testsuite/tests/simplCore/should_compile/T26588.hs
• + testsuite/tests/simplCore/should_compile/T26589.hs
• testsuite/tests/simplCore/should_compile/T4201.stdout
• testsuite/tests/simplCore/should_compile/T7360.stderr
• testsuite/tests/simplCore/should_compile/T8331.stderr
• testsuite/tests/simplCore/should_compile/all.T
• testsuite/tests/simplCore/should_compile/rule2.stderr
• testsuite/tests/simplCore/should_compile/simpl017.stderr
• + testsuite/tests/simplCore/should_run/T26323.hs
• + testsuite/tests/simplCore/should_run/T26323.stdout
• testsuite/tests/simplCore/should_run/all.T
• testsuite/tests/simplStg/should_compile/T15226b.stderr
• testsuite/tests/simplStg/should_compile/T22840.stderr
• + testsuite/tests/splice-imports/DodgyLevelExport.hs
• + testsuite/tests/splice-imports/DodgyLevelExport.stderr
• + testsuite/tests/splice-imports/DodgyLevelExportA.hs
• + testsuite/tests/splice-imports/LevelImportExports.hs
• + testsuite/tests/splice-imports/LevelImportExports.stdout
• + testsuite/tests/splice-imports/LevelImportExportsA.hs
• testsuite/tests/splice-imports/Makefile
• + testsuite/tests/splice-imports/ModuleExport.hs
• + testsuite/tests/splice-imports/ModuleExport.stderr
• + testsuite/tests/splice-imports/ModuleExportA.hs
• + testsuite/tests/splice-imports/ModuleExportB.hs
• testsuite/tests/splice-imports/SI03.stderr
• testsuite/tests/splice-imports/SI05.stderr
• testsuite/tests/splice-imports/SI16.stderr
• testsuite/tests/splice-imports/SI18.stderr
• testsuite/tests/splice-imports/SI20.stderr
• testsuite/tests/splice-imports/SI25.stderr
• testsuite/tests/splice-imports/SI28.stderr
• testsuite/tests/splice-imports/SI29.stderr
• testsuite/tests/splice-imports/SI31.stderr
• + testsuite/tests/splice-imports/T26087.stderr
• + testsuite/tests/splice-imports/T26087A.hs
• + testsuite/tests/splice-imports/T26087B.hs
• + testsuite/tests/splice-imports/T26088.stderr
• + testsuite/tests/splice-imports/T26088A.hs
• + testsuite/tests/splice-imports/T26088B.hs
• + testsuite/tests/splice-imports/T26090.hs
• + testsuite/tests/splice-imports/T26090.stderr
• + testsuite/tests/splice-imports/T26090A.hs
• testsuite/tests/splice-imports/all.T
• testsuite/tests/tcplugins/CtIdPlugin.hs
• + testsuite/tests/tcplugins/T26395.hs
• + testsuite/tests/tcplugins/T26395.stderr
• + testsuite/tests/tcplugins/T26395_Plugin.hs
• testsuite/tests/tcplugins/all.T
• + testsuite/tests/th/GadtConSigs_th_dump1.hs
• + testsuite/tests/th/GadtConSigs_th_dump1.stderr
• + testsuite/tests/th/GadtConSigs_th_pprint1.hs
• + testsuite/tests/th/GadtConSigs_th_pprint1.stderr
• testsuite/tests/th/Makefile
• + testsuite/tests/th/QQInQuote.hs
• + testsuite/tests/th/QQTopError.hs
• + testsuite/tests/th/QQTopError.stderr
• testsuite/tests/th/T10267.stderr
• testsuite/tests/th/T10598_TH.stderr
• testsuite/tests/th/T10945.stderr
• testsuite/tests/th/T11452.stderr
• testsuite/tests/th/T14627.stderr
• testsuite/tests/th/T14681.stderr
• testsuite/tests/th/T15321.stderr
• testsuite/tests/th/T16180.hs
• testsuite/tests/th/T16976z.stderr
• testsuite/tests/th/T17804.stderr
• testsuite/tests/th/T17820a.stderr
• testsuite/tests/th/T17820b.stderr
• testsuite/tests/th/T17820c.stderr
• testsuite/tests/th/T17820d.stderr
• testsuite/tests/th/T17820e.stderr
• testsuite/tests/th/T20868.stdout
• testsuite/tests/th/T23829_hasty.stderr
• testsuite/tests/th/T23829_hasty_b.stderr
• testsuite/tests/th/T5508.stderr
• testsuite/tests/th/T5795.stderr
• testsuite/tests/th/T7276.stderr
• testsuite/tests/th/T8761.stderr
• + testsuite/tests/th/TH_Depends_Dir.hs
• + testsuite/tests/th/TH_Depends_Dir.stdout
• + testsuite/tests/th/TH_Depends_Dir_External.hs
• testsuite/tests/th/TH_Lift.stderr
• testsuite/tests/th/TH_NestedSplicesFail3.stderr
• testsuite/tests/th/TH_NestedSplicesFail4.stderr
• testsuite/tests/th/TH_StaticPointers02.stderr
• testsuite/tests/th/all.T
• testsuite/tests/th/overloaded/TH_overloaded_constraints_fail.stderr
• testsuite/tests/type-data/should_run/T22332a.stderr
• testsuite/tests/typecheck/T16127/T16127.stderr
• testsuite/tests/typecheck/no_skolem_info/T13499.stderr
• testsuite/tests/typecheck/no_skolem_info/T14040.stderr
• testsuite/tests/typecheck/no_skolem_info/T20232.stderr
• testsuite/tests/typecheck/should_compile/Makefile
• testsuite/tests/typecheck/should_compile/T11339.stderr
• testsuite/tests/typecheck/should_compile/T12427a.stderr
• testsuite/tests/typecheck/should_compile/T12763.stderr
• testsuite/tests/typecheck/should_compile/T13050.stderr
• testsuite/tests/typecheck/should_compile/T13651.hs
• − testsuite/tests/typecheck/should_compile/T13651.stderr
• + testsuite/tests/typecheck/should_compile/T14010.hs
• testsuite/tests/typecheck/should_compile/T14273.stderr
• testsuite/tests/typecheck/should_compile/T14434.hs
• testsuite/tests/typecheck/should_compile/T14590.stderr
• + testsuite/tests/typecheck/should_compile/T14745.hs
• testsuite/tests/typecheck/should_compile/T14774.stdout
• + testsuite/tests/typecheck/should_compile/T17705.hs
• testsuite/tests/typecheck/should_compile/T18406b.stderr
• testsuite/tests/typecheck/should_compile/T18529.stderr
• + testsuite/tests/typecheck/should_compile/T20873c.hs
• − testsuite/tests/typecheck/should_compile/T22141a.stderr
• − testsuite/tests/typecheck/should_compile/T22141b.stderr
• − testsuite/tests/typecheck/should_compile/T22141c.stderr
• − testsuite/tests/typecheck/should_compile/T22141d.stderr
• − testsuite/tests/typecheck/should_compile/T22141e.stderr
• testsuite/tests/typecheck/should_compile/T22560d.stdout
• testsuite/tests/typecheck/should_compile/T23171.hs
• testsuite/tests/typecheck/should_compile/T23739a.hs
• testsuite/tests/typecheck/should_compile/T25180.stderr
• testsuite/tests/typecheck/should_compile/T25266a.stderr
• + testsuite/tests/typecheck/should_compile/T25992.hs
• + testsuite/tests/typecheck/should_compile/T25992.stderr
• + testsuite/tests/typecheck/should_compile/T25992a.hs
• + testsuite/tests/typecheck/should_compile/T26030.hs
• + testsuite/tests/typecheck/should_compile/T26154.hs
• + testsuite/tests/typecheck/should_compile/T26154_A.hs
• + testsuite/tests/typecheck/should_compile/T26154_B.hs
• + testsuite/tests/typecheck/should_compile/T26154_B.hs-boot
• + testsuite/tests/typecheck/should_compile/T26154_Other.hs
• + testsuite/tests/typecheck/should_compile/T26225.hs
• + testsuite/tests/typecheck/should_compile/T26225b.hs
• + testsuite/tests/typecheck/should_compile/T26256a.hs
• + testsuite/tests/typecheck/should_compile/T26277.hs
• + testsuite/tests/typecheck/should_compile/T26345.hs
• + testsuite/tests/typecheck/should_compile/T26346.hs
• + testsuite/tests/typecheck/should_compile/T26350.hs
• + testsuite/tests/typecheck/should_compile/T26358.hs
• + testsuite/tests/typecheck/should_compile/T26376.hs
• + testsuite/tests/typecheck/should_compile/T26451.hs
• + testsuite/tests/typecheck/should_compile/T26457.hs
• + testsuite/tests/typecheck/should_compile/T26582.hs
• testsuite/tests/typecheck/should_compile/T9497a.stderr
• testsuite/tests/typecheck/should_compile/TcSpecPragmas.stderr
• + testsuite/tests/typecheck/should_compile/TyAppPat_Tricky.hs
• testsuite/tests/typecheck/should_compile/TypeRepCon.hs
• testsuite/tests/typecheck/should_compile/all.T
• testsuite/tests/typecheck/should_compile/hole_constraints_nested.stderr
• testsuite/tests/typecheck/should_compile/refinement_hole_fits.stderr
• testsuite/tests/typecheck/should_compile/subsumption_sort_hole_fits.stderr
• testsuite/tests/typecheck/should_compile/tc126.hs
• testsuite/tests/typecheck/should_compile/valid_hole_fits.stderr
• testsuite/tests/typecheck/should_fail/AmbigFDs.hs
• − testsuite/tests/typecheck/should_fail/AmbigFDs.stderr
• testsuite/tests/typecheck/should_fail/DoExpansion3.stderr
• testsuite/tests/typecheck/should_fail/FD3.stderr
• testsuite/tests/typecheck/should_fail/FDsFromGivens2.stderr
• testsuite/tests/typecheck/should_fail/T11672.stderr
• testsuite/tests/typecheck/should_fail/T12177.stderr
• testsuite/tests/typecheck/should_fail/T12373.stderr
• − testsuite/tests/typecheck/should_fail/T12563.stderr
• testsuite/tests/typecheck/should_fail/T13506.stderr
• testsuite/tests/typecheck/should_fail/T14605.hs
• testsuite/tests/typecheck/should_fail/T14605.stderr
• testsuite/tests/typecheck/should_fail/T14618.stderr
• testsuite/tests/typecheck/should_fail/T14884.stderr
• testsuite/tests/typecheck/should_fail/T15629.stderr
• testsuite/tests/typecheck/should_fail/T15801.stderr
• testsuite/tests/typecheck/should_fail/T15807.stderr
• testsuite/tests/typecheck/should_fail/T15883e.stderr
• testsuite/tests/typecheck/should_fail/T16074.stderr
• testsuite/tests/typecheck/should_fail/T16204c.stderr
• testsuite/tests/typecheck/should_fail/T16512a.stderr
• testsuite/tests/typecheck/should_fail/T18357a.stderr
• testsuite/tests/typecheck/should_fail/T18640a.stderr
• testsuite/tests/typecheck/should_fail/T18640b.stderr
• testsuite/tests/typecheck/should_fail/T18851.hs
• testsuite/tests/typecheck/should_fail/T18851b.hs
• − testsuite/tests/typecheck/should_fail/T18851b.stderr
• testsuite/tests/typecheck/should_fail/T18851c.hs
• − testsuite/tests/typecheck/should_fail/T18851c.stderr
• testsuite/tests/typecheck/should_fail/T19415.stderr
• testsuite/tests/typecheck/should_fail/T19415b.stderr
• testsuite/tests/typecheck/should_fail/T19627.stderr
• testsuite/tests/typecheck/should_fail/T20241b.stderr
• testsuite/tests/typecheck/should_fail/T20443b.stderr
• testsuite/tests/typecheck/should_fail/T20666.stderr
• testsuite/tests/typecheck/should_fail/T20666a.stderr
• testsuite/tests/typecheck/should_fail/T20666b.stderr
• − testsuite/tests/typecheck/should_fail/T20873c.hs
• − testsuite/tests/typecheck/should_fail/T20873c.stderr
• testsuite/tests/typecheck/should_fail/T21130.stderr
• testsuite/tests/typecheck/should_fail/T21530a.stderr
• testsuite/tests/typecheck/should_fail/T21530b.stderr
• testsuite/tests/typecheck/should_compile/T22141a.hs → testsuite/tests/typecheck/should_fail/T22141a.hs
• testsuite/tests/typecheck/should_fail/T22141a.stderr
• testsuite/tests/typecheck/should_compile/T22141b.hs → testsuite/tests/typecheck/should_fail/T22141b.hs
• testsuite/tests/typecheck/should_fail/T22141b.stderr
• testsuite/tests/typecheck/should_compile/T22141c.hs → testsuite/tests/typecheck/should_fail/T22141c.hs
• testsuite/tests/typecheck/should_fail/T22141c.stderr
• testsuite/tests/typecheck/should_compile/T22141d.hs → testsuite/tests/typecheck/should_fail/T22141d.hs
• testsuite/tests/typecheck/should_fail/T22141d.stderr
• testsuite/tests/typecheck/should_compile/T22141e.hs → testsuite/tests/typecheck/should_fail/T22141e.hs
• testsuite/tests/typecheck/should_fail/T22141e.stderr
• testsuite/tests/typecheck/should_compile/T22141e_Aux.hs → testsuite/tests/typecheck/should_fail/T22141e_Aux.hs
• testsuite/tests/typecheck/should_fail/T22684.stderr
• testsuite/tests/typecheck/should_fail/T22707.stderr
• testsuite/tests/typecheck/should_fail/T22912.stderr
• + testsuite/tests/typecheck/should_fail/T23162a.hs
• + testsuite/tests/typecheck/should_fail/T23162a.stderr
• testsuite/tests/typecheck/should_fail/T23427.stderr
• testsuite/tests/typecheck/should_fail/T23739b.stderr
• testsuite/tests/typecheck/should_fail/T23739c.stderr
• testsuite/tests/typecheck/should_fail/T24064.stderr
• testsuite/tests/typecheck/should_fail/T2414.stderr
• testsuite/tests/typecheck/should_fail/T24279.hs
• − testsuite/tests/typecheck/should_fail/T24279.stderr
• testsuite/tests/typecheck/should_fail/T25325.stderr
• testsuite/tests/typecheck/should_fail/T2534.stderr
• + testsuite/tests/typecheck/should_fail/T25950.hs
• + testsuite/tests/typecheck/should_fail/T25950.stderr
• + testsuite/tests/typecheck/should_fail/T26255a.hs
• + testsuite/tests/typecheck/should_fail/T26255a.stderr
• + testsuite/tests/typecheck/should_fail/T26255b.hs
• + testsuite/tests/typecheck/should_fail/T26255b.stderr
• + testsuite/tests/typecheck/should_fail/T26255c.hs
• + testsuite/tests/typecheck/should_fail/T26255c.stderr
• + testsuite/tests/typecheck/should_fail/T26318.hs
• + testsuite/tests/typecheck/should_fail/T26318.stderr
• + testsuite/tests/typecheck/should_fail/T26330.hs
• + testsuite/tests/typecheck/should_fail/T26330.stderr
• testsuite/tests/typecheck/should_fail/T5246.stderr
• testsuite/tests/typecheck/should_fail/T5978.stderr
• testsuite/tests/typecheck/should_fail/T6022.stderr
• testsuite/tests/typecheck/should_fail/T7264.stderr
• testsuite/tests/typecheck/should_fail/T7368a.stderr
• testsuite/tests/typecheck/should_fail/T7696.stderr
• testsuite/tests/typecheck/should_fail/T8142.stderr
• testsuite/tests/typecheck/should_fail/T8603.stderr
• testsuite/tests/typecheck/should_fail/T8883.stderr
• testsuite/tests/typecheck/should_fail/T9497d.stderr
• testsuite/tests/typecheck/should_fail/T9612.stderr
• testsuite/tests/typecheck/should_fail/TcStaticPointersFail03.stderr
• testsuite/tests/typecheck/should_fail/TyAppPat_TooMany.stderr
• testsuite/tests/typecheck/should_fail/UnliftedNewtypesFamilyKindFail2.stderr
• testsuite/tests/typecheck/should_fail/VisFlag1.stderr
• testsuite/tests/typecheck/should_fail/all.T
• testsuite/tests/typecheck/should_fail/tcfail037.stderr
• testsuite/tests/typecheck/should_fail/tcfail097.stderr
• testsuite/tests/typecheck/should_fail/tcfail122.stderr
• testsuite/tests/typecheck/should_fail/tcfail128.stderr
• testsuite/tests/typecheck/should_fail/tcfail140.stderr
• testsuite/tests/typecheck/should_fail/tcfail143.stderr
• testsuite/tests/typecheck/should_fail/tcfail153.stderr
• testsuite/tests/typecheck/should_fail/tcfail168.stderr
• testsuite/tests/typecheck/should_fail/tcfail174.stderr
• testsuite/tests/typecheck/should_fail/tcfail177.stderr
• testsuite/tests/typecheck/should_fail/tcfail185.stderr
• testsuite/tests/typecheck/should_run/T10284.stderr
• testsuite/tests/typecheck/should_run/T13838.stderr
• testsuite/tests/typecheck/should_run/T9497a-run.stderr
• testsuite/tests/typecheck/should_run/T9497b-run.stderr
• testsuite/tests/typecheck/should_run/T9497c-run.stderr
• testsuite/tests/typecheck/should_run/Typeable1.stderr
• + testsuite/tests/unboxedsums/UbxSumUnpackedSize.hs
• + testsuite/tests/unboxedsums/UbxSumUnpackedSize.stdout
• + testsuite/tests/unboxedsums/UbxSumUnpackedSize.stdout-ws-32
• testsuite/tests/unboxedsums/all.T
• testsuite/tests/unboxedsums/unboxedsums_unit_tests.hs
• testsuite/tests/unboxedsums/unpack_sums_7.stdout
• testsuite/tests/unsatisfiable/T23816.stderr
• testsuite/tests/unsatisfiable/UnsatDefer.stderr
• + testsuite/tests/vdq-rta/should_compile/T25127_data.hs
• + testsuite/tests/vdq-rta/should_compile/T25127_data_inst.hs
• + testsuite/tests/vdq-rta/should_compile/T25127_infix.hs
• + testsuite/tests/vdq-rta/should_compile/T25127_newtype.hs
• testsuite/tests/vdq-rta/should_compile/all.T
• testsuite/tests/vdq-rta/should_fail/T23738_fail_pun.stderr
• testsuite/tests/vdq-rta/should_fail/T23739_fail_case.hs
• testsuite/tests/vdq-rta/should_fail/T23739_fail_case.stderr
• testsuite/tests/vdq-rta/should_fail/T24159_type_syntax_th_fail.script
• + testsuite/tests/vdq-rta/should_fail/T25127_fail_arity.hs
• + testsuite/tests/vdq-rta/should_fail/T25127_fail_arity.stderr
• + testsuite/tests/vdq-rta/should_fail/T25127_fail_th_quote.hs
• + testsuite/tests/vdq-rta/should_fail/T25127_fail_th_quote.stderr
• testsuite/tests/vdq-rta/should_fail/all.T
• testsuite/tests/warnings/should_compile/DataToTagWarnings.hs
• + testsuite/tests/warnings/should_compile/DodgyExports02.hs
• + testsuite/tests/warnings/should_compile/DodgyExports02.stderr
• + testsuite/tests/warnings/should_compile/DodgyExports03.hs
• + testsuite/tests/warnings/should_compile/DodgyExports03.stderr
• + testsuite/tests/warnings/should_compile/DuplicateModExport.hs
• + testsuite/tests/warnings/should_compile/DuplicateModExport.stderr
• + testsuite/tests/warnings/should_compile/EmptyModExport.hs
• + testsuite/tests/warnings/should_compile/EmptyModExport.stderr
• testsuite/tests/warnings/should_compile/T14794a.hs
• testsuite/tests/warnings/should_compile/T14794a.stderr
• testsuite/tests/warnings/should_compile/T14794b.hs
• testsuite/tests/warnings/should_compile/T14794b.stderr
• testsuite/tests/warnings/should_compile/T14794c.hs
• testsuite/tests/warnings/should_compile/T14794c.stderr
• testsuite/tests/warnings/should_compile/T14794d.hs
• testsuite/tests/warnings/should_compile/T14794d.stderr
• testsuite/tests/warnings/should_compile/T14794e.hs
• testsuite/tests/warnings/should_compile/T14794e.stderr
• testsuite/tests/warnings/should_compile/T14794f.hs
• testsuite/tests/warnings/should_compile/T14794f.stderr
• testsuite/tests/warnings/should_compile/all.T
• testsuite/tests/wasm/should_run/control-flow/LoadCmmGroup.hs
• testsuite/tests/wasm/should_run/control-flow/RunWasm.hs
• testsuite/tests/wcompat-warnings/Template.hs
• + testsuite/tests/wcompat-warnings/WCompatWarningsOn.stderr
• utils/check-exact/ExactPrint.hs
• utils/check-exact/Parsers.hs
• utils/check-exact/Preprocess.hs
• utils/deriveConstants/Main.hs
• utils/genprimopcode/Lexer.x
• utils/genprimopcode/Main.hs
• utils/genprimopcode/Parser.y
• utils/genprimopcode/ParserM.hs
• utils/genprimopcode/Syntax.hs
• utils/genprimopcode/genprimopcode.cabal
• utils/ghc-pkg/Main.hs
• utils/ghc-pkg/ghc-pkg.cabal.in
• utils/ghc-toolchain/exe/Main.hs
• utils/ghc-toolchain/ghc-toolchain.cabal
• utils/ghc-toolchain/src/GHC/Toolchain/CheckArm.hs
• + utils/ghc-toolchain/src/GHC/Toolchain/CheckPower.hs
• + utils/ghc-toolchain/src/GHC/Toolchain/Library.hs
• utils/ghc-toolchain/src/GHC/Toolchain/ParseTriple.hs
• utils/ghc-toolchain/src/GHC/Toolchain/PlatformDetails.hs
• utils/ghc-toolchain/src/GHC/Toolchain/Target.hs
• utils/ghc-toolchain/src/GHC/Toolchain/Tools/Cc.hs
• utils/ghc-toolchain/src/GHC/Toolchain/Tools/Cpp.hs
• utils/ghc-toolchain/src/GHC/Toolchain/Tools/Cxx.hs
• utils/ghc-toolchain/src/GHC/Toolchain/Tools/Link.hs
• utils/ghc-toolchain/src/GHC/Toolchain/Tools/MergeObjs.hs
• utils/ghc-toolchain/src/GHC/Toolchain/Utils.hs
• utils/haddock/CHANGES.md
• utils/haddock/doc/cheatsheet/haddocks.md
• utils/haddock/doc/markup.rst
• utils/haddock/haddock-api/haddock-api.cabal
• utils/haddock/haddock-api/resources/html/Linuwial.std-theme/linuwial.css
• utils/haddock/haddock-api/src/Haddock/Backends/Hoogle.hs
• utils/haddock/haddock-api/src/Haddock/Backends/Hyperlinker.hs
• utils/haddock/haddock-api/src/Haddock/Backends/Hyperlinker/Renderer.hs
• utils/haddock/haddock-api/src/Haddock/Backends/Hyperlinker/Utils.hs
• utils/haddock/haddock-api/src/Haddock/Backends/LaTeX.hs
• utils/haddock/haddock-api/src/Haddock/Backends/Xhtml/Decl.hs
• utils/haddock/haddock-api/src/Haddock/Backends/Xhtml/Utils.hs
• utils/haddock/haddock-api/src/Haddock/Convert.hs
• utils/haddock/haddock-api/src/Haddock/GhcUtils.hs
• utils/haddock/haddock-api/src/Haddock/Interface.hs
• utils/haddock/haddock-api/src/Haddock/Interface/AttachInstances.hs
• utils/haddock/haddock-api/src/Haddock/Interface/Create.hs
• utils/haddock/haddock-api/src/Haddock/Interface/LexParseRn.hs
• utils/haddock/haddock-api/src/Haddock/Interface/Rename.hs
• utils/haddock/haddock-api/src/Haddock/InterfaceFile.hs
• utils/haddock/haddock-api/src/Haddock/Types.hs
• utils/haddock/haddock-library/haddock-library.cabal
• utils/haddock/haddock-library/src/Documentation/Haddock/Parser.hs
• utils/haddock/haddock-library/test/Documentation/Haddock/ParserSpec.hs
• utils/haddock/haddock-test/haddock-test.cabal
• utils/haddock/haddock-test/src/Test/Haddock.hs
• utils/haddock/haddock-test/src/Test/Haddock/Config.hs
• utils/haddock/haddock.cabal
• utils/haddock/html-test/ref/Bug1004.html
• utils/haddock/html-test/ref/Bug1050.html
• + utils/haddock/html-test/ref/Bug25739.html
• + utils/haddock/html-test/ref/Bug26246.html
• utils/haddock/html-test/ref/Bug548.html
• utils/haddock/html-test/ref/Bug85.html
• utils/haddock/html-test/ref/Bug923.html
• utils/haddock/html-test/ref/Bug973.html
• utils/haddock/html-test/ref/BundledPatterns.html
• utils/haddock/html-test/ref/BundledPatterns2.html
• utils/haddock/html-test/ref/ConstructorPatternExport.html
• utils/haddock/html-test/ref/GADTRecords.html
• utils/haddock/html-test/ref/Hash.html
• utils/haddock/html-test/ref/ImplicitParams.html
• utils/haddock/html-test/ref/Instances.html
• utils/haddock/html-test/ref/LinearTypes.html
• utils/haddock/html-test/ref/PatternSyns.html
• utils/haddock/html-test/ref/PromotedTypes.html
• + utils/haddock/html-test/ref/RedactTypeSynonyms.html
• utils/haddock/html-test/ref/TypeOperators.html
• + utils/haddock/html-test/src/Bug25739.hs
• + utils/haddock/html-test/src/Bug26246.hs
• + utils/haddock/html-test/src/RedactTypeSynonyms.hs
• utils/haddock/html-test/src/TypeOperators.hs
• utils/haddock/hypsrc-test/Main.hs
• utils/haddock/hypsrc-test/ref/src/Bug1091.html
• utils/haddock/hypsrc-test/ref/src/CPP.html
• utils/haddock/hypsrc-test/ref/src/Classes.html
• utils/haddock/hypsrc-test/ref/src/Constructors.html
• utils/haddock/hypsrc-test/ref/src/Identifiers.html
• utils/haddock/hypsrc-test/ref/src/LinkingIdentifiers.html
• utils/haddock/hypsrc-test/ref/src/Literals.html
• utils/haddock/hypsrc-test/ref/src/Operators.html
• utils/haddock/hypsrc-test/ref/src/Polymorphism.html
• utils/haddock/hypsrc-test/ref/src/PositionPragmas.html
• utils/haddock/hypsrc-test/ref/src/Quasiquoter.html
• utils/haddock/hypsrc-test/ref/src/Records.html
• utils/haddock/hypsrc-test/ref/src/TemplateHaskellQuasiquotes.html
• utils/haddock/hypsrc-test/ref/src/TemplateHaskellSplices.html
• utils/haddock/hypsrc-test/ref/src/Types.html
• utils/haddock/hypsrc-test/ref/src/UsingQuasiquotes.html
• utils/haddock/latex-test/ref/LinearTypes/LinearTypes.tex
• + utils/haddock/latex-test/ref/RedactTypeSynonyms/RedactTypeSynonyms.tex
• + utils/haddock/latex-test/src/RedactTypeSynonyms/RedactTypeSynonyms.hs
• utils/hpc
• utils/hsc2hs
• utils/iserv/iserv.cabal.in
• utils/jsffi/dyld.mjs

The diff was not included because it is too large.