Hannes Siebenhandl pushed to branch wip/hie-file-improvements at Glasgow Haskell Compiler / GHC

Commits:

• 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
  

• 84a087d5
  by Sylvain Henry at 2025-11-28T17:35:28-05:00

  Fix PIC jump tables on Windows (#24016)
  
  Avoid overflows in jump tables by using a base label closer to the jump
  targets. See added Note [Jump tables]
  

• 82db7042
  by Zubin Duggal at 2025-11-28T17:36:10-05:00

  rts/linker/PEi386: Copy strings before they are inserted into LoadedDllCache. The original strings are temporary and might be freed at an arbitrary point.
  
  Fixes #26613
  

• ff3f0d09
  by Ben Gamari at 2025-11-29T18:34:28-05:00

  gitlab-ci: Run ghcup-metadata jobs on OpenCape runners
  
  This significantly reduces our egress traffic
  and makes the jobs significantly faster.

• ef0dc33b
  by Matthew Pickering at 2025-11-29T18:35:10-05:00

  Use 'OsPath' in getModificationTimeIfExists
  
  This part of the compiler is quite hot during recompilation checking in
  particular since the filepaths will be translated to a string. It is
  better to use the 'OsPath' native function, which turns out to be easy
  to do.
  

• fa3bd0a6
  by Georgios Karachalias at 2025-11-29T18:36:05-05:00

  Use OsPath in PkgDbRef and UnitDatabase, not FilePath
  

• 0d7c05ec
  by Ben Gamari at 2025-12-01T03:13:46-05: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.
  
  -------------------------
  Metric Decrease:
      T14697
  -------------------------
  

• 3b2c4598
  by Vladislav Zavialov at 2025-12-01T03:14:29-05:00

  Namespace-specified wildcards in import/export lists (#25901)
  
  This change adds support for top-level namespace-specified wildcards
  `type ..` and `data ..` to import and export lists.
  
  Examples:
    import M (type ..) -- imports all type and class constructors from M
    import M (data ..) -- imports all data constructors and terms from M
    module M (type .., f) where
      -- exports all type and class constructors defined in M,
      -- plus the function 'f'
  
  The primary intended usage of this feature is in combination with module
  aliases, allowing namespace disambiguation:
    import Data.Proxy as T (type ..)  -- T.Proxy is unambiguously the type constructor
    import Data.Proxy as D (data ..)  -- D.Proxy is unambiguously the data constructor
  
  The patch accounts for the interactions of wildcards with:
  * Imports with `hiding` clauses
  * Import warnings -Wunused-imports, -Wdodgy-imports
  * Export warnings -Wduplicate-exports, -Wdodgy-exports
  
  Summary of the changes:
  
  1. Move the NamespaceSpecifier type from GHC.Hs.Binds to GHC.Hs.Basic,
     making it possible to use it in more places in the AST.
  
  2. Extend the AST (type: IE) with a representation of `..`, `type ..`,
     and `data ..` (constructor: IEWholeNamespace). Per the proposal, the
     plain `..` is always rejected with a dedicated error message.
  
  3. Extend the grammar in Parser.y with productions for `..`, `type ..`,
     and `data ..` in both import and export lists.
  
  4. Implement wildcard imports by updating the `filterImports` function
     in GHC.Rename.Names; the logic for IEWholeNamespace is roughly
     modeled after the Nothing (no explicit import list) case.
  
  5. Implement wildcard exports by updating the `exports_from_avail`
     function in GHC.Tc.Gen.Export; the logic for IEWholeNamespace is
     closely modeled after the IEModuleContents case.
  
  6. Refactor and extend diagnostics to report the new warnings and
     errors. See PsErrPlainWildcardImport, DodgyImportsWildcard,
                 PsErrPlainWildcardExport, DodgyExportsWildcard,
                 TcRnDupeWildcardExport.
  
  Note that this patch is specifically about top-level import/export
  items. Subordinate import/export items are left unchanged.
  

• c71faa76
  by Luite Stegeman at 2025-12-01T03:16:05-05:00

  rts: Handle overflow of ELF section header string table
  
  If the section header string table is stored in a section greater
  than or equal to SHN_LORESERVE (0xff00), the 16-bit field e_shstrndx
  in the ELF header does not contain the section number, but rather
  an overflow value SHN_XINDEX (0xffff) indicating that we need to look
  elsewhere.
  
  This fixes the linker by not using e_shstrndx directly but calling
  elf_shstrndx, which correctly handles the SHN_XINDEX value.
  
  Fixes #26603
  

• ab20eb54
  by Mike Pilgrem at 2025-12-01T22:46:55+00:00

  Re CLC issue 292 Warn GHC.Internal.List.{init,last} are partial
  
  Also corrects the warning for `tail` to refer to `Data.List.uncons` (like the existing warning for `head`).
  
  In module `Settings.Warnings`, applies `-Wno-x-partial` to the `filepath`, and `parsec` packages (outside GHC's repository).
  
  Also bumps submodules.
  

• fc1d7f79
  by Jade Lovelace at 2025-12-02T11:04:09-05:00

  docs: fix StandaloneKindSignatures in DataKinds docs
  
  These should be `type` as otherwise GHC reports a duplicate definition
  error.
  

• beae879b
  by Rodrigo Mesquita at 2025-12-03T15:42:37+01:00

  task: Substitute some datatypes for newtypes
  
  * Substitutes some data type declarations for newtype declarations
  * Adds comment to `LlvmConfigCache`, which must decidedly not be a
    newtype.
  
  Fixes #23555
  

• 3bd7dd44
  by mangoiv at 2025-12-04T04:36:45-05:00

  Renamer: reinstate the template haskell level check in notFound
  
  Out-of-scope names might be caused by a staging error, as is explained by
  Note [Out of scope might be a staging error] in GHC.Tc.Utils.Env.hs.
  This logic was assumed to be dead code after 217caad1 and has thus been
  removed. This commit reintroduces it and thus fixes issue #26099.
  

• 0318010b
  by Zubin Duggal at 2025-12-04T04:37:27-05:00

  testlib: Optionally include the way name in the expected output file
  
  This allows us to have different outputs for different ways.
  

• 6d945fdd
  by Zubin Duggal at 2025-12-04T04:37:27-05:00

  testsuite: Accept output of tests failing in ext-interp way due to differing compilation requirements
  
  Fixes #26552
  

• 0ffc5243
  by Cheng Shao at 2025-12-04T04:38:09-05:00

  devx: minor fixes for compile_flags.txt
  
  This patch includes minor fixes for compile_flags.txt to improve
  developer experience when using clangd as language server to hack on
  RTS C sources:
  
  - Ensure `-fPIC` is passed and `__PIC__` is defined, to be coherent
    with `-DDYNAMIC` and ensure the `__PIC__` guarded code paths are
    indexed
  - Add the missing `-DRtsWay` definition, otherwise a few source files
    like `RtsUtils.c` and `Trace.c` would produce clangd errors
  

• e36a5fcb
  by Matthew Pickering at 2025-12-05T16:25:57-05:00

  Add support for building bytecode libraries
  
  A bytecode library is a collection of bytecode files (.gbc) and a
  library which combines together additional object files.
  
  A bytecode library is created by invoking GHC with the `-bytecodelib`
  flag.
  
  A library can be created from in-memory `ModuleByteCode` linkables or
  by passing `.gbc` files as arguments on the command line.
  
  Fixes #26298
  

• 8f9ae339
  by Matthew Pickering at 2025-12-05T16:25:57-05:00

  Load bytecode libraries to satisfy package dependencies
  
  This commit allows you to use a bytecode library to satisfy a package
  dependency when using the interpreter.
  
  If a user enables `-fprefer-byte-code`, then if a package provides a
  bytecode library, that will be loaded and used to satisfy the
  dependency.
  
  The main change is to separate the relevant parts of the `LoaderState`
  into external and home package byte code. Bytecode is loaded into either
  the home package or external part (similar to HPT/EPS split), HPT
  bytecode can be unloaded. External bytecode is never unloaded.
  
  The unload function has also only been called with an empty list of
  "stable linkables" for a long time. It has been modified to directly
  implement a complete unloading of the home package bytecode linkables.
  
  At the moment, the bytecode libraries are found in the "library-dirs"
  field from the package description. In the future when `Cabal`
  implements support for "bytecode-library-dirs" field, we can read the
  bytecode libraries from there. No changes to the Cabal submodule are
  necessary at the moment.
  
  Four new tests are added in testsuite/tests/cabal, which generate fake
  package descriptions and test loading the libraries into GHCi.
  
  Fixes #26298
  

• 54458ce4
  by mangoiv at 2025-12-05T16:26:50-05:00

  ExplicitLevelImports: improve documentation of the code
  
  - more explicit names for variable names like `flg` or `topLevel`
  - don't pass the same value twice to functions
  - some explanations of interesting but undocumented code paths
  - adjust comment to not mention non-existent error message
  

• c7061392
  by mangoiv at 2025-12-05T16:27:42-05:00

  driver: don't expect nodes to exist when checking paths between them
  
  In `mgQueryZero`, previously node lookups were expected to never fail,
  i.e. it was expected that when calculating the path between two nodes in
  a zero level import graph, both nodes would always exist. This is not
  the case, e.g. in some situations involving exact names (see the
  test-case). The fix is to first check whether the node is present in the
  graph at all, instead of panicking, just to report that there is no
  path.
  
  Closes #26568
  

• d6cf8463
  by Peng Fan at 2025-12-06T11:06:28-05:00

  NCG/LA64: Simplify genCCall into two parts
  
  genCCall is too long, so it's been simplified into two parts:
  genPrim and genLibCCall.
  
  Suggested by Andreas Klebinger
  

• 9d371d23
  by Matthew Pickering at 2025-12-06T11:07:09-05:00

  hadrian: Use a response file to invoke GHC for dep gathering.
  
  In some cases we construct an argument list too long for GHC to
  handle directly on windows. This happens when we generate
  the dependency file because the command line will contain
  references to a large number of .hs files.
  
  To avoid this we now invoke GHC using a response file when
  generating dependencies to sidestep length limitations.
  
  Note that we only pass the actual file names in the dependency
  file. Why? Because this side-steps #26560
  

• 0043bfb0
  by Marc Scholten at 2025-12-06T11:08:03-05:00

  update xhtml to 3000.4.0.0
  
  haddock-api: bump xhtml bounds
  
  haddock-api: use lazy text instead of string to support xhtml 3000.4.0.0
  
  Bumping submodule xhtml to 3000.4.0.0
  
  add xhtml to stage0Packages
  
  remove unused import of writeUtf8File
  
  Remove redundant import
  
  Update haddock golden files for xhtml 3000.4.0.0
  
  Metric Decrease:
      haddock.Cabal
      haddock.base
  

• fc958fc9
  by Julian Ospald at 2025-12-06T11:08:53-05:00

  rts: Fix object file format detection in loadArchive
  
  Commit 76d1041dfa4b96108cfdd22b07f2b3feb424dcbe seems to
  have introduced this bug, ultimately leading to failure of
  test T11788. I can only theorize that this test isn't run
  in upstream's CI, because they don't build a static GHC.
  
  The culprit is that we go through the thin archive, trying
  to follow the members on the filesystem, but don't
  re-identify the new object format of the member. This pins
  `object_fmt` to `NotObject` from the thin archive.
  
  Thanks to @angerman for spotting this.
  

• 0f297f6e
  by mangoiv at 2025-12-06T11:09:44-05:00

  users' guide: don't use f strings in the python script to ensure compatibility with python 3.5
  

• 3bfe7aa2
  by Matthew Pickering at 2025-12-07T12:18:57-05:00

  ci: Try using multi repl in ghc-in-ghci test
  
  This should be quite a bit faster than the ./hadrian/ghci command as it
  doesn't properly build all the dependencies.
  

• 2ef1601a
  by Rodrigo Mesquita at 2025-12-07T12:19:38-05:00

  Stack.Decode: Don't error on bitmap size 0
  
  A RET_BCO may have a bitmap with no payload.
  In that case, the bitmap = 0.
  
  One can observe this by using -ddump-bcos and interpreting
  
  ```
  main = pure ()
  ```
  
  Observe, for instance, that the BCO for this main function has size 0:
  
  ```
  ProtoBCO Main.main#0:
     \u []
         break<main:Main,0>() GHC.Internal.Base.pure
                                  GHC.Internal.Base.$fApplicativeIO GHC.Internal.Tuple.()
     bitmap:  0 []
     BRK_FUN <breakarray> main:Main 0 <cc>
     PACK     () 0
     PUSH_G   GHC.Internal.Base.$fApplicativeIO
     PUSH_APPLY_PP
     PUSH_G   GHC.Internal.Base.pure
     ENTER
  ```
  
  Perhaps we never tried to decode a stack in which a BCO like this was
  present. However, for the debugger, we want to decode stacks of threads
  stopped at breakpoints, and these kind of BCOs do get on a stack under
  e.g. `stg_apply_interp_info` frames.
  
  See the accompanying test in the next commit for an example to trigger
  the bug this commit fixes.
  
  Fixes #26640
  

• 747153d2
  by Rodrigo Mesquita at 2025-12-07T12:19:38-05:00

  Add test for #26640
  

• d4b1e353
  by Simon Hengel at 2025-12-10T00:00:02-05:00

  Fix syntax error in gadt_syntax.rst

• 91cc8be6
  by Cheng Shao at 2025-12-10T00:00:43-05:00

  ci: fix "ci.sh clean" to address frequent out of space error on windows runners
  
  This patch fixes the `ci.sh clean` logic to address frequent out of
  space error on windows runners; previously it didn't clean up the
  inplace mingw blobs, which is the largest source of space leak on
  windows runners. See added comment for detailed explanation.
  

• fe2b79f4
  by Recursion Ninja at 2025-12-10T08:34:18-05:00

  Narrow before optimising MUL/DIV/REM into shifts
  
  The MUL/DIV/REM operations can be optimised into shifts when one of the
  operands is a constant power of 2. However, as literals in Cmm are
  stored as 'Integer', for this to be correct we first need to narrow the
  literal to the appropriate width before checking whether the literal is
  a power of 2.
  
  Fixes #25664
  

• 06c2349c
  by Recursion Ninja at 2025-12-10T08:34:58-05:00

  Decouple 'Language.Haskell.Syntax.Type' from 'GHC.Utils.Panic'
  
    - Remove the *original* defintion of 'hsQTvExplicit' defined within 'Language.Haskell.Syntax.Type'
  
    - Redefine 'hsQTvExplicit' as 'hsq_explicit' specialized to 'GhcPass' exported by 'GHC.Utils.Panic'
  
    - Define 'hsQTvExplicitBinders' as 'hsq_explicit' specialized to 'DocNameI' exported by 'Haddock.GhcUtils'.
  
    - Replace all call sites of the original 'hsQTvExplicit' definition with either:
      1. 'hsQTvExplicit' updated definition
      2. 'hsQTvExplicitBinders'
  
  All call sites never entered the 'XLHsQTyVars' constructor branch, but a call to 'panic' existed on this code path because the type system was not strong enought to guarantee that the 'XLHsQTyVars' construction was impossible.
  These two specialized functions provide the type system with enough information to make that guarantee, and hence the dependancy on 'panic' can be removed.
  

• ac0815d5
  by sheaf at 2025-12-10T23:39:57-05:00

  Quantify arg before mult in function arrows
  
  As noted in #23764, we expect quantification order to be left-to-right,
  so that in a type such as
  
    a %m -> b
  
  the inferred quantification order should be [a, m, b] and not [m, a, b].
  
  This was addressed in commit d31fbf6c, but that commit failed to update
  some other functions such as GHC.Core.TyCo.FVs.tyCoFVsOfType.
  
  This affects Haddock, as whether we print an explicit forall or not
  depends on whether the inferred quantification order matches the actual
  quantification order.
  

• 2caf796e
  by sheaf at 2025-12-10T23:39:57-05:00

  Haddock: improvements to ty-var quantification
  
  This commit makes several improvements to how Haddock deals with the
  quantification of type variables:
  
    1. In pattern synonyms, Haddock used to jumble up universal and
       existential quantification. That is now fixed, fixing #26252.
  
       Tested in the 'PatternSyns2' haddock-html test.
  
    2. The logic for computing whether to use an explicit kind annotation
       for a type variable quantified in a forall was not even wrong.
       This commit improves the heuristic, but it will always remain an
       imperfect heuristic (lest we actually run kind inference again).
       In the future (#26271), we hope to avoid reliance on this heuristic.
  

• b14bdd59
  by Teo Camarasu at 2025-12-10T23:40:38-05:00

  Add explicit export list to GHC.Num
  
  Let's make clear what this module exports to allow us to easily deprecate and remove some of these in the future. Resolves https://gitlab.haskell.org/ghc/ghc/-/issues/26625
  

• d99f8326
  by Cheng Shao at 2025-12-11T19:14:18-05:00

  compiler: remove unused CPP code in foreign stub
  
  This patch removes unused CPP code in the generated foreign stub:
  
  - `#define IN_STG_CODE 0` is not needed, since `Rts.h` already
    includes this definition
  - The `if defined(__cplusplus)` code paths are not needed in the `.c`
    file, since we don't generate C++ stubs and don't include C++
    headers in our stubs. But it still needs to be present in the `.h`
    header since it might be later included into C++ source files.
  

• 46c9746f
  by Cheng Shao at 2025-12-11T19:14:57-05:00

  configure: bump LlvmMaxVersion to 22
  
  This commit bumps LlvmMaxVersion to 22; 21.x releases have been
  available since Aug 26th, 2025 and there's no regressions with 21.x so
  far. This bump is also required for updating fedora image to 43.
  

• 96fce8d0
  by Cheng Shao at 2025-12-12T01:17:51+01:00

  hadrian: add support for building with UndefinedBehaviorSanitizer
  
  This patch adds a +ubsan flavour transformer to hadrian to build all
  stage1+ C/C++ code with UndefinedBehaviorSanitizer. This is
  particularly useful to catch potential undefined behavior in the RTS
  codebase.
  

• f7a06d8c
  by Cheng Shao at 2025-12-12T01:17:51+01:00

  ci: update alpine/fedora & add ubsan job
  
  This patch updates alpine image to 3.23, fedora image to 43, and adds
  a `x86_64-linux-fedora43-validate+debug_info+ubsan` job that's run in
  validate/nightly pipelines to catch undefined behavior in the RTS
  codebase.
  

• 2ccd11ca
  by Cheng Shao at 2025-12-12T01:17:51+01:00

  rts: fix zero-length VLA undefined behavior in interpretBCO
  
  This commit fixes a zero-length VLA undefined behavior in interpretBCO, caught by UBSan:
  
  ```
  +rts/Interpreter.c:3133:19: runtime variable length array bound evaluates to non-positive value 0
  ```
  

• 4156ed19
  by Cheng Shao at 2025-12-12T01:17:51+01:00

  rts: fix unaligned ReadSpB in interpretBCO
  
  This commit fixes unaligned ReadSpB in interpretBCO, caught by UBSan:
  
  ```
  +rts/Interpreter.c:2174:64: runtime load of misaligned address 0x004202059dd1 for type 'StgWord', which requires 8 byte alignment
  ```
  
  To perform proper unaligned read, we define StgUnalignedWord as a type
  alias of StgWord with aligned(1) attribute, and load StgUnalignedWord
  instead of StgWord in ReadSpB, so the C compiler is aware that we're
  not loading with natural alignment.
  

• fef89fb9
  by Cheng Shao at 2025-12-12T01:17:51+01:00

  rts: fix signed integer overflow in subword arithmetic in interpretBCO
  
  This commit fixes signed integer overflow in subword arithmetic in
  interpretBCO, see added note for detailed explanation.
  

• 3c001377
  by Cheng Shao at 2025-12-13T05:03:15-05:00

  ci: use treeless fetch for perf notes
  
  This patch improves the ci logic for fetching perf notes by using
  treeless fetch
  (https://github.blog/open-source/git/get-up-to-speed-with-partial-clone-and-shallow-clone),
  to avoid downloading all blobs of the perf notes repo at once, and
  only fetch the actually required blobs on-demand when needed. This
  makes the initial `test-metrics.sh pull` operation much faster, and
  also more robust, since we are seeing an increasing rate of 504 errors
  in CI when fetching all perf notes at once, which is a major source of
  CI flakiness at this point.
  
  Co-authored-by: Codex <codex@openai.com>
  

• 123a8d77
  by Peter Trommler at 2025-12-13T05:03:57-05:00

  Cmm: remove restriction in MachOp folding
  

• 0b54b5fd
  by Andreas Klebinger at 2025-12-13T05:04:38-05:00

  Remove explicit Typeable deriviations.
  

• 08b13f7b
  by Cheng Shao at 2025-12-13T05:05:18-05:00

  ci: set gc.auto=0 during setup stage
  
  This patch sets `gc.auto=0` during `setup` stage of CI, see added
  comment for detailed explanation.
  

• 3b5aecb5
  by Ben Gamari at 2025-12-13T23:43:10+01:00

  Bump exceptions submodule to 0.10.11
  

• c32de3b0
  by Johan Förberg at 2025-12-15T02:36:03-05:00

  base: Define Semigroup and Monoid instances for lazy ST
  
  CLC proposal:
  https://github.com/haskell/core-libraries-committee/issues/374
  
  Fixes #26581
  

• 4f8b660c
  by mangoiv at 2025-12-15T02:37:05-05:00

  ci: do not require nightly cabal-reinstall job to succeed
  

• 2c2a3ef3
  by Cheng Shao at 2025-12-15T11:51:53-05:00

  docs: drop obsolete warning about -fexternal-interpreter on windows
  
  This patch drops an obsolete warning about -fexternal-interpreter not
  supported on windows; it is supported since a long time ago, including
  the profiled way.
  

• 68573aa5
  by Marc Scholten at 2025-12-15T11:53:00-05:00

  haddock: Drop Haddock.Backends.HaddockDB as it's unused
  

• b230d549
  by mangoiv at 2025-12-16T15:17:45-05:00

  base: generalize delete{Firsts,}By
  
  When we delete{Firsts,}By we should not require the
  lists to be  the same type. This is an especially useful
  generalisation in the case of deleteFirstsBy because we
  can skip an invocation of the map function.
  
  This change was discussed on the core-libraries-committee's bug
  tracker at https://github.com/haskell/core-libraries-committee/issues/372.
  

• 6a2b43e3
  by Cheng Shao at 2025-12-16T15:18:30-05:00

  compiler: clean up redundant LANGUAGE pragmas
  
  This patch bumps `default-language` of `ghc`/`ghc-bin` from `GHC2021`
  to `GHC2024` (which is supported in ghc 9.10, current boot ghc lower
  version bound), and also cleans up redundant `LANGUAGE` pragmas (as
  well as `default-extensions`/`other-extensions`) that are already
  implied by `GHC2024`.
  
  Co-authored-by: Codex <codex@openai.com>
  

• fca9cd7c
  by sheaf at 2025-12-18T13:18:18-05:00

  X86 CodeGen: fix assign_eax_sse_regs
  
  We must set %al to the number of SSE2 registers that contain arguments
  (in case we are dealing with a varargs function). The logic for counting
  how many arguments reside in SSE2 registers was incorrect, as it used
  'isFloatFormat', which incorrectly ignores vector registers.
  
  We now instead do case analysis on the register class:
  
    is_sse_reg r =
      case targetClassOfReg platform r of
        RcFloatOrVector -> True
        RcInteger       -> False
  
  This change is necessary to prevent segfaults in T20030_test1j, because
  subsequent commits change the format calculations, resulting in vector
  formats more often.
  

• 53150617
  by sheaf at 2025-12-18T13:18:19-05:00

  X86 regUsageOfInstr: fix format for IMUL
  
  When used with 8-bit operands, the IMUL instruction returns the result
  in the lower 16 bits of %rax (also known as %ax). This is different
  than for the other sizes, where an input at 16, 32 or 64 bits will
  result in 16, 32 or 64 bits of output in both %rax and %rdx.
  
  This doesn't affect the behaviour of the compiler, because we don't
  allow partial writes at sub-word sizes. The rationale is explained
  in Wrinkle [Don't allow scalar partial writes] in Note [Register formats in liveness analysis],
  in GHC.CmmToAsm.Reg.Liveness.
  

• c7a56dd1
  by sheaf at 2025-12-18T13:18:19-05:00

  Liveness analysis: consider register formats
  
  This commit updates the register allocator to be a bit more careful in
  situations in which a single register is used at multiple different
  formats, e.g. when xmm1 is used both to store a Double# and a DoubleX2#.
  
  This is done by introducing the 'Regs' newtype around 'UniqSet RegWithFormat',
  for which the combining operations take the larger of the two formats
  instead of overriding the format.
  
  Operations on 'Regs' are defined in 'GHC.CmmToAsm.Reg.Regs'. There is
  a modest compile-time cost for the additional overhead for tracking
  register formats, which causes the metric increases of this commit.
  
  The subtle aspects of the implementation are outlined in
  Note [Register formats in liveness analysis] in GHC.CmmToAsm.Reg.Liveness.
  
  Fixes #26411 #26611
  
  -------------------------
  Metric Increase:
      T12707
      T26425
      T3294
  -------------------------
  

• c2e83339
  by sheaf at 2025-12-18T13:18:19-05:00

  Register allocator: reload at same format as spill
  
  This commit ensures that if we spill a register onto the stack at a
  given format, we then always reload the register at this same format.
  
  This ensures we don't end up in a situation where we spill F64x2 but end
  up only reloading the lower F64. This first reload would make us believe
  the whole data is in a register, thus silently losing the upper 64 bits
  of the spilled register's contents.
  
  Fixes #26526
  

• 55ab583b
  by sheaf at 2025-12-18T13:18:19-05:00

  Register allocation: writes redefine format
  
  As explained in Note [Allocated register formats] in GHC.CmmToAsm.Reg.Linear,
  we consider all writes to redefine the format of the register.
  
  This ensures that in a situation such as
  
    movsd .Ln6m(%rip),%v1
    shufpd $0,%v1,%v1
  
  we properly consider the broadcast operation to change the format of %v1
  from F64 to F64x2.
  
  This completes the fix to #26411 (test in T26411b).
  

• 951402ed
  by Vladislav Zavialov at 2025-12-18T13:19:05-05:00

  Parser: improve mkModuleImpExp, remove checkImportSpec
  
  1. The `mkModuleImpExp` helper now knows whether it is processing an import or
     export list item, and uses this information to produce a more accurate error
     message for `import M (T(..,x))` with PatternSynonyms disabled.
     The old message incorrectly referred to this case as an export form.
  
  2. The `checkImportSpec` helper is removed in favor of more comprehensive error
     checking in `mkModuleImpExp`.
  
  3. Additionaly, the invariants of `ImpExpList` and `ImpExpAllWith` have been
     made more explicit in the comments and assertions (calls to 'panic').
  
  Test case: import-syntax-no-ext
  

• 47d83d96
  by Vladislav Zavialov at 2025-12-18T13:19:06-05:00

  Subordinate namespace-specified wildcards (#25901)
  
  Add support for subordinate namespace-specified wildcards
  `X(type ..)` and `X(data ..)` to import and export lists.
  
  Examples:
    import M (Cls(type ..))  -- imports Cls and all its associated types
    import M (Cls(data ..))  -- imports Cls and all its methods
    module M (R(data ..), C(type ..)) where
      -- exports R and all its data constructors and record fields;
      -- exports C and all its associated types, but not its methods
  
  The scope of this change is limited to the case where the wildcard is the only
  subordinate import/export item, whereas the more complex forms `X(type .., f)`
  or `X(type .., data ..)` are unsupported and raise the newly introduced
  PsErrUnsupportedExplicitNamespace error. This restriction may be lifted later.
  
  Summary of the changes:
  
  1. Refactor IEThingAll to store its extension field XIEThingAll as a record
     IEThingAllExt instead of a tuple.
  
  2. Extend the AST by adding a NamespaceSpecifier field to IEThingAllExt,
     representing an optional namespace specifier `type` or `data` in front
     of a subordinate wildcard `X(..)`.
  
  3. Extend the grammar in Parser.y with productions for `type ..` and `data ..`
     in subordinate import/export items.
  
  4. Introduce `filterByNamespaceGREs` to filter [GlobalRdrElt] by a
     NamespaceSpecifier; use it in `filterImports` and `exports_from_avail`
     to account for the namespace specifier in IEThingAll.
  
  5. Improve diagnostics by storing more information in DodgyImportsEmptyParent
     and DodgyExportsEmptyParent.
  
  Test cases:
    T25901_sub_e   T25901_sub_f   T25901_sub_g   T25901_sub_a
    T25901_sub_b   T25901_sub_c   T25901_sub_d   T25901_sub_w
    DodgyImports02 DodgyImports03 DodgyImports04
  

• eac418bb
  by Recursion Ninja at 2025-12-18T13:19:48-05:00

  Removing the 'Data' instance for 'InstEnv'.
  
  The 'Data' instance is blocking work on Trees that Grow, and the
  'Data' instance seem to have been added without a clear purpose.
  

• e920e038
  by Recursion Ninja at 2025-12-18T13:19:48-05:00

  'Decouple Language.Haskell.Syntax.Decls' from 'GHC.Unit.Module.Warnings'
  

• bd38b76c
  by Cheng Shao at 2025-12-18T13:20:31-05:00

  testsuite: improve coverage of foundation test
  
  This patch refactors the `foundation` test a bit to improve coverage:
  
  - Instead of using a hard-coded seed, a random seed is now taken from
    the command line, and printed upon test failure. This improves test
    coverage over many future CI runs, and shall a failure occur, the
    seed is available in the CI log for local reproduction.
  - The iterations count is bumped to 1000 instead of 100, similar to
    the bump in `test-primops`. Runtime timeout is bumped 2x just to be
    safe.
  - Improve `newLCGGen` by using non-atomic loads/stores on a
    `MutableByteArray#` for storing mutable `Word64`, this test doesn't
    use parallelism in the first place
  - Fixed a few compiler warnings and removed redundant pragmas and
    imports
  
  Co-authored-by: Codex <codex@openai.com>
  

• 3995187c
  by Sylvain Henry at 2025-12-18T13:21:45-05:00

  Doc: document -pgmi "" (#26634)
  

• 5729418c
  by Cheng Shao at 2025-12-18T13:22:29-05:00

  rts: use __builtin_mul_overflow for hs_mulIntMayOflo
  
  This patch uses `__builtin_mul_overflow` to implement
  `hs_mulIntMayOflo`. This is a GNU C checked arithmetic builtin
  function supported by gcc/clang, is type-generic so works for both
  32-bit/64-bit, and makes the code both more efficient and easier to
  read/maintain than the previous hand rolled logic.
  

• 1ca4b49a
  by Cheng Shao at 2025-12-18T13:23:11-05:00

  compiler/rts: fix ABI mismatch in barf() invocations
  
  This patch fixes a long-standing issue of ABI mismatch in `barf()`
  invocations, both in compiler-emitted code and in hand written Cmm
  code:
  
  - In RTS, we have `barf()` which reports a fatal internal error
    message and exits the program.
  - `barf()` is a variadic C function! When used as a callee of a
    foreign call with `ccall` calling convention instead of `capi`,
    there is an ABI mismatch between the caller and the callee!
  - Unfortunately, both the compiler and the Cmm sources contain many
    places where we call `barf()` via `ccall` convention!! Like, when
    you write `foreign "C" barf("foo object (%p) entered!", R1)`, it
    totally doesn't do what you think it'll do at all!! The second
    argument `R1` is not properly passed in `va_list`, and the behavior
    is completely undefined!!
  - Even more unfortunately, this issue has been sitting around long
    enough because the ABI mismatch is subtle enough on normie platforms
    like x64 and arm64.
  - But there are platforms like wasm32 that are stricter about ABI, and
    the broken `barf()` invocations already causes trouble for wasm
    backend: we had to use ugly hacks like `barf(errmsg, NULL)` to make
    `wasm-ld` happy, and even with this band-aid, compiler-generated
    `barf()` invocations are still broken, resulting in regressions in
    certain debug-related functionality, e.g. `-dtag-inference-checks`
    is broken on wasm32 (#22882).
  
  This patch properly fixes the issue:
  
  - We add non-variadic `barf` wrappers in the RTS that can be used as
    `ccall` callees
  - Both the compiler `emitBarf` logic and the hand-written Cmm are
    changed to call these wrappers
  - `emitBarf` now also properly annotates the foreign call as
    `CmmNeverReturns` to indicate it's a noreturn call to enable more
    efficient code generation
  
  `-dtag-inference-checks` now works on wasm. Closes #22882.
  
  Co-authored-by: Codex <codex@openai.com>
  

• b3dd23b9
  by Vilim Lendvaj at 2025-12-18T13:23:57-05:00

  Remove outdated comment
  
  The Traversable instance for ZipList is no longer in
  GHC.Internal.Data.Traversable. In fact, it is right below this very comment.
  

• 9a9c2f03
  by Cheng Shao at 2025-12-18T13:24:39-05:00

  compiler: remove unused OtherSection logic
  
  This patch removes the OtherSection logic in Cmm, given it's never
  actually used by any of our backends.
  

• 91edd292
  by Wolfgang Jeltsch at 2025-12-19T03:18:19-05:00

  Remove unused known-key and name variables for generics
  
  This removes the known-key and corresponding name variables for `K1`,
  `M1`, `R`, `D`, `C`, `S`, and `URec` from `GHC.Generics`, as they are
  apparently nowhere used in GHC’s source code.
  

• 73ee7e38
  by Wolfgang Jeltsch at 2025-12-19T03:19:02-05:00

  Remove unused known keys and names for generics classes
  
  This removes the known-key and corresponding name variables for
  `Datatype`, `Constructor`, and `Selector` from `GHC.Generics`, as they
  are apparently nowhere used in GHC’s source code.
  

• f69c5f14
  by Cheng Shao at 2025-12-19T03:19:45-05:00

  wasm: fix handling of ByteArray#/MutableByteArray# arguments in JSFFI imports
  
  This patch fixes the handling of ByteArray#/MutableByteArray#
  arguments in JSFFI imports, see the amended note and manual for
  explanation. Also adds a test to witness the fix.
  
  Co-authored-by: Codex <codex@openai.com>
  

• 224446a2
  by Cheng Shao at 2025-12-20T07:49:54-05:00

  rts: workaround -Werror=maybe-uninitialized false positives
  
  In some cases gcc might report -Werror=maybe-uninitialized that we
  know are false positives, but need to workaround it to make validate
  builds with -Werror pass.
  

• 251ec087
  by Cheng Shao at 2025-12-20T07:49:54-05:00

  hadrian: use -Og as C/C++ optimization level when debugging
  
  This commit enables -Og as optimization level when compiling the debug
  ways of rts. According to gcc documentation
  (https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html#index-Og),
  -Og is a better choice than -O0 for producing debuggable code. It's
  also supported by clang as well, so it makes sense to use it as a
  default for debugging. Also add missing -g3 flag to C++ compilation
  flags in +debug_info flavour transformer.
  

• fb586c67
  by Cheng Shao at 2025-12-20T07:50:36-05:00

  compiler: replace DList with OrdList
  
  This patch removes `DList` logic from the compiler and replaces it
  with `OrdList` which also supports O(1) concatenation and should be
  more memory efficient than the church-encoded `DList`.
  

• 8149c987
  by Cheng Shao at 2025-12-20T17:06:51-05:00

  hadrian: add with_profiled_libs flavour transformer
  
  This patch adds a `with_profiled_libs` flavour transformer to hadrian
  which is the exact opposite of `no_profiled_libs`. It adds profiling
  ways to stage1+ rts/library ways, and doesn't alter other flavour
  settings. It is useful when needing to test profiling logic locally
  with a quick flavour.
  

• 746b18cd
  by Cheng Shao at 2025-12-20T17:06:51-05:00

  hadrian: fix missing profiled dynamic libraries in profiled_ghc
  
  This commit fixes the profiled_ghc flavour transformer to include
  profiled dynamic libraries as well, since they're supported by GHC
  since !12595.
  

• 4dd7e3b9
  by Cheng Shao at 2025-12-20T17:07:33-05:00

  ci: set http.postBuffer to mitigate perf notes timeout on some runners
  
  This patch sets http.postBuffer to mitigate the timeout when fetching
  perf notes on some runners with slow internet connection. Fixes #26684.
  

• bc36268a
  by Wolfgang Jeltsch at 2025-12-21T16:23:24-05:00

  Remove unused known keys and names for type representations
  
  This removes the known-key and corresponding name variables for
  `TrName`, `TrNameD`, `TypeRep`, `KindRepTypeLitD`, `TypeLitSort`, and
  `mkTrType`, as they are apparently nowhere used in GHC’s source code.
  

• ff5050e9
  by Wolfgang Jeltsch at 2025-12-21T16:24:04-05:00

  Remove unused known keys and names for natural operations
  
  This removes the known-key and corresponding name variables for
  `naturalAndNot`, `naturalLog2`, `naturalLogBaseWord`, `naturalLogBase`,
  `naturalPowMod`, `naturalSizeInBase`, `naturalToFloat`, and
  `naturalToDouble`, as they are apparently nowhere used in GHC’s source
  code.
  

• 424388c2
  by Wolfgang Jeltsch at 2025-12-21T16:24:45-05:00

  Remove the unused known key and name for `Fingerprint`
  
  This removes the variables for the known key and the name of the
  `Fingerprint` data constructor, as they are apparently nowhere used in
  GHC’s source code.
  

• a1ed86fe
  by Wolfgang Jeltsch at 2025-12-21T16:25:26-05:00

  Remove the unused known key and name for `failIO`
  
  This removes the variables for the known key and the name of the
  `failIO` operation, as they are apparently nowhere used in GHC’s source
  code.
  

• b8220daf
  by Wolfgang Jeltsch at 2025-12-21T16:26:07-05:00

  Remove the unused known key and name for `liftM`
  
  This removes the variables for the known key and the name of the `liftM`
  operation, as they are apparently nowhere used in GHC’s source code.
  

• eb0628b1
  by Wolfgang Jeltsch at 2025-12-21T16:26:47-05:00

  Fix the documentation of `hIsClosed`
  

• db1ce858
  by sheaf at 2025-12-22T17:11:17-05:00

  Do deep subsumption when computing valid hole fits
  
  This commit makes a couple of improvements to the code that
  computes "valid hole fits":
  
    1. It uses deep subsumption for data constructors.
       This matches up the multiplicities, as per
       Note [Typechecking data constructors].
       This fixes #26338 (test: LinearHoleFits).
  
    2. It now suggests (non-unidirectional) pattern synonyms as valid
       hole fits. This fixes #26339 (test: PatSynHoleFit).
  
    3. It uses 'stableNameCmp', to make the hole fit output deterministic.
  
  -------------------------
  Metric Increase:
      hard_hole_fits
  -------------------------
  

• 72ee9100
  by sheaf at 2025-12-22T17:11:17-05:00

  Speed up hole fits with a quick pre-test
  
  This speeds up the machinery for valid hole fits by doing a small
  check to rule out obviously wrong hole fits, such as:
  
    1. A hole fit identifier whose type has a different TyCon at the head,
       after looking through foralls and (=>) arrows, e.g.:
          hole_ty = Int
          cand_ty = Maybe a
       or
          hole_ty = forall a b. a -> b
          cand_ty = forall x y. Either x y
    2. A hole fit identifier that is not polymorphic when the hole type
       is polymorphic, e.g.
         hole_ty = forall a. a -> a
         cand_ty = Int -> Int
  
  -------------------------
  Metric Decrease:
      hard_hole_fits
  -------------------------
  

• 30e513ba
  by Cheng Shao at 2025-12-22T17:12:00-05:00

  configure: remove unused win32-tarballs.md5sum
  
  This patch removes the unused `win32-tarballs.md5sum` file from the
  tree. The current mingw tarball download logic in
  `mk/get-win32-tarballs.py` fetches and checks against `SHA256SUM` from
  the same location where the tarballs are fetched, and this file has
  been unused for a few years.
  

• a2d52b3b
  by Wolfgang Jeltsch at 2025-12-23T04:47:33-05:00

  Add an operation `System.IO.hGetNewlineMode`
  
  This commit also contains some small code and documentation changes for
  related operations, for the sake of consistency.
  

• b26d134a
  by Cheng Shao at 2025-12-23T04:48:15-05:00

  rts: opportunistically reclaim slop space in shrinkMutableByteArray#
  
  Previously, `shrinkMutableByteArray#` shrinks a `MutableByteArray#`
  in-place by assigning the new size to it, and zeroing the extra slop
  space. That slop space is not reclaimed and wasted. But it's often the
  case that we allocate a `MutableByteArray#` upfront, then shrink it
  shortly after, so the `MutableByteArray#` closure sits right at the
  end of a nursery block; this patch identifies such chances, and also
  shrink `bd->free` if possible, reducing heap space fragmentation.
  
  Co-authored-by: Codex <codex@openai.com>
  
  -------------------------
  Metric Decrease:
      T10678
  -------------------------
  

• c72ddabf
  by Cheng Shao at 2025-12-23T16:13:23-05:00

  hadrian: fix bootstrapping with ghc-9.14
  
  This patch fixes bootstrapping GHC with ghc-9.14, tested locally with
  ghc-9.14.1 release as bootstrapping GHC.
  

• 0fd6d8e4
  by Cheng Shao at 2025-12-23T16:14:05-05:00

  hadrian: pass -keep-tmp-files to test ghc when --keep-test-files is enabled
  
  This patch makes hadrian pass `-keep-tmp-files` to test ghc when
  `--keep-test-files` is enabled, so you can check the ghc intermediate
  files when debugging certain test failures. Closes #26688.
  

• 81d10134
  by Cheng Shao at 2025-12-24T06:11:52-05:00

  configure: remove dead code in configure scripts
  
  This patch removes dead code in our configure scripts, including:
  
  - Variables and auto-detected programs that are not used
  - autoconf functions that are not used, or export a variable that's
    not used
  - `AC_CHECK_HEADERS` invocations that don't have actual corresponding
    `HAVE_XXX_H` usage
  - Other dead code (e.g. stray `AC_DEFUN()`)
  
  Co-authored-by: Codex <codex@openai.com>
  

• fb1381c3
  by Wolfgang Jeltsch at 2025-12-24T06:12:34-05:00

  Remove unused known keys and names for list operations
  
  This removes the known-key and corresponding name variables for
  `concat`, `filter`, `zip`, and `(++)`, as they are apparently nowhere
  used in GHC’s source code.
  

• 7b9c20f4
  by Recursion Ninja at 2025-12-24T10:35:36-05:00

  Decoupling Language.Haskell.Syntax.Binds from GHC.Types.Basic
  by transferring InlinePragma types between the modules.
  
    * Moved InlinePragma data-types to Language.Haskell.Syntax.Binds.InlinePragma
  
    * Partitioned of Arity type synonyms to GHC.Types.Arity
  
    * InlinePragma is now extensible via Trees That Grow
  
    * Activation is now extensible via Trees That Grow
  
    * Maybe Arity change to more descriptive InlineSaturation data-type
  
    * InlineSaturation information removed from InlinePragma during GHS parsing pass
  
    * Cleaned up the exposed module interfaces of the new modules
  

• a3afae0c
  by Simon Peyton Jones at 2025-12-25T15:26:36-05:00

  Check for rubbish literals in Lint
  
  Addresses #26607.
  
  See new Note [Checking for rubbish literals] in GHC.Core.Lint
  

• 8a317b6f
  by Aaron Allen at 2026-01-01T03:05:15-05:00

  [#26183] Associated Type Iface Fix
  
  When determining "extras" for class decl interface entries, axioms for
  the associated types need to included so that dependent modules will be
  recompiled if those axioms change.
  
  resolves #26183
  

• ae1aeaab
  by Cheng Shao at 2026-01-01T03:06:32-05:00

  testsuite: run numeric tests with optasm when available
  
  This patch adds the `optasm` extra way to nueric tests when NCG is
  available. Some numeric bugs only surface with optimization, omitting
  this can hide these bugs and even make them slip into release! (e.g. #26711)
  

• 6213bb57
  by maralorn at 2026-01-02T16:30:32+01:00

  GHC.Internal.Exception.Context: Fix comment
  
  on addExceptionAnnotation

• b820ff50
  by Janis Voigtlaender at 2026-01-05T02:43:18-05:00

  GHC.Internal.Control.Monad.replicateM: Fix comment
  

• a8a94aad
  by Cheng Shao at 2026-01-05T16:24:04-05:00

  hadrian: drops unused PE linker script for windows
  
  This patch drops unused PE linker script for windows in the
  `MergeObjects` builder of hadrian. The linker script is used for
  merging object files into a single `HS*.o` object file and undoing the
  effect of split sections, when building the "ghci library" object
  file. However, we don't build the ghci library on windows, and this
  code path is actually unreachable.
  

• 53038ea9
  by Cheng Shao at 2026-01-05T16:24:04-05:00

  hadrian: drop unused logic for building ghci libraries
  
  This patch drops the unused logic for building ghci libraries in
  hadrian:
  
  - The term "ghci library" refers to an optional object file per
    library `HS*.o`, which is merged from multiple object files in that
    library using the `MergeObjects` builder in hadrian.
  - The original rationale of having a ghci library object, in addition
    to normal archives, was to speedup ghci loading, since the combined
    object is linked with a linker script to undo the effects of
    `-fsplit-sections` to reduce section count and make it easier for
    the RTS linker to handle.
  - However, most GHC builds enable `dynamicGhcPrograms` by default, in
    such cases the ghci library would already not be built.
  - `dynamicGhcPrograms` is disabled on Windows, but still we don't
    build the ghci library due to lack of functioning merge objects
    command.
  - The only case that we actually build ghci library objects, are
    alpine fully static bindists. However, for other reasons, split
    sections is already disabled for fully static builds anyway!
  - There will not be any regression if the ghci library objects are
    absent from a GHC global libdir when `dynamicGhcPrograms` is
    disabled. The RTS linker can already load the archives without any
    issue.
  
  Hence the removal. We now forcibly disable ghci libraries for all
  Cabal components, and rip out all logic related to `MergeObjects` and
  ghci libraries in hadrian. This also nicely cleans up some old todos
  and fixmes that are no longer relevant.
  
  Note that MergeObjects in hadrian is not the same thing as merge
  objects in the GHC driver. The latter is not affected by this patch.
  
  -------------------------
  Metric Decrease:
      libdir
  -------------------------
  
  Co-authored-by: Codex <codex@openai.com>
  

• 8f209336
  by Simon Jakobi at 2026-01-05T16:24:48-05:00

  User's guide: Fix link to language extensions
  
  Instead of linking to haddocks, it seemed more useful to link
  to the extension overview in the user's guide.
  
  Closes #26614.
  

• 0b7df6db
  by Simon Peyton Jones at 2026-01-06T09:32:23-05:00

  Improved fundeps for closed type families
  
  The big payload of this commit is to execute the plan suggested
  in #23162, by improving the way that we generate functional
  dependencies for closed type families.
  
  It is all described in Note [Exploiting closed type families]
  
  Most of the changes are in GHC.Tc.Solver.FunDeps
  
  Other small changes
  
  * GHC.Tc.Solver.bumpReductionDepth.  This function brings together the code that
     * Bumps the depth
     * Checks for overflow
    Previously the two were separated, sometimes quite widely.
  
  * GHC.Core.Unify.niFixSubst: minor improvement, removing an unnecessary
    itraetion in the base case.
  
  * GHC.Core.Unify: no need to pass an InScopeSet to
    tcUnifyTysForInjectivity. It can calculate one for itself; and it is
    never inspected anyway so it's free to do so.
  
  * GHC.Tc.Errors.Ppr: slight impovement to the error message for
    reduction-stack overflow, when a constraint (rather than a type) is
    involved.
  
  * GHC.Tc.Solver.Monad.wrapUnifier: small change to the API
  

• fde8bd88
  by Simon Peyton Jones at 2026-01-06T09:32:23-05:00

  Add missing (KK4) to kick-out criteria
  
  There was a missing case in kick-out that meant we could fail
  to solve an eminently-solvable constraint.
  
  See the new notes about (KK4)
  

• 00082844
  by Simon Peyton Jones at 2026-01-06T09:32:23-05:00

  Some small refactorings of error reporting in the typechecker
  
  This is just a tidy-up commit.
  
  * Add ei_insoluble to ErrorItem, to cache insolubility.
    Small tidy-up.
  
  * Remove `is_ip` and `mkIPErr` from GHC.Tc.Errors; instead enhance mkDictErr
    to handle implicit parameters.  Small refactor.
  

• fe4cb252
  by Simon Peyton Jones at 2026-01-06T09:32:24-05:00

  Improve recording of insolubility for fundeps
  
  This commit addresses #22652, by recording when the fundeps for
  a constraint are definitely insoluble.  That in turn improves the
  perspicacity of the pattern-match overlap checker.
  
  See Note [Insoluble fundeps]
  

• df0ffaa5
  by Simon Peyton Jones at 2026-01-06T09:32:24-05:00

  Fix a buglet in niFixSubst
  
  The MR of which this is part failed an assertion check extendTvSubst
  because we extended the TvSubst with a CoVar.  Boo.
  
  This tiny patch fixes it, and adds the regression test from #13882
  that showed it up.
  

• 3d6aba77
  by konsumlamm at 2026-01-06T09:33:16-05:00

  Fix changelog formatting

• 69e0ab59
  by Cheng Shao at 2026-01-06T19:37:56-05:00

  compiler: add targetHasRTSWays function
  
  This commit adds a `targetHasRTSWays` util function in
  `GHC.Driver.Session` to query if the target RTS has a given Ways (e.g.
  WayThreaded).
  

• 25a0ab94
  by Cheng Shao at 2026-01-06T19:37:56-05:00

  compiler: link on-demand external interpreter with threaded RTS
  
  This commit makes the compiler link the on-demand external interpreter
  program with threaded RTS if it is available in the target RTS ways.
  This is a better default than the previous single-threaded RTS, and it
  enables the external interpreter to benefit from parallelism when
  deserializing CreateBCOs messages.
  

• 92404a2b
  by Cheng Shao at 2026-01-06T19:37:56-05:00

  hadrian: link iserv with threaded RTS
  
  This commit makes hadrian link iserv with threaded RTS if it's
  available in the RTS ways. Also cleans up the iserv main C program
  which can be replaced by the `-fkeep-cafs` link-time option.
  

• a20542d2
  by Cheng Shao at 2026-01-06T19:38:38-05:00

  ghc-internal: remove unused GMP macros
  
  This patch removes unused GMP related macros from `ghc-internal`. The
  in-tree GMP version was hard coded and outdated, but it was not used
  anywhere anyway.
  

• 4079dcd6
  by Cheng Shao at 2026-01-06T19:38:38-05:00

  hadrian: fix in-tree gmp configure error on newer c compilers
  
  Building in-tree gmp on newer c compilers that default to c23 fails at
  configure stage, this patch fixes it, see added comment for
  explanation.
  

• 414d1fe1
  by Cheng Shao at 2026-01-06T19:39:20-05:00

  compiler: fix LLVM backend pdep/pext handling for i386 target
  
  This patch fixes LLVM backend's pdep/pext handling for i386 target,
  and also removes non-existent 128/256/512 bit hs_pdep/hs_pext callees.
  See amended note for more explanation. Fixes #26450.
  
  Co-authored-by: Codex <codex@openai.com>
  

• c7f6fba3
  by Cheng Shao at 2026-01-06T19:39:20-05:00

  ci: remove allow_failure flag for i386 alpine job
  
  The LLVM codegen issue for i386 has been fixed, and the i386 alpine
  job should pass now. This commit removes the allow_failure flag so
  that other i386 regressions in the future are signaled more timely.
  

• 52d00c05
  by Simon Peyton Jones at 2026-01-07T10:24:21-05:00

  Add missing InVar->OutVar lookup in SetLevels
  
  As #26681 showed, the SetLevels pass was failing to map an InVar to
  an OutVar.  Very silly!  I'm amazed it hasn't broken before now.
  
  I have improved the type singatures (to mention InVar and OutVar)
  so it's more obvious what needs to happen.
  

• ab0a5594
  by Cheng Shao at 2026-01-07T10:25:04-05:00

  hadrian: drop deprecated pkgHashSplitObjs code path
  
  This patch drops deprecated `pkgHashSplitObjs` code path from hadrian,
  since GHC itself has removed split objs support many versions ago and
  this code path is unused.
  

• bb3a2ba1
  by Cheng Shao at 2026-01-07T10:25:44-05:00

  hadrian: remove linting/assertion in quick-validate flavour
  
  The `quick-validate` flavour is meant for testing ghc and passing the
  testsuite locally with similar settings to `validate` but faster. This
  patch removes the linting/assertion overhead in `quick-validate` to
  improve developer experience. I also took the chance to simplify
  redundant logic of rts/library way definition in `validate` flavour.
  

• 7971f5dd
  by Cheng Shao at 2026-01-07T10:26:26-05:00

  deriveConstants: clean up unused constants
  
  This patch cleans up unused constants from `deriveConstants`, they are
  not used by C/Cmm code in the RTS, nor compiler-generated code.
  
  Co-authored-by: Codex <codex@openai.com>
  

• 4df96993
  by Cheng Shao at 2026-01-07T10:27:08-05:00

  hadrian: pass -fno-omit-frame-pointer with +debug_info
  
  This patch adds `-fno-omit-frame-pointer` as C/C++ compilation flag
  when compiling with `+debug_info` flavour transformer. It's a sane
  default when you care about debugging and reliable backtraces, and
  makes debugging/profiling with bpf easier.
  

• 8a3900a3
  by Aaron Allen at 2026-01-07T10:27:57-05:00

  [26705] Include TyCl instances in data fam iface entry
  
  Ensures dependent modules are recompiled when the class instances for a
  data family instance change.
  
  resolves #26705
  

• a0b980af
  by Cheng Shao at 2026-01-07T10:28:38-05:00

  hadrian: remove unused Hp2Ps/Hpc builders
  
  This patch removes the Hp2Ps/Hpc builders from hadrian, they are
  unused in the build system. Note that the hp2ps/hpc programs are still
  built and not affected.
  

• 50a58757
  by Cheng Shao at 2026-01-07T10:29:20-05:00

  hadrian: only install js files to libdir for wasm/js targets
  
  There are certain js files required for wasm/js targets to work, and
  previously hadrian would install those js files to libdir
  unconditionally on other targets as well. This could be a minor
  annoyance for packagers especially when the unused js files contain
  shebangs that interfere with the packaging process. This patch makes
  hadrian only selectively install the right js files for the right
  targets.
  
  Co-authored-by: Codex <codex@openai.com>
  

• da40e553
  by Simon Peyton Jones at 2026-01-07T10:30:00-05:00

  Add flavour transformer assertions_stage1
  
  This allows us to enable -DDEBUG assertions in the stage1 compiler
  

• ec3cf767
  by Cheng Shao at 2026-01-08T06:24:31-05:00

  make: remove unused Makefiles from legacy make build system
  
  This patch removes unused Makefiles from legacy make build system; now
  they are never used by hadrian in any way, and they already include
  common boilerplate mk files that are long gone in the make build
  system removal, hence the housecleaning.
  
  Co-authored-by: Codex <codex@openai.com>
  

• 04ea3f83
  by Cheng Shao at 2026-01-08T06:25:13-05:00

  compiler: use -O3 as LLVM optimization level for ghc -O2
  
  The GHC driver clamps LLVM optimization level to `-O2` due to LLVM
  crashes, but those were historical issues many years ago that are no
  longer relevant for LLVM versions we support today. This patch changes
  the driver to use `-O3` as LLVM optimization level when compiling with
  `-O2`, which is a better default when we're willing to trade
  compilation time for faster generated code.
  

• 472df471
  by Peter Trommler at 2026-01-08T13:28:54-05:00

  Use half-word literals in info tables
  
  With this commit info tables are mapped to the same assembler code
  on big-endian and little-endian platforms.
  
  Fixes #26579.
  

• 393f9c51
  by Simon Peyton Jones at 2026-01-08T13:29:35-05:00

  Refactor srutOkForBinderSwap
  
  This MR does a small refactor:
  
  * Moves `scrutOkForBinderSwap` and `BinderSwapDecision`
    to GHC.Core.Utils
  
  * Inverts the sense of the coercion it returns, which makes
    more sense
  
  No effect on behaviour
  

• ad76fb0f
  by Simon Peyton Jones at 2026-01-08T13:29:36-05:00

  Improve case merging
  
  This small MR makes case merging happen a bit more often than
  it otherwise could, by getting join points out of the way.
  
  See #26709 and GHC.Core.Utils
    Note [Floating join points out of DEFAULT alternatives]
  

• 4c9395f5
  by Cheng Shao at 2026-01-08T13:30:16-05:00

  hadrian: remove broken hsc2hs flag when cross compiling to windows
  
  This patch removes the `--via-asm` hsc2hs flag when cross compiling to
  windows. With recent llvm-mingw toolchain, it would fail with:
  
  ```
  x86_64-w64-mingw32-hsc2hs: Cannot combine instructions: [Quad 8,Long 4,Long 241,Ref ".Ltmp1-.Ltmp0"]
  ```
  
  The hsc2hs default `--cross-compile` logic is slower but works.
  

• 71fdef55
  by Simon Peyton Jones at 2026-01-08T13:30:57-05:00

  Try harder to keep the substitution empty
  
  Avoid unnecessary cloning of variables in the Simplifier.
  
  Addresses #26724,
  
  See Note [Keeping the substitution empty]
  
  We get some big wins in compile time
  
  Metrics: compile_time/bytes allocated
  -------------------------------------
                                           Baseline
                      Test    Metric          value      New value Change
  ----------------------------------------------------------------------------
  CoOpt_Singletons(normal) ghc/alloc    721,544,088    692,174,216  -4.1% GOOD
       LargeRecord(normal) ghc/alloc  1,268,031,157  1,265,168,448  -0.2%
            T14766(normal) ghc/alloc    918,218,533    688,432,296 -25.0% GOOD
            T15703(normal) ghc/alloc    318,103,629    306,638,016  -3.6% GOOD
            T17836(normal) ghc/alloc    419,174,584    418,400,824  -0.2%
            T18478(normal) ghc/alloc    471,042,976    470,261,376  -0.2%
            T20261(normal) ghc/alloc    573,387,162    563,663,336  -1.7%
            T24984(normal) ghc/alloc     87,832,666     87,636,168  -0.2%
            T25196(optasm) ghc/alloc  1,103,284,040  1,101,376,992  -0.2%
    hard_hole_fits(normal) ghc/alloc    224,981,413    224,608,208  -0.2%
  
                 geo. mean                                          -0.3%
                 minimum                                           -25.0%
                 maximum                                            +0.1%
  
  Metric Decrease:
      CoOpt_Singletons
      T14766
      T15703
  

• 30341168
  by Simon Peyton Jones at 2026-01-08T13:31:38-05:00

  Add regression test for #24867
  

• 1ac1a541
  by Julian Ospald at 2026-01-09T02:48:53-05:00

  Support statically linking executables properly
  
  Fixes #26434
  
  In detail, this does a number of things:
  * Makes GHC aware of 'extra-libraries-static' (this changes the package
    database format).
  * Adds a switch '-static-external' that will honour 'extra-libraries-static'
    to link external system dependencies statically.
  * Adds a new field to settings/targets: "ld supports verbatim namespace".
    This field is used by '-static-external' to conditionally use '-l:foo.a'
    syntax during linking, which is more robust than trying to find the
    absolute path to an archive on our own.
  * Adds a switch '-fully-static' that is meant as a high-level interface
    for e.g. cabal. This also honours 'extra-libraries-static'.
  
  This also attempts to clean up the confusion around library search directories.
  At the moment, we have 3 types of directories in the package database
  format:
  * library-dirs
  * library-dirs-static
  * dynamic-library-dirs
  
  However, we only have two types of linking: dynamic or static. Given the
  existing logic in 'mungeDynLibFields', this patch assumes that
  'library-dirs' is really just nothing but a fallback and always
  prefers the more specific variants if they exist and are non-empty.
  
  Conceptually, we should be ok with even just one search dirs variant.
  Haskell libraries are named differently depending on whether they're
  static or dynamic, so GHC can conveniently pick the right one depending
  on the linking needs. That means we don't really need to play tricks
  with search paths to convince the compiler to do linking as we want it.
  For system C libraries, the convention has been anyway to place static and
  dynamic libs next to each other, so we need to deal with that issue
  anyway and it is outside of our control. But this is out of the scope
  of this patch.
  
  This patch is backwards compatible with cabal. Cabal should however
  be patched to use the new '-fully-static' switch.
  

• ad3c808d
  by Julian Ospald at 2026-01-09T02:48:53-05:00

  Warn when "-dynamic" is mixed with "-staticlib"
  

• 322dd672
  by Matthew Pickering at 2026-01-09T02:49:35-05:00

  rts: Use INFO_TABLE_CONSTR for stg_dummy_ret_closure
  
  Since the closure type is CONSTR_NOCAF, we need to use INFO_TABLE_CONSTR
  to populate the constructor description field (this crashes ghc-debug
  when decoding AP_STACK frames sometimes)
  
  Fixes #26745
  

• 039bac4c
  by Ben Gamari at 2026-01-09T20:22:16-05:00

  ghc-internal: Move STM utilities out of GHC.Internal.Conc.Sync
  
  This is necessary to avoid an import cycle on Windows when importing
  `GHC.Internal.Exception.Context` in `GHC.Internal.Conc.Sync`.
  
  On the road to address #25365.
  

• 8c389e8c
  by Ben Gamari at 2026-01-09T20:22:16-05:00

  base: Capture backtrace from throwSTM
  
  Implements core-libraries-committee#297.
  
  Fixes #25365.
  

• e1ce1fc3
  by Ben Gamari at 2026-01-09T20:22:16-05:00

  base: Annotate rethrown exceptions in catchSTM with WhileHandling
  
  Implements core-libraries-committee#298
  

• c4ebdbdf
  by Cheng Shao at 2026-01-09T20:23:06-05:00

  compiler: make getPrim eagerly evaluate its result
  
  This commit makes `GHC.Utils.Binary.getPrim` eagerly evaluate its
  result, to avoid accidental laziness when future patches build other
  binary parsers using `getPrim`.
  

• 66a0c4f7
  by Cheng Shao at 2026-01-09T20:23:06-05:00

  compiler: implement fast get/put for Word16/Word32/Word64
  
  Previously, `GHC.Utils.Binary` contains `get`/`put` functions for
  `Word16`/`Word32`/`Word64` which always loads and stores them as
  big-endian words at a potentially unaligned address. The previous
  implementation is based on loads/stores of individual bytes and
  concatenating bytes with bitwise operations, which currently cannot be
  fused to a single load/store operation by GHC.
  
  This patch implements fast `get`/`put` functions for
  `Word16`/`Word32`/`Word64` based on a single memory load/store, with
  an additional `byteSwap` operation on little-endian hosts. It is based
  on unaligned load/store primops added since GHC 9.10, and we already
  require booting with at least 9.10, so it's about time to switch to
  this faster path.
  

• 641ec3f0
  by Simon Peyton Jones at 2026-01-09T20:23:55-05:00

  Fix scoping errors in specialisation
  
  Using -fspecialise-aggressively in #26682 showed up a couple of
  subtle errors in the type-class specialiser.
  
  * dumpBindUDs failed to call `deleteCallsMentioning`, resulting in a
    call that mentioned a dictionary that was not in scope.  This call
    has been missing since 2009!
      commit c43c981705ec33da92a9ce91eb90f2ecf00be9fe
      Author: Simon Peyton Jones <simonpj@microsoft.com>
      Date:   Fri Oct 23 16:15:51 2009 +0000
  
    Fixed by re-combining `dumpBindUDs` and `dumpUDs`.
  
  * I think there was another bug involving the quantified type
    variables in polymorphic specialisation. In any case I refactored
    `specHeader` and `spec_call` so that the former looks for the
    extra quantified type variables rather than the latter.  This
    is quite a worthwhile simplification: less code, easier to grok.
  
  Test case in simplCore/should_compile/T26682,
  brilliantly minimised by @sheaf.
  

• 2433e91d
  by Cheng Shao at 2026-01-09T20:24:43-05:00

  compiler: change sectionProtection to take SectionType argument
  
  This commit changes `sectionProtection` to only take `SectionType`
  argument instead of whole `Section`, since it doesn't need the Cmm
  section content anyway, and it can then be called in parts of NCG
  where we only have a `SectionType` in scope.
  

• e5926fbe
  by Cheng Shao at 2026-01-09T20:24:43-05:00

  compiler: change isInitOrFiniSection to take SectionType argument
  
  This commit changes `isInitOrFiniSection` to only take `SectionType`
  argument instead of whole `Section`, since it doesn't need the Cmm
  section content anyway, and it can then be called in parts of NCG
  where we only have a `SectionType` in scope. Also marks it as
  exported.
  

• 244d57d7
  by Cheng Shao at 2026-01-09T20:24:43-05:00

  compiler: fix split sections on windows
  
  This patch fixes split sections on windows by emitting the right
  COMDAT section header in NCG, see added comment for more explanation.
  Fix #26696 #26494.
  
  -------------------------
  Metric Decrease:
      LargeRecord
      T9675
      size_hello_artifact
      size_hello_artifact_gzip
      size_hello_unicode
      size_hello_unicode_gzip
  Metric Increase:
      T13035
  -------------------------
  
  Co-authored-by: Codex <codex@openai.com>
  

• 182f3d0f
  by Cheng Shao at 2026-01-09T20:25:28-05:00

  iserv: add comment about -fkeep-cafs
  

• 49675b69
  by Matthew Craven at 2026-01-09T20:26:14-05:00

  Account for "stupid theta" in demand sig for DataCon wrappers
  
  Fixes #26748.
  

• f3c18890
  by Samuel Thibault at 2026-01-10T15:48:22+01:00

  hurd: Fix getExecutablePath build
  
  3939a8bf93e27 ("GNU/Hurd: Add getExecutablePath support") added using
  /proc/self/exe for GNU/Hurd but missed adding the required imports for
  the corresponding code.
  

• 7f15bd15
  by Samuel Thibault at 2026-01-12T07:16:25-05:00

  Fix the OS string encoding for GNU/Hurd
  
  Following https://github.com/haskell/cabal/pull/9434/files , and as seen
  in the various gnu_HOST_OS usages in the source code, it is expected that
  GNU/Hurd is advertised as "gnu", like the autotools do.
  

• 1db2f240
  by Andrew Lelechenko at 2026-01-12T07:17:06-05:00

  Add since annotation for Data.Bifoldable1
  
  Fixes #26432
  

• e038a383
  by Sven Tennie at 2026-01-12T07:17:49-05:00

  Ignore Windows CI tool directories in Git
  
  Otherwise, we see thousands of changes in `git status` which is very
  confusing to work with.
  

• 023c301c
  by sheaf at 2026-01-13T04:57:30-05:00

  Don't re-use stack slots for growing registers
  
  This commit avoids re-using a stack slot for a register that has grown
  but already had a stack slot.
  
  For example, suppose we have stack slot assigments
  
    %v1 :: FF64 |-> StackSlot 0
    %v2 :: FF64 |-> StackSlot 1
  
  Later, we start using %v1 at a larger format (e.g. F64x2) and we need
  to spill it again. Then we **must not** use StackSlot 0, as a spill
  at format F64x2 would clobber the data in StackSlot 1.
  
  This can cause some fragmentation of the `StackMap`, but that's probably
  OK.
  
  Fixes #26668
  

• d0966e64
  by fendor at 2026-01-13T04:58:11-05:00

  Remove `traceId` from ghc-pkg executable
  

• 20d7efec
  by Simon Peyton Jones at 2026-01-13T12:41:22-05:00

  Make SpecContr rules fire a bit later
  
  See #26615 and Note [SpecConstr rule activation]
  

• 8bc4eb8c
  by Andrew Lelechenko at 2026-01-13T12:42:03-05:00

  Upgrade mtl submodule to 2.3.2
  
  Fixes #26656
  

• c94aaacd
  by Cheng Shao at 2026-01-13T12:42:44-05:00

  compiler: remove iserv and only use on-demand external interpreter
  
  This patch removes `iserv` from the tree completely. Hadrian would no
  longer build or distribute `iserv`, and the GHC driver would use the
  on-demand external interpreter by default when invoked with
  `-fexternal-interpreter`, without needing to specify `-pgmi ""`. This
  has multiple benefits:
  
  - It allows cleanup of a lot of legacy hacks in the hadrian codebase.
  - It paves the way for running cross ghc's iserv via cross emulator
    (#25523), fixing TH/ghci support for cross targets other than
    wasm/js.
  

• c1fe0097
  by Peter Trommler at 2026-01-14T03:54:49-05:00

  PPC NCG: Fix shift right MO code
  
  The shift amount in shift right [arithmetic] MOs is machine word
  width. Therefore remove unnecessary zero- or sign-extending of
  shift amount.
  
  It looks harmless to extend the shift amount argument because the
  shift right instruction uses only the seven lowest bits (i. e. mod 128).
  But now we have a conversion operation from a smaller type to word width
  around a memory load at word width. The types are not matching up but
  there is no check done in CodeGen. The necessary conversion from word
  width down to the smaller width would be translated into a no-op on
  PowerPC anyway. So all seems harmless if it was not for a small
  optimisation in getRegister'.
  
  In getRegister' a load instruction with the smaller width of the
  conversion operation was generated. This loaded the most significant
  bits of the word in memory on a big-endian platform. These bits were
  zero and hence shift right was used with shift amount zero and not one
  as required in test Sized.
  
  Fixes #26519
  

• 2dafc65a
  by Cheng Shao at 2026-01-14T03:55:31-05:00

  Tree-wide cleanup of cygwin logic
  
  GHC has not supported cygwin for quite a few years already, and will
  not resume support in the forseeable future. The only supported
  windows toolchain is clang64/clangarm64 of the msys2 project. This
  patch cleans up the unused cygwin logic in the tree.
  
  Co-authored-by: Codex <codex@openai.com>
  

• 66b96e2a
  by Teo Camarasu at 2026-01-14T03:56:13-05:00

  Set default eventlog-flush-interval to 5s
  
  Resolves #26707
  

• d0254579
  by Andrew Lelechenko at 2026-01-14T03:56:53-05:00

  Document when -maxN RTS option was added
  

• f25e2b12
  by Cheng Shao at 2026-01-14T11:10:39-05:00

  testsuite: remove obsolete --ci option from the testsuite driver
  
  This patch removes the obsolete `--ci` option from the testsuite
  driver: neither the CI scripts nor hadrian ever invokes the testsuite
  driver with `--ci`, and the perf notes are always fetched to the
  `refs/notes/perf` local reference anyway.
  

• 7964763b
  by Julian Ospald at 2026-01-14T11:11:31-05:00

  Fix fetch_cabal
  
  * download cabal if the existing one is of an older version
  * fix FreeBSD download url
  * fix unpacking on FreeBSD
  

• 6b0129c1
  by Julian Ospald at 2026-01-14T11:11:31-05:00

  Bump toolchain in CI
  

• 0f53ccc6
  by Julian Ospald at 2026-01-14T11:11:31-05:00

  Use libffi-clib
  
  Previously, we would build libffi via hadrian
  and bundle it manually with the GHC bindist.
  
  This now moves all that logic out of hadrian
  and allows us to have a clean Haskell package
  to build and link against and ship it without
  extra logic.
  
  This patch still retains the ability to link
  against a system libffi.
  
  The main reason of bundling libffi was that on
  some platforms (e.g. FreeBSD and Mac), system libffi
  is not visible to the C toolchain by default,
  so users would require settings in e.g. cabal
  to be able to compile anything.
  
  This adds the submodule libffi-clib to the repository.
  

• 5e1cd595
  by Peng Fan at 2026-01-14T11:12:26-05:00

  NCG/LA64: add support for la664 micro architecture
  
  Add '-mla664' flag to LA664, which has some new features:
  atomic instructions, dbar hints, etc.
  
  'LA464' is the default so that unrecognized instructions are not
  generated.
  

• c56567ec
  by Simon Peyton Jones at 2026-01-15T23:19:04+00:00

  Add evals for strict data-con args in worker-functions
  
  This fixes #26722, by adding an eval in a worker for
  arguments of strict data constructors, even if the
  function body uses them strictly.
  
  See (WIS1) in Note [Which Ids should be strictified]
  
  I took the opportunity to make substantial improvements in the
  documentation for call-by-value functions.  See especially
     Note [CBV Function Ids: overview] in GHC.Types.Id.Info
     Note [Which Ids should be CBV candidates?] ditto
     Note [EPT enforcement] in GHC.Stg.EnforceEpt
  among others.
  

• 9719ce5d
  by Simon Peyton Jones at 2026-01-15T23:19:04+00:00

  Improve `interestingArg`
  
  This function analyses a function's argument to see if it is
  interesting enough to deserve an inlining discount. Improvements
  for
    * LitRubbish arguments
    * exprIsExpandable arguments
  
  See Note [Interesting arguments] which is substantially rewritten.
  

• 7b616b9f
  by Cheng Shao at 2026-01-16T06:45:00-05:00

  compiler: fix regression when compiling foreign stubs in the rts unit
  
  This patch fixes a regression when compiling foreign stubs in the rts
  unit introduced in 05e25647f72bc102061af3f20478aa72bff6ff6e. A simple
  revert would fix it, but it's better to implement a proper fix with
  comment for better understanding of the underlying problem, see the
  added comment for explanation.
  
  Co-authored-by: Codex <codex@openai.com>
  

• c343ef64
  by Sylvain Henry at 2026-01-16T06:45:51-05:00

  base: remove GHC.JS.Prim.Internal.Build (#23432)
  
  See accepted CLC proposal https://github.com/haskell/core-libraries-committee/issues/329
  

• 29c0aceb
  by Simon Peyton Jones at 2026-01-16T17:18:11-05:00

  Improve newtype unwrapping
  
  Ticket #26746 describes several relatively-minor shortcomings of newtype
  unwrapping.  This MR addresses them, while also (arguably) simplifying
  the code a bit.
  
  See new Note [Solving newtype equalities: overview]
  and     Note [Decomposing newtype equalities]
  and     Note [Eager newtype decomposition]
  and     Note [Even more eager newtype decomposition]
  
  For some reason, on Windows only, runtime allocations decrease for test
  T5205 (from 52k to 48k).  I have not idea why. No change at all on Linux.
  I'm just going to accept the change.  (I saw this same effect in another
  MR so I think it's a fault in the baseline.)
  
  Metric Decrease:
      T5205
  

• 8b59e62c
  by Andreas Klebinger at 2026-01-16T17:18:52-05:00

  testsuite: Widen acceptance window for T5205.
  
  Fixes #26782
  

• 9e5e0234
  by mangoiv at 2026-01-17T06:03:03-05:00

  add a new issue template for getting verified
  
  To reduce spam created by new users, we will in future not grant
  any rights but reporting issues to new users. That is why we will
  have to be able to verify them. The added issue template serves that
  purpose.
  

• b18b2c42
  by Cheng Shao at 2026-01-17T06:03:44-05:00

  llvm: fix split sections for llvm backend
  
  This patch fixes split sections for llvm backend:
  
  - Pass missing `--data-sections`/`--function-sections` flags to
    llc/opt.
  - Use `@llvm.compiler.used` instead of `@llvm.used` to avoid sections
    being unnecessarily retained at link-time.
  
  Fixes #26770.
  
  -------------------------
  Metric Decrease:
      libdir
      size_hello_artifact
      size_hello_unicode
  -------------------------
  
  Co-authored-by: Codex <codex@openai.com>
  

• ebf66f67
  by Cheng Shao at 2026-01-17T13:16:50-05:00

  Update autoconf scripts
  
  Scripts taken from autoconf a2287c3041a3f2a204eb942e09c015eab00dc7dd
  

• 598624b9
  by Andreas Klebinger at 2026-01-17T13:17:32-05:00

  CString.hs: Update incorrect comment.
  
  Fixes #26322
  

• eea2036b
  by Cheng Shao at 2026-01-18T10:00:49-05:00

  libraries: bump haskeline submodule to 0.8.4.1
  
  This patch bumps the haskeline submodule to 0.8.4.1 which includes an
  important fix for an ANSI handling bug on Windows
  (https://github.com/haskell/haskeline/pull/126).
  

• 87d8f6c2
  by Cheng Shao at 2026-01-18T10:01:30-05:00

  hadrian: replace default -H32m/-H64m with -O64M to improve mutator productivity
  
  Most hadrian build flavours pass `-H32m`/`-H64m` to GHC as
  conventional wisdom to improve mutator productivity and reduce GC
  overhead. They were inherited from the legacy Make build system, and
  there used to be make flags to instrument a build process with
  `-Rghc-timing` option to collect GC stats of each GHC run from stderr.
  
  It's time to revisit whether there are better defaults for
  `-H32m`/`-H64m`, and this patch changes it to `-O64M` which indeed
  improves mutator productivity based on real statistics. `-O64M` is
  more aggressive than `-H64m`; it allows the old generation to grow to
  at least 64M before triggering major GC and reduces major GC runs.
  
  The stats of a clean build with `validate` flavour and `-H64m`:
  
  ```
  h64m.log
    matched RTS stat lines: 5499
    sum MUT cpu     : 2400.808 s
    sum GC cpu      : 1378.292 s
    sum MUT elapsed : 2788.253 s
    sum GC elapsed  : 1389.233 s
    GC/MUT cpu ratio     : 0.574 (GC is 57.4% of MUT)
    GC/MUT elapsed ratio : 0.498 (GC is 49.8% of MUT)
    GC fraction of (MUT+GC) cpu     : 36.5%
    GC fraction of (MUT+GC) elapsed : 33.3%
    per-line GC/MUT cpu ratio: median 0.691, p90 1.777
    per-line GC/MUT elapsed ratio: median 0.519, p90 1.081
  ```
  
  The stats of a clean build with `validate` flavour and `-O64M`:
  
  ```
  o64m.log
    matched RTS stat lines: 5499
    sum MUT cpu     : 2377.383 s
    sum GC cpu      : 1127.146 s
    sum MUT elapsed : 2758.857 s
    sum GC elapsed  : 1135.587 s
    GC/MUT cpu ratio     : 0.474 (GC is 47.4% of MUT)
    GC/MUT elapsed ratio : 0.412 (GC is 41.2% of MUT)
    GC fraction of (MUT+GC) cpu     : 32.2%
    GC fraction of (MUT+GC) elapsed : 29.2%
    per-line GC/MUT cpu ratio: median 0.489, p90 1.099
    per-line GC/MUT elapsed ratio: median 0.367, p90 0.806
  ```
  
  Mutator time is roughly in the same ballpark, but GC CPU time has
  reduced by 18.22%, and mutator productivity has increased from 63.5%
  to 67.8%.
  

• 8372e13d
  by Cheng Shao at 2026-01-18T10:02:12-05:00

  rts: remove unused .def files from rts/win32
  
  This patch removes unused .def files from `rts/win32`, given we don't
  build .dll files for rts/ghc-internal/ghc-prim at all. Even when we
  resurrect win32 dll support at some point in the future, these .def
  files still contain incorrect symbols anyway and won't be of any use.
  

• f6af485d
  by Cheng Shao at 2026-01-18T10:03:19-05:00

  .gitmodules: use gitlab mirror for the libffi-clib submodule
  
  This patch fixes .gitmodules to use the gitlab mirror for the
  libffi-clib submodule, to make it coherent with other submodules that
  allow ghc developers to experiment with wip branches in submodules for
  ghc patches. Fixes #26783.
  

• 41432d25
  by Cheng Shao at 2026-01-18T10:05:13-05:00

  hadrian: remove the horrible i386 speedHack
  
  When hadrian builds certain rts objects for i386, there's a horrible
  speedHack that forces -fno-PIC even for dynamic ways of those objects.
  This is not compatible with newer versions of gcc/binutils as well as
  clang/lld, and this patch removes it. Fixes #26792.
  

• 323eb8f0
  by Cheng Shao at 2026-01-18T21:48:19-05:00

  hadrian: enable split sections for cross stage0
  
  This patch fixes a minor issue with `splitSectionsArgs` in hadrian:
  previously, it's unconditionally disabled for stage0 libraries because
  it's not going to be shipped in the final bindists. But it's only true
  when not cross compiling. So for now we also need to enable it for
  cross stage0 as well.
  

• 3fadfefe
  by Andreas Klebinger at 2026-01-18T21:49:01-05:00

  RTS: Document -K behaviour better
  

• 30f442a9
  by Teo Camarasu at 2026-01-20T13:57:26-05:00

  base: don't expose GHC.Num.{BigNat, Integer, Natural}
  
  We no longer expose GHC.Num.{BigNat, Integer, Natural} from base instead users should get these modules from ghc-bignum.
  We make this change to insulate end users from changes to GHC's implementation of big numbers.
  Implements CLC proposal 359: https://github.com/haskell/core-libraries-committee/issues/359
  

• 75a9053d
  by Teo Camarasu at 2026-01-20T13:58:07-05:00

  base: deprecate GHC internals in GHC.Num
  
  Implements CLC proposal: https://github.com/haskell/core-libraries-committee/issues/360
  

• 9534b032
  by Andreas Klebinger at 2026-01-20T13:58:50-05:00

  ghc-experimental: Update Changelog
  
  I tried to reconstruct a high level overview of the changes and when
  they were made since we introduced it.
  
  Fixes #26506
  
  Co-authored-by: Teo Camarasu <teofilcamarasu@gmail.com>
  

• 346f2f5a
  by Cheng Shao at 2026-01-20T13:59:30-05:00

  hadrian: remove RTS options in ghc-in-ghci flavour
  
  This patch removes the RTS options passed to ghc in ghc-in-ghci
  flavour, to workaround command line argument handling issue in
  hls/hie-boot that results in `-O64M` instead of `+RTS -O64M -RTS`
  being passed to ghc. It's not a hadrian bug per se, since ghc's own
  ghc-in-ghci multi repl works fine, but we should still make sure HLS
  works. Closes #26801.
  

• 759fd15a
  by Andreas Klebinger at 2026-01-21T16:05:28-05:00

  Don't build GHC with -Wcompat
  
  Without bumping the boot compiler the warnings it produces are often not
  actionable leading to pointless noise.
  
  Fixes #26800
  

• 3172db94
  by Torsten Schmits at 2026-01-21T16:06:11-05:00

  Use the correct field of ModOrigin when formatting error message listing hidden reexports
  

• 485c12b2
  by Cheng Shao at 2026-01-21T16:06:54-05:00

  Revert "hadrian: handle findExecutable "" gracefully"
  
  This reverts commit 1e5752f64a522c4025365856d92f78073a7b3bba. The
  underlying issue has been fixed in
  https://github.com/haskell/directory/commit/75828696e7145adc09179111a0d631b9a09963a4
  and present since 1.3.9.0, and hadrian directory lower bound is
  1.3.9.0, so we can revert our own in house hack now.
  

• 5efb58dc
  by Cheng Shao at 2026-01-21T16:07:36-05:00

  rts: fix typo in TICK_ALLOC_RTS
  
  This patch fixes a typo in the `TICK_ALLOC_RTS` macro, the original
  `bytes` argument was silently dropped. The Cmm code has its own
  version of `TICK_ALLOC_RTS` not affected by this typo, it affected the
  C RTS, and went unnoticed because the variable `n` happened to also be
  available at its call site. But the number was incorrect. Also fixes
  its call site since `WDS()` is not available in C.
  

• c406ea69
  by Cheng Shao at 2026-01-21T16:07:36-05:00

  rts: remove broken & unused ALLOC_P_TICKY
  
  This patch removes the `ALLOC_P_TICKY` macro from the rts, it's
  unused, and its expanded code is already broken.
  

• 34a27e20
  by Simon Peyton Jones at 2026-01-21T16:08:17-05:00

  Make the implicit-parameter class have representational role
  
  This MR addresses #26737, by making the built-in class IP
  have a representational role for its second parameter.
  
  See Note [IP: implicit parameter class] in
    ghc-internal:GHC.Internal.Classes.IP
  
  In fact, IP is (unfortunately, currently) exposed by
  base:GHC.Base, so we ran a quick CLC proposal to
  agree the change:
    https://github.com/haskell/core-libraries-committee/issues/385
  
  Some (small) compilations get faster because they only need to
  load (small) interface file GHC.Internal.Classes.IP.hi,
  rather than (large) GHC.Internal.Classes.hi.
  
  Metric Decrease:
      T10421
      T12150
      T12425
      T24582
      T5837
      T5030
  

• ca79475f
  by Cheng Shao at 2026-01-21T16:09:00-05:00

  testsuite: avoid re.sub in favor of simple string replacements
  
  This patch refactors the testsuite driver and avoids the usage of
  re.sub in favor of simple string replacements when possible. The
  changes are not comprehensive, and there are still a lot of re.sub
  usages lingering around the tree, but this already addresses a major
  performance bottleneck in the testsuite driver that might has to do
  with quadratic or worse slowdown in cpython's regular expression
  engine when handling certain regex patterns with large strings.
  Especially on i386, and i386 jobs are the bottlenecks of all full-ci
  validate pipelines!
  
  Here are the elapsed times of testing x86_64/i386 with -j48 before
  this patch:
  
  x86_64: `Build completed in 6m06s`
  i386: `Build completed in 1h36m`
  
  And with this patch:
  
  x86_64: `Build completed in 4m55s`
  i386: `Build completed in 4m23s`
  
  Fixes #26786.
  
  Co-authored-by: Codex <codex@openai.com>
  

• 88c93796
  by Zubin Duggal at 2026-01-21T16:09:42-05:00

  ghc-toolchain: Also configure windres on non-windows platforms.
  It may be needed for cross compilation.
  
  Fixes #24588
  

• 9788c0ec
  by Cheng Shao at 2026-01-21T16:10:24-05:00

  ghci: print external interpreter trace messages to stderr instead of stdout
  
  This patch makes ghci print external interpreter trace messages to
  stderr instead of stdout, which is a much saner choice for diagnostic
  information. Closes #26807.
  

• 0491f08a
  by Sylvain Henry at 2026-01-22T03:44:26-05:00

  GC: don't use CAS without PARALLEL_GC on
  
  If we're not using the parallel GC, there is no reason to do a costly
  CAS. This was flagged as taking time in a perf profile.
  

• 211a8f56
  by Sylvain Henry at 2026-01-22T03:44:26-05:00

  GC: suffix parallel GC with "par" instead of "thr"
  
  Avoid some potential confusion (see discussion in !15351).
  

• 77a23cbd
  by fendor at 2026-01-22T03:45:08-05:00

  Remove blanket ignore that covers libraries/
  

• 18bf7f5c
  by Léana Jiang at 2026-01-22T08:58:45-05:00

  doc: update Flavour type in hadrian user-settings
  

• 3d5a1365
  by Cheng Shao at 2026-01-22T08:59:28-05:00

  hadrian: add missing notCross predicate for stage0 -O0
  
  There are a few hard-coded hadrian args that pass -O0 when compiling
  some heavy modules in stage0, which only makes sense when not
  cross-compiling and when cross-compiling we need properly optimized
  stage0 packages. So this patch adds the missing `notCross` predicate
  in those places.
  

• ee937134
  by Matthew Pickering at 2026-01-22T09:00:10-05:00

  Fix ghc-experimental GHC.Exception.Backtrace.Experimental module
  
  This module wasn't added to the cabal file so it was never compiled or
  included in the library.
  

• 1b490f5a
  by Zubin Duggal at 2026-01-22T09:00:53-05:00

  hadrian: Add ghc-{experimental,internal}.cabal to the list of dependencies of the doc target
  We need these files to detect the version of these libraries
  
  Fixes #26738
  

• cdb74049
  by Cheng Shao at 2026-01-22T14:52:36-05:00

  rts: avoid Cmm loop to initialize Array#/SmallArray#
  
  Previously, `newArray#`/`newSmallArray#` called an RTS C function to
  allocate the `Array#`/`SmallArray#`, then used a Cmm loop to
  initialize the elements. Cmm doesn't have native for-loop so the code
  is a bit awkward, and it's less efficient than a C loop, since the C
  compiler can effectively vectorize the loop with optimizations.
  
  So this patch moves the loop that initializes the elements to the C
  side. `allocateMutArrPtrs`/`allocateSmallMutArrPtrs` now takes a new
  `init` argument and initializes the elements if `init` is non-NULL.
  

• 4c784f00
  by Cheng Shao at 2026-01-22T14:53:19-05:00

  Fix testsuite run for +ipe flavour transformer
  
  This patch makes the +ipe flavour transformer pass the entire
  testsuite:
  
  - An RTS debug option `-DI` is added, the IPE trace information is now
    only printed with `-DI`. The test cases that do require IPE trace
    are now run with `-DI`.
  - The testsuite config option `ghc_with_ipe` is added, enabled when
    running the testsuite with `+ipe`, which skips a few tests that are
    sensitive to eventlog output, allocation patterns etc that can fail
    under `+ipe`.
  
  This is the first step towards #26799.
  
  Co-authored-by: Codex <codex@openai.com>
  

• be8e5236
  by Ben Gamari at 2026-01-23T03:28:45-05:00

  hadrian: Bump QuickCheck upper bound
  
  This patch bumps QuickCheck upper bound to 2.18. selftest rule
  manually tested to work with current latest QuickCheck-2.17.1.0.
  

• 5aa328fb
  by Zubin Duggal at 2026-01-23T03:29:30-05:00

  Add genindex to index.rst. This adds a link to the index in the navigation bar.
  
  Fixes #26437
  

• 917ab8ff
  by Oleg Grenrus at 2026-01-23T10:52:55-05:00

  Export labelThread from Control.Concurrent
  

• 3f5e8d80
  by Cheng Shao at 2026-01-23T10:53:37-05:00

  ci: only push perf notes on master/release branches
  
  This patch fixes push_perf_notes logic in ci.sh to only push perf
  notes on master/release branches. We used to unconditionally push perf
  notes even in MRs, but the perf numbers in the wip branches wouldn't
  be used as baseline anyway, plus this is causing a space leak in the
  ghc-performance-notes repo. See #25317 for the perf notes repo size
  problem.
  
  Co-authored-by: Codex <codex@openai.com>
  

• 414b9593
  by Cheng Shao at 2026-01-24T07:11:51-05:00

  ci: remove duplicate keys in .gitlab-ci.yml
  
  This patch removes accidentally duplicate keys in `.gitlab-ci.yml`.
  The YAML spec doesn't allow duplicate keys in the first place, and
  according to GitLab docs
  (https://docs.gitlab.com/ci/yaml/yaml_optimization/#anchors), the
  latest key overrides the earlier entries.
  

• e5cb5491
  by Cheng Shao at 2026-01-24T07:12:34-05:00

  hadrian: drop obsolete configure/make builder logic for libffi
  
  This patch drops obsolete hadrian logic around `Configure
  libffiPath`/`Make libffiPath` builders, they are no longer needed
  after libffi-clib has landed. Closes #26815.
  

• 2d160222
  by Simon Hengel at 2026-01-24T07:13:17-05:00

  Fix typo in roles.rst

• 56db94f7
  by Peter Trommler at 2026-01-26T11:26:18+01:00

  PPC NCG: Generate clear right insn at arch width
  
  The clear right immediate (clrrxi) is only available in word and
  doubleword width. Generate clrrxi instructions at architecture
  width for all MachOp widths.
  
  Fixes #24145
  

• 5957a8ad
  by Wolfgang Jeltsch at 2026-01-27T06:11:40-05:00

  Add operations for obtaining operating-system handles
  
  This contribution implements CLC proposal #369. It adds operations for
  obtaining POSIX file descriptors and Windows handles that underlie
  Haskell handles. Those operating system handles can also be obtained
  without such additional operations, but this is more involved and, more
  importantly, requires using internals.
  

• 86a0510c
  by Greg Steuck at 2026-01-27T06:12:34-05:00

  Move flags to precede patterns for grep and read files directly
  
  This makes the tests pass with non-GNU (i.e. POSIX-complicant) tools.
  There's no reason to use cat and pipe where direct file argument works.
  

• 50761451
  by Cheng Shao at 2026-01-27T21:51:23-05:00

  ci: update darwin boot ghc to 9.10.3
  
  This patch updates darwin boot ghc to 9.10.3, along with other related
  updates, and pays off some technical debt here:
  
  - Update `nixpkgs` and use the `nixpkgs-25.05-darwin` channel.
  - Update the `niv` template.
  - Update LLVM to 21 and update `llvm-targets` to reflect LLVM 21
    layout changes for arm64/x86_64 darwin targets.
  - Use `stdenvNoCC` to prevent nix packaged apple sdk from being used
    by boot ghc, and manually set `DEVELOPER_DIR`/`SDKROOT` to enforce
    the usage of system-wide command line sdk for macos.
  - When building nix derivation for boot ghc, run `configure` via the
    `arch` command so that `configure` and its subprocesses pick up the
    manually specified architecture.
  - Remove the previous horrible hack that obliterates `configure` to
    make autoconf test result in true. `configure` now properly does its
    job.
  - Remove the now obsolete configure args and post install settings
    file patching logic.
  - Use `scheme-small` for texlive to avoid build failures in certain
    unused texlive packages, especially on x86_64-darwin.
  

• 94dcd15e
  by Matthew Pickering at 2026-01-27T21:52:05-05:00

  Evaluate backtraces for "error" exceptions at the moment they are thrown
  
  See Note [Capturing the backtrace in throw] and
  Note [Hiding precise exception signature in throw] which explain the
  implementation.
  
  This commit makes `error` and `throw` behave the same with regard to
  backtraces. Previously, exceptions raised by `error` would not contain
  useful IPE backtraces.
  
  I did try and implement `error` in terms of `throw` but it started to
  involve putting diverging functions into hs-boot files, which seemed to
  risky if the compiler wouldn't be able to see if applying a function
  would diverge.
  
  CLC proposal: https://github.com/haskell/core-libraries-committee/issues/383
  
  Fixes #26751
  

• ef35e3ea
  by Teo Camarasu at 2026-01-27T21:52:46-05:00

  ghc-internal: move all Data instances to Data.Data
  
  Most instances of Data are defined in GHC.Internal.Data.Data.
  Let's move all remaining instance there.
  
  This moves other modules down in the dependency hierarchy allowing for
  more parallelism, and it decreases the likelihood that we would need to
  load this heavy .hi file if we don't actually need it.
  
  Resolves #26830
  
  Metric Decrease:
      T12227
      T16875
  

• 5e0ec555
  by sheaf at 2026-01-28T06:56:38-05:00

  Add test case for #25679
  
  This commit adds the T25679 test case. The test now passes, thanks to
  commit 1e53277af36d3f0b6ad5491f70ffc5593a49dcfd.
  
  Fixes #25679
  

• f1cd1611
  by sheaf at 2026-01-28T06:56:38-05:00

  Improve defaulting of representational equalities
  
  This commit makes the defaulting of representational equalities, introduced
  in 1e53277a, a little bit more robust. Now, instead of calling the eager
  unifier, it calls the full-blown constraint solver, which means that it can
  handle some subtle situations, e.g. involving functional dependencies and
  type-family injectivity annotations, such as:
  
    type family F a = r | r -> a
    type instance F Int = Bool
  
    [W] F beta ~R Bool
  

• 25edf516
  by sheaf at 2026-01-28T06:56:38-05:00

  Improve errors for unsolved representational equalities
  
  This commit adds a new field of CtLoc, CtExplanations, which allows the
  typechecker to leave some information about what it has done. For the moment,
  it is only used to improve error messages for unsolved representational
  equalities. The typechecker will now accumulate, when unifying at
  representational role:
  
    - out-of-scope newtype constructors,
    - type constructors that have nominal role in a certain argument,
    - over-saturated type constructors,
    - AppTys, e.g. `c a ~R# c b`, to report that we must assume that 'c' has
      nominal role in its parameters,
    - data family applications that do not reduce, potentially preventing
      newtype unwrapping.
  
  Now, instead of having to re-construct the possible errors after the fact,
  we simply consult the CtExplanations field.
  
  Additionally, this commit modifies the typechecker error messages that
  concern out-of-scope newtype constructors. The error message now depends
  on whether we have an import suggestion to provide to the user:
  
    - If we have an import suggestion for the newtype constructor,
      the message will be of the form:
  
        The data constructor MkN of the newtype N is out of scope
        Suggested fix: add 'MkN' to the import list in the import of 'M'
  
    - If we don't have any import suggestions, the message will be
      of the form:
  
        NB: The type 'N' is an opaque newtype, whose constructor is hidden
  
  Fixes #15850, #20289, #20468, #23731, #25949, #26137
  

• 4d0e6da1
  by Simon Peyton Jones at 2026-01-28T06:57:19-05:00

  Fix two bugs in short-cut constraint solving
  
  There are two main changes here:
  
  * Use `isSolvedWC` rather than `isEmptyWC` in `tryShortCutSolver`
    The residual constraint may have some fully-solved, but
    still-there implications, and we don't want them to abort short
    cut solving!  That bug caused #26805.
  
  * In the short-cut solver, we abandon the fully-solved residual
    constraint; but we may thereby lose track of Givens that are
    needed, and either report them as redundant or prune evidence
    bindings that are in fact needed.
  
    This bug stopped the `constraints` package from compiling;
    see the trail in !15389.
  
  The second bug led me to (another) significant refactoring
  of the mechanism for tracking needed EvIds.   See the new
     Note [Tracking needed EvIds] in GHC.Tc.Solver.Solve
  It's simpler and much less head-scratchy now.
  
  Some particulars:
  
  * An EvBindsVar now tracks NeededEvIds
  
  * We deal with NeededEvIds for an implication only when it is
    fully solved.  Much simpler!
  
  * `tryShortCutTcS` now takes a `TcM WantedConstraints` rather than
    `TcM Bool`, so that is can plumb the needed EvIds correctly.
  
  * Remove `ic_need` and `ic_need_implic` from Implication (hooray),
    and add `ics_dm` and `ics_non_dm` to `IC_Solved`.
  
  Pure refactor
  * Shorten data constructor `CoercionHole` to `CH`, following
    general practice in GHC.
  * Rename `EvBindMap` to `EvBindsMap` for consistency
  

• 662480b7
  by Cheng Shao at 2026-01-28T06:58:00-05:00

  ci: use debian validate bindists instead of fedora release bindists in testing stage
  
  This patch changes the `abi-test`, `hadrian-multi` and `perf` jobs in
  the full-ci pipeline testing stage to use debian validate bindists
  instead of fedora release bindists, to increase pipeline level
  parallelism and allow full-ci pipelines to complete earlier. Closes #26818.
  

• 39581ec6
  by Cheng Shao at 2026-01-28T06:58:40-05:00

  ci: run perf test with -j$cores
  
  This patch makes the perf ci job compile Cabal with -j$cores to speed
  up the job.
  

• 607b287b
  by Wolfgang Jeltsch at 2026-01-28T15:41:53+02:00

  Remove `GHC.Desugar` from `base`
  
  `GHC.Desugar` was deprecated and should have been removed in GHC 9.14.
  However, the removal was forgotten, although there was a code block that
  was intended to trigger a compilation error when the GHC version in use
  was 9.14 or later. This code sadly didn’t work, because the
  `__GLASGOW_HASKELL__` macro was misspelled as `__GLASGOW_HASKELL`.
  

• e8f5a45d
  by sterni at 2026-01-29T04:19:18-05:00

  users_guide: fix runtime error during build with Sphinx 9.1.0
  
  Appears that pathto is stricter about what it accepts now.
  Tested Sphinx 8.2.3 and 9.1.0 on the ghc-9.10 branch.
  
  Resolves #26810.
  
  Co-authored-by: Martin Weinelt <hexa@darmstadt.ccc.de>
  

• ce2d62fb
  by Jessica Clarke at 2026-01-29T19:48:51-05:00

  PPC NCG: Use libcall for 64-bit cmpxchg on 32-bit PowerPC
  
  There is no native instruction for this, and even if there were a
  register pair version we could use, the implementation here is assuming
  the values fit in a single register, and we end up only using / defining
  the low halves of the registers.
  
  Fixes: b4d39adbb5 ("PrimOps: Add CAS op for all int sizes")
  Fixes: #23969
  

• 43d97761
  by Michael Karcher at 2026-01-29T19:49:43-05:00

  NCG for PPC: add pattern for CmmRegOff to iselExpr64
  
  Closes #26828

• aeeb4a20
  by Matthew Pickering at 2026-01-30T11:42:47-05:00

  determinism: Use deterministic map for Strings in TyLitMap
  
  When generating typeable evidence the types we need evidence for all
  cached in a TypeMap, the order terms are retrieved from a type map
  determines the order the bindings appear in the program.
  
  A TypeMap is quite diligent to use deterministic maps, apart from in the
  TyLitMap, which uses a UniqFM for storing strings, whose ordering
  depends on the Unique of the FastString.
  
  This can cause non-deterministic .hi and .o files.
  
  An unexpected side-effect is the error message but RecordDotSyntaxFail8
  changing. I looked into this with Sam and this change caused the
  constraints to be solved in a different order which results in a
  slightly different error message. I have accepted the new test, since
  the output before was non-deterministic and the new output is consistent
  with the other messages in that file.
  
  Fixes #26846
  

• 9e4d70c2
  by Andrew Lelechenko at 2026-01-30T11:43:29-05:00

  Upgrade text submodule to 2.1.4
  

• 631fa5ae
  by Recursion Ninja at 2026-01-31T22:30:11+00:00

  Decouple `L.S.H.Decls` from importing `GHC.Types.Basic`
  
  Data-types within `GHC.Types.Basic` which describe components of
  the AST are migrated to `Language.Haskell.Syntax.Basic`. Related
  function definitions are also moved.
  
  Types moved to L.H.S. because they are part of the AST:
    * TopLevelFlag
    * RuleName
  
  Types moved from L.H.S. to GHC.Hs. because they are not needed in the AST:
    * TyConFlavour
    * TypeOrData
    * NewOrData
  
  Migrated instances:
    * `Outputable` instances moved to in `GHC.Utils.Outputable`
    * `Binary` instance of `Boxity` moved to to `GHC.Utils.Binary`
    * Other `Binary` instances are orphans to be migrated later.
  
  The `OverlapMode` data-type is given a TTG extension point.
  The `OverlapFlag` data-type, which depends on `OverlapMode`,
  is updated to support `OverlapMode` with a GHC "pass" type paramerter.
  In order to avoid module import cycles, `OverlapMode` and `OverlapFlag`
  are migrated to new modules (no way around this).
  
    * Migrated `OverlapMode` to new module `Language.Haskell.Syntax.Overlap`
    * Migrated `OverlapFlag` to new module `GHC.Hs.Decls.Overlap`
  

• 9769cc03
  by Simon Hengel at 2026-02-01T04:21:03-05:00

  Update the documentation for MultiWayIf (fixes #25376)
  
  (so that it matches the implementation)
  

• 5fc9442a
  by Peter Trommler at 2026-02-01T04:21:44-05:00

  hadrian: Fix dependency generation for assembler
  
  Assembler files allow # for comments unless in column 1. A modern
  cpp for C treats those a preprocessor directives. We tell gcc that
  a .S file is assembler with cpp and not C.
  
  Fixes #26819
  

• 269c4087
  by Simon Peyton Jones at 2026-02-01T19:38:10-05:00

  Include current phase in the range for rule/unfoldings
  
  This MR fixes a bad loop in the compiler: #26826.
  
  The fix is to add (WAR2) to
     Note [What is active in the RHS of a RULE or unfolding?]
  in GHC.Core.Opt.Simplify.Utils
  

• ddf1434f
  by Vladislav Zavialov at 2026-02-01T19:38:52-05:00

  Refactor: merge HsMultilineString into HsString (#26860)
  
  Before this patch, HsLit defined two separate constructors to represent
  single-line and multi-line strings:
  
  	data HsLit x
  	  ...
  	  | HsString (XHsString x) FastString
  	  | HsMultilineString (XHsMultilineString x) FastString
  
  I found this to be an unnecessary complication and an obstacle to unifying
  HsLit with HsTyLit. Now we use HsString for both kinds of literals.
  
  One user-facing change here is `ppr (HsString st s)` behaving differently for
  single-line strings containing newlines:
  
  	x = "first line \
  	    \asdf\n\
  	    \second line"
  
  Previously, the literal was fed to `ftext` with its newlines, producing an
  ill-formed SDoc. This issue is now addressed by using `split` for both
  single-line and multi-line strings:
  
  	vcat $ map text $ split '\n' (unpackFS src)
  
  See the parser/should_fail/T26860ppr test.
  
  In addition (and unrelatedly to the main payload of this patch),
  drop the unused pmPprHsLit helper.
  

• 2b4f463c
  by Simon Peyton Jones at 2026-02-02T17:32:32+00:00

  Remove exprIsCheap from doFloatFromRhs
  
  See #26854 and Note [Float when expandable]
  
  This patch simplifies the code, by removing an extra unnecessary test.
  

• 9db7f21f
  by Brandon Chinn at 2026-02-03T09:15:10-05:00

  Refactor: make function patterns exhaustive
  
  Also added missing (==) logic for:
    * HsMultilineString
    * HsInt{8,16,32}
    * HsWord{8,16,32}
  

• aa9c5e2c
  by Hécate Kleidukos at 2026-02-03T15:58:35-05:00

  driver: Hide source paths at verbosity level 1 by default
  

• c64cca1e
  by mangoiv at 2026-02-03T15:59:29-05:00

  ExplicitLevelImports: check staging for types just like for values
  
  Previously, imported types were entirely exempted from staging checks as
  the implicit stage persistance assumed to be all imported types to be
  well staged. ExplicitLevelImports' change specification, however, does
  not do such an exemption. Thus we want to introduce such a check, just
  like we have for values.
  ExplicitLevelImports does not, however, talk about local names - from
  its perspective, we could theoretically keep treating locally introduced
  types specially - e.g. an ill-staged used in a quote would only emit a
  warning, not an error. To allow for a potential future migration away
  from such wrinkles as the staging check in notFound
  (see  Note [Out of scope might be a staging error]) we consistently do
  the strict staging check that we also do for value if ExplicitLevelImports
  is on.
  
  Closes #26098
  

• 5f0dbeb6
  by Simon Hengel at 2026-02-03T16:00:12-05:00

  Use Haddock formatting in deprecation message of `initNameCache`

• 01ecb612
  by Andreas Klebinger at 2026-02-04T09:56:25-05:00

  testsuite: Explicitly use utf-8 encoding in rts-includes linter.
  
  Not doing so caused failures on windows, as python failed to pick a
  reasonable encoding even with locale set.
  
  Fixes #26850
  

• ea0d1317
  by Zubin Duggal at 2026-02-04T09:57:06-05:00

  Bump transformers submodule to 0.6.3.0
  
  Fixes #26790
  

• cbe4300e
  by Simon Peyton Jones at 2026-02-05T04:31:04-05:00

  Fix subtle bug in GHC.Core.Utils.mkTick
  
  This patch fixes a decade-old bug in `mkTick`, which
  could generate type-incorrect code!  See the diagnosis
  in #26772.
  
  The new code is simpler and easier to understand.
  (As #26772 says, I think it could be improved further.)
  

• a193a8da
  by Simon Peyton Jones at 2026-02-05T04:31:04-05:00

  Modify a debug-trace in the Simplifier
  
  ...just to show a bit more information.
  

• b579dfdc
  by Simon Peyton Jones at 2026-02-05T04:31:04-05:00

  Fix long-standing interaction between ticks and casts
  
  The code for Note [Eliminate Identity Cases] was simply wrong when
  ticks and casts interacted.  This patch fixes the interaction.
  
  It was shown up when validating #26772, although it's not the exactly
  the bug that's reported by #26772.  Nor is it easy to reproduce, hence
  no regression test.
  

• fac0de1e
  by Cheng Shao at 2026-02-05T04:31:49-05:00

  libraries: bump Cabal submodule to 3.16.1.0
  

• 00589122
  by Cheng Shao at 2026-02-05T04:31:49-05:00

  libraries: bump deepseq submodule to 1.5.2.0
  
  Also:
  
  - Get rid of usage of deprecated `NFData` function instance in the
    compiler
  - `T21391` still relies on `NFData` function instance, add
    `-Wno-deprecations` for the time being.
  

• 84474c71
  by Cheng Shao at 2026-02-05T04:31:50-05:00

  libraries: bump directory submodule to 1.3.10.1
  

• 1a9f4662
  by Cheng Shao at 2026-02-05T04:31:50-05:00

  libraries: bump exceptions submodule to 0.10.12
  

• 2e39a340
  by Peng Fan at 2026-02-07T03:42:01-05:00

  NCG/LA64: adjust register usage to avoid src-register being clobbered
  

• 9faf1b35
  by Teo Camarasu at 2026-02-07T03:42:43-05:00

  ghc-internal: Delete unnecessary GHC.Internal.Data.Ix
  
  This module merely re-exports GHC.Internal.Ix. It was copied from
  `base` when `ghc-internal` was split, but there is no reason to have
  this now. So, let's delete it.
  
  Resolves #26848
  

• d112b440
  by Sven Tennie at 2026-02-07T10:47:56-05:00

  Add cabal.project file to generate-ci
  
  This fixes the HLS setup for our CI code generation script
  (generate-ci).
  
  The project file simply makes `generate-ci` of the cabal file
  discoverable.
  

• 5339f6f0
  by Andreas Klebinger at 2026-02-07T10:48:40-05:00

  CI: Don't collapse test results.
  
  This puts test output back into the primary test log instead of a
  subsection removing the need to expand a section to see test results.
  
  While the intention was good in practice the old behaviour mostly wastes time
  by requiring expansion of the section.
  
  Fixes #26882
  

• 0e1cd2e0
  by Evan Piro at 2026-02-08T10:35:16-08:00

  Linker.MacOS reduce dynflags import
  

• 1c79a4cd
  by Michael Alan Dorman at 2026-02-09T08:11:51-05:00

  Remove `extra_src_files` variable from `testsuite/driver/testlib.py`
  
  While reading through the test harness code, I noticed this variable
  with a TODO attached that referenced #12223.  Although that bug is
  closed, it strongly implied that this special-case variable that only
  affected a single test was expected to be removed at some point.
  
  I also looked at 3415bcaa0b1903b5e12dfaadb5b774718e406eab---where it
  was added---whose commit message suggested that it would have been
  desirable to remove it, but that there were special circumstances that
  meant it had to remain (though it doesn't elucidate what those special
  circumstances are).
  
  However, the special circumstances were mentioned as if the test was
  in a different location than is currently is, so I decided to try
  changing the test to use the standard `extra_files` mechanism, which
  works in local testing.
  
  This also seems like a reasonable time to remove the script that was
  originally used in the transition, since it doesn't really serve a
  purpose anymore.
  

• 0020e38a
  by Matthew Pickering at 2026-02-09T17:29:14-05:00

  determinism: Use a stable sort in WithHsDocIdentifiers binary instance
  
  `WithHsDocIdentifiers` is defined as
  
  ```
   71 data WithHsDocIdentifiers a pass = WithHsDocIdentifiers
   72   { hsDocString      :: !a
   73   , hsDocIdentifiers :: ![Located (IdP pass)]
   74   }
  ```
  
  This list of names is populated from `rnHsDocIdentifiers`, which calls
  `lookupGRE`, which calls `lookupOccEnv_AllNameSpaces`, which calls
  `nonDetEltsUFM` and returns the results in an order depending on
  uniques.
  
  Sorting the list with a stable sort before returning the interface makes
  the output deterministic and follows the approach taken by other fields
  in `Docs`.
  
  Fixes #26858
  

• 89898ce6
  by echoumcp1 at 2026-02-09T17:30:01-05:00

  Replace putstrln with logMsg in handleSeqHValueStatus
  
  Fixes #26549
  

• 7c52c4f9
  by John Paul Adrian Glaubitz at 2026-02-10T13:52:43-05:00

  rts: Switch prim to use modern atomic compiler builtins
  
  The __sync_*() atomic compiler builtins have been deprecated in GCC
  for a while now and also don't provide variants for 64-bit values
  such as __sync_fetch_and_add_8().
  
  Thus, replace them with the modern __atomic_*() compiler builtins and
  while we're at it, also drop the helper macro CAS_NAND() which is now
  no longer needed since we stopped using the __sync_*() compiler builtins
  altogether.
  
  Co-authored-by: Ilias Tsitsimpis <iliastsi@debian.org>
  
  Fixes #26729
  

• cf60850a
  by Recursion Ninja at 2026-02-10T13:53:27-05:00

  Decoupling L.H.S.Decls from GHC.Types.ForeignCall
  
    - Adding TTG extension point for 'CCallTarget'
    - Adding TTG extension point for 'CType'
    - Adding TTG extension point for 'Header'
    - Moving ForeignCall types that do not need extension
      to new L.H.S.Decls.Foreign module
    - Replacing 'Bool' parameters with descriptive data-types
      to increase clairty and prevent "Boolean Blindness"
  

• 11a04cbb
  by Eric Lee at 2026-02-11T09:20:46-05:00

  Derive Semigroup/Monoid for instances believed could be derived in #25871
  

• 15d9ce44
  by Eric Lee at 2026-02-11T09:20:46-05:00

  add Ghc.Data.Pair deriving
  

• c85dc170
  by Evan Piro at 2026-02-11T09:21:45-05:00

  Linker.MacOS reduce options import
  

• a541dd83
  by Chris Wendt at 2026-02-11T16:06:41-05:00

  Initialize plugins for `:set +c` in GHCi
  
  Fixes #23110.
  

• 0f5a73bc
  by Cheng Shao at 2026-02-11T16:07:27-05:00

  compiler: add Binary Text instance
  
  This patch adds `Binary` instance for strict `Text`, in preparation of
  making `Text` usable in certain GHC API use cases (e.g. haddock). This
  also introduces `text` as a direct dependency of the `ghc` package.
  

• 9e58b8a1
  by Cheng Shao at 2026-02-11T16:08:10-05:00

  ghc-toolchain: add C11 check
  
  This patch partially reverts commit
  b8307eab80c5809df5405d76c822bf86877f5960 that removed C99 check in
  autoconf/ghc-toolchain. Now we:
  
  - No longer re-implement `FP_SET_CFLAGS_C11` similar to
    `FP_SET_CFLAGS_C99` in the past, since autoconf doesn't provide a
    convenient `AC_PROG_CC_C11` function. ghc-toolchain will handle it
    anyway.
  - The Cmm CPP C99 check is relanded and repurposed for C11.
  - The C99 logic in ghc-toolchain is relanded and repurposed for C11.
  - The C99 check in Stg.h is corrected to check for C11. The obsolete
    _ISOC99_SOURCE trick is dropped.
  - Usages of `-std=gnu99` in the testsuite are corrected to use
    `-std=gnu11`.
  
  Closes #26908.
  

• 4df0adf6
  by Simon Peyton Jones at 2026-02-11T21:50:13-05:00

  Simplify the treatment of static forms
  
  This MR implements GHC proposal 732: simplify static forms,
     https://github.com/ghc-proposals/ghc-proposals/pull/732
  thereby addressing #26556.
  
  See `Note [Grand plan for static forms]` in GHC.Iface.Tidy.StaticPtrTable
  
  The main changes are:
  
  * There is a new, simple rule for (static e), namely that the free
    term variables of `e` must be bound at top level.  The check is
    done in the `HsStatic` case of `GHC.Rename.Expr.rnExpr`
  
  * That in turn substantially simplifies the info that the typechecker
    carries around in its type environment.  Hooray.
  
  * The desugarer emits static bindings to top level directly; see the
    `HsStatic` case of `dsExpr`.
  
  * There is no longer any special static-related magic in the FloatOut
    pass.  And the main Simplifier pipeline no longer needs a special case
    to run FloatOut even with -O0.  Hooray.
  
  All this forced an unexpected change to the pattern match checker. It
  recursively invokes the main Hs desugarer when it wants to take a look
  at a term to spot some special cases (notably constructor applications).
  We don't want to emit any nested (static e) bindings to top level a
  second time!  Yikes.
  
  That forced a modest refactor in GHC.HsToCore.Pmc:
  
  * The `dsl_nablas` field of `DsLclEnv` now has a `NoPmc` case, which says
    "I'm desugaring just for pattern-match checking purposes".
  
  * When that flag is set we don't emit static binds.
  
  That in turn forces a cascade of refactoring, but the net effect is an
  improvement; less risk of duplicated (even exponential?) work.
  
  See Note [Desugaring HsExpr during pattern-match checking].
  
  10% metric decrease, on some architectures, of compile-time max-bytes-used on T15304.
  
  Metric Decrease:
      T15304
  

• 7922f728
  by Teo Camarasu at 2026-02-11T21:50:58-05:00

  ghc-internal: avoid depending on GHC.Internal.Exts
  
  This module is mostly just re-exports. It made sense as a user-facing
  module, but there's no good reason ghc-internal modules should depend on
  it and doing so linearises the module graph
  
  - move considerAccessible to GHC.Internal.Magic
  
  Previously it lived in GHC.Internal.Exts, but it really deserves to live
  along with the other magic function, which are already re-exported from .Exts
  
  - move maxTupleSize to GHC.Internal.Tuple
  
  This previously lived in GHC.Internal.Exts but a comment already said it
  should be moved to .Tuple
  
  Resolves #26832
  

• b6a4a29b
  by Eric Lee at 2026-02-11T21:51:55-05:00

  Remove unused Semigroup imports to fix GHC 9.14 bootstrapping
  

• 99d8c146
  by Simon Peyton Jones at 2026-02-12T17:36:59+00:00

  Fix subtle bug in cast worker/wrapper
  
  See (CWw4) in Note [Cast worker/wrapper].
  
  The true payload is in the change to the definition of
     GHC.Types.Id.Info.hasInlineUnfolding
  Everthing else is just documentation.
  
  There is a 2% compile time decrease for T13056;
  I'll take the win!
  
  Metric Decrease:
      T13056
  

• 530e8e58
  by Simon Peyton Jones at 2026-02-12T20:17:23-05:00

  Add regression tests for four StaticPtr bugs
  
  Tickets #26545, #24464, #24773, #16981 are all solved by the
  recently-landed MR
  
      commit 318ee13bcffa6aa8df42ba442ccd92aa0f7e210c
      Author: Simon Peyton Jones <simon.peytonjones@gmail.com>
      Date:   Mon Oct 20 23:07:20 2025 +0100
  
      Simplify the treatment of static forms
  
  This MR just adds regression tests for them.
  

• 4157160f
  by Cheng Shao at 2026-02-13T06:27:04-05:00

  ci: remove unused hlint-ghc-and-base job definition
  
  This patch removes the unused `hlint-ghc-and-base` job definition,
  it's never run since !9806. Note that hadrian lint rules still work
  locally, so anyone that wishes to run hlint on the codebase can
  continue to do so in their local worktree.
  

• 039f1977
  by Cheng Shao at 2026-02-13T06:27:47-05:00

  wasm: use import.meta.main for proper distinction of nodejs main modules
  
  This patch uses `import.meta.main` for proper distinction of nodejs
  main modules, especially when the main module might be installed as a
  symlink. Fixes #26916.
  

• 14f485ee
  by ARATA Mizuki at 2026-02-17T09:09:24+09:00

  Support more x86 extensions: AVX-512 {BW,DQ,VL} and GFNI
  
  Also, mark AVX-512 ER and PF as deprecated.
  
  AVX-512 instructions can be used for certain 64-bit integer vector operations.
  
  GFNI can be used to implement bitReverse (currently not used by NCG, but LLVM may use it).
  
  Closes #26406
  Addresses #26509
  

• 016f79d5
  by fendor at 2026-02-17T09:16:16-05:00

  Hide implementation details from base exception stack traces
  
  Ensure we hide the implementation details of the exception throwing mechanisms:
  
  * `undefined`
  * `throwSTM`
  * `throw`
  * `throwIO`
  * `error`
  
  The `HasCallStackBacktrace` should always have a length of exactly 1,
  not showing internal implementation details in the stack trace, as these
  are vastly distracting to end users.
  
  CLC proposal [#387](https://github.com/haskell/core-libraries-committee/issues/387)
  

• 4f2840f2
  by Brian J. Cardiff at 2026-02-17T17:04:08-05:00

  configure: Accept happy-2.2
  
  In Jan 2026 happy-2.2 was released. The most sensible change is https://github.com/haskell/happy/issues/335 which didn't trigger in a fresh build
  

• 10b4d364
  by Duncan Coutts at 2026-02-17T17:04:52-05:00

  Fix errors in the documentation of the eventlog STOP_THREAD status codes
  
  Fix the code for BlockedOnMsgThrowTo.
  
  Document all the known historical warts.
  
  Fixes issue #26867
  

• c5e15b8b
  by Phil de Joux at 2026-02-18T05:07:36-05:00

  haddock: use snippets for all list examples
  
  - generate snippet output for docs
  - reduce font size to better fit snippets
  - Use only directive to guard html snippets
  - Add latex snippets for lists
  

• d388bac1
  by Phil de Joux at 2026-02-18T05:07:36-05:00

  haddock: Place the snippet input and output together
  
  - Put the output seemingly inside the example box
  

• 016fa306
  by Samuel Thibault at 2026-02-18T05:08:35-05:00

  Fix linking against libm by moving the -lm option
  
  For those systems that need -lm for getting math functions, this is
  currently added on the link line very early, before the object files being
  linked together. Newer toolchains enable --as-needed by default, which means
  -lm is ignored at that point because no object requires a math function
  yet. With such toolchains, we thus have to add -lm after the objects, so the
  linker actually includes libm in the link.
  

• 68bd0805
  by Teo Camarasu at 2026-02-18T05:09:19-05:00

  ghc-internal:  Move GHC.Internal.Data.Bool to base
  
  This is a tiny module that only defines bool :: Bool -> a -> a -> a. We can just move this to base and delete it from ghc-internal. If we want this functionality there we can just use a case statement or if-then expression.
  
  Resolves 26865
  

• 4c40df3d
  by fendor at 2026-02-20T10:24:48-05:00

  Add optional `SrcLoc` to `StackAnnotation` class
  
  `StackAnnotation`s give access to an optional `SrcLoc` field that
  user-added stack annotations can use to provide better backtraces in both error
  messages and when decoding the callstack.
  
  We update builtin stack annotations such as `StringAnnotation` and
  `ShowAnnotation` to also capture the `SrcLoc` of the current `CallStack`
  to improve backtraces by default (if stack annotations are used).
  
  This change is backwards compatible with GHC 9.14.1.
  

• fd9aaa28
  by Simon Hengel at 2026-02-20T10:25:33-05:00

  docs: Fix grammar in explicit_namespaces.rst
  

• 44354255
  by Vo Minh Thu at 2026-02-20T18:53:06-05:00

  GHCi: add a :version command.
  
  This looks like:
  
      ghci> :version
      GHCi, version 9.11.20240322
  
  This closes #24576.
  
  Co-Author: Markus Läll <markus.l2ll@gmail.com>
  

• eab3dbba
  by Andreas Klebinger at 2026-02-20T18:53:51-05:00

  hadrian/build-cabal: Better respect and utilize -j
  
  * We now respect -j<n> for the cabal invocation to build hadrian rather
    than hardcoding -j
  * We use the --semaphore flag to ensure cabal/ghc build the hadrian
    executable in parallel using the -jsem mechanism.
  
  Saves 10-15s on fresh builds for me.
  
  Fixes #26876
  

• 17839248
  by Teo Camarasu at 2026-02-24T08:36:03-05:00

  ghc-internal: avoid depending on GHC.Internal.Control.Monad.Fix
  
  This module contains the definition of MonadFix, since we want an
  instance for IO, that instance requires a lot of machinery and we want
  to avoid an orphan instance, this will naturally be quite high up in the
  dependency graph.
  
  So we want to avoid other modules depending on it as far as possible.
  
  On Windows, the IO manager depends on the RTSFlags type, which
  transtively depends on MonadFix. We refactor things to avoid this
  dependency, which would have caused a regression.
  
  Resolves #26875
  
  Metric Decrease:
      T12227
  

• fa88d09a
  by Wolfgang Jeltsch at 2026-02-24T08:36:47-05:00

  Refine the imports of `System.IO.OS`
  
  Commit 68bd08055594b8cbf6148a72d108786deb6c12a1 replaced the
  `GHC.Internal.Data.Bool` import by a `GHC.Internal.Base` import.
  However, while the `GHC.Internal.Data.Bool` import was conditional and
  partial, the `GHC.Internal.Base` import is unconditional and total. As a
  result, the import list is not tuned to import only the necessary bits
  anymore, and furthermore GHC emits a lot of warnings about redundant
  imports.
  
  This commit makes the `GHC.Internal.Base` import conditional and partial
  in the same way that the `GHC.Internal.Data.Bool` import was.
  

• c951fef1
  by Cheng Shao at 2026-02-25T20:58:28+00:00

  wasm: add /assets endpoint to serve user-specified assets
  
  This patch adds an `/assets` endpoint to the wasm dyld http server, so
  that users can also fetch assets from the same host with sensible
  default MIME types, without needing a separate http server for assets
  that also introduces CORS headaches:
  
  - A `-fghci-browser-assets-dir` driver flag is added to specify the
    assets root directory (defaults to `$PWD`)
  - The dyld http server fetches `mime-db` on demand and uses it as
    source of truth for mime types.
  
  Closes #26951.
  

• dde22f97
  by Sylvain Henry at 2026-02-26T13:14:03-05:00

  Fix -fcheck-prim-bounds for non constant args (#26958)
  
  Previously we were only checking bounds for constant (literal)
  arguments!
  
  I've refactored the code to simplify the generation of out-of-line Cmm
  code for the primop composed of some inline code + some call to an
  external Cmm function.
  

• bd3eba86
  by Vladislav Zavialov at 2026-02-27T05:48:01-05:00

  Check for negative type literals in the type checker (#26861)
  
  GHC disallows negative type literals (e.g., -1), as tested by T8306 and
  T8412. This check is currently performed in the renamer:
  
    rnHsTyLit tyLit@(HsNumTy x i) = do
      when (i < 0) $
        addErr $ TcRnNegativeNumTypeLiteral tyLit
  
  However, this check can be bypassed using RequiredTypeArguments
  (see the new test case T26861). Prior to this patch, such programs
  caused the compiler to hang instead of reporting a proper error.
  This patch addresses the issue by adding an equivalent check in
  the type checker, namely in tcHsType.
  
  The diff is deliberately minimal to facilitate backporting. A more
  comprehensive rework of HsTyLit is planned for a separate commit.
  

• faf14e0c
  by Vladislav Zavialov at 2026-02-27T05:48:45-05:00

  Consistent pretty-printing of HsString, HsIsString, HsStrTy
  
  Factor out a helper to pretty-print string literals, thus fixing newline
  handling for overloaded string literals and type literals.
  
  Test cases: T26860ppr T26860ppr_overloaded T26860ppr_tylit
  
  Follow up to ddf1434ff9bb08cfef3c93f23de6b83ec698aa27
  

• f108a972
  by Arnaud Spiwack at 2026-02-27T12:53:01-05:00

  Make list comprehension completely non-linear
  
  Fixes #25081
  
  From the note:
  
  The usefulness of list comprehension in conjunction with linear types is dubious.
  After all, statements are made to be run many times, for instance in
  
  ```haskell
  [u | y <- [0,1], stmts]
  ```
  
  both `u` and `stmts` are going to be run several times.
  
  In principle, though, there are some position in a monad comprehension
  expression which could be considered linear. We could try and make it so that
  these positions are considered linear by the typechecker, but in practice the
  desugarer doesn't take enough care to ensure that these are indeed desugared to
  linear sites. We tried in the past, and it turned out that we'd miss a
  desugaring corner case (#25772).
  
  Until there's a demand for this very specific improvement, let's instead be
  conservative, and consider list comprehension to be completely non-linear.
  

• ae799cab
  by Simon Jakobi at 2026-02-27T12:53:54-05:00

  PmAltConSet: Use Data.Set instead of Data.Map
  
  ...to store `PmLit`s.
  
  The Map was only used to map keys to themselves.
  Changing the Map to a Set saves a Word of memory per entry.
  
  Resolves #26756.
  

• dcd7819c
  by Vladislav Zavialov at 2026-02-27T18:46:03-05:00

  Drop HsTyLit in favor of HsLit (#26862, #25121)
  
  This patch is a small step towards unification of HsExpr and HsType,
  taking care of literals (HsLit) and type literals (HsTyLit).
  
  Additionally, it improves error messages for unsupported type literals,
  such as unboxed or fractional literals (test cases: T26862, T26862_th).
  
  Changes to the AST:
  
  * Use HsLit           where HsTyLit   was previously used
  * Use HsChar          where HsCharTy  was previously used
  * Use HsString        where HsStrTy   was previously used
  * Use HsNatural (NEW) where HsNumTy   was previously used
  * Use HsDouble  (NEW) to represent unsupported fractional type literals
  
  Changes to logic:
  
  * Parse unboxed and fractional type literals (to be rejected later)
  
  * Drop the check for negative literals in the renamer (rnHsTyLit)
    in favor of checking in the type checker (tc_hs_lit_ty)
  
  * Check for invalid type literals in TH (repTyLit) and report
    unrepresentable literals with ThUnsupportedTyLit
  
  * Allow negative type literals in TH (numTyLit). This is fine as
    these will be taken care of at splice time (test case: T8306_th)
  

• c927954f
  by Vladislav Zavialov at 2026-02-27T18:46:50-05:00

  Increase test coverage of diagnostics
  
  Add test cases for the previously untested diagnostics:
    [GHC-01239] PsErrIfInFunAppExpr
    [GHC-04807] PsErrProcInFunAppExpr
    [GHC-08195] PsErrInvalidRecordCon
    [GHC-16863] PsErrUnsupportedBoxedSumPat
    [GHC-18910] PsErrSemiColonsInCondCmd
    [GHC-24737] PsErrInvalidWhereBindInPatSynDecl
    [GHC-25037] PsErrCaseInFunAppExpr
    [GHC-25078] PsErrPrecedenceOutOfRange
    [GHC-28021] PsErrRecordSyntaxInPatSynDecl
    [GHC-35827] TcRnNonOverloadedSpecialisePragma
    [GHC-40845] PsErrUnpackDataCon
    [GHC-45106] PsErrInvalidInfixHole
    [GHC-50396] PsErrInvalidRuleActivationMarker
    [GHC-63930] MultiWayIfWithoutAlts
    [GHC-65536] PsErrNoSingleWhereBindInPatSynDecl
    [GHC-67630] PsErrMDoInFunAppExpr
    [GHC-70526] PsErrLetCmdInFunAppCmd
    [GHC-77808] PsErrDoCmdInFunAppCmd
    [GHC-86934] ClassPE
    [GHC-90355] PsErrLetInFunAppExpr
    [GHC-91745] CasesExprWithoutAlts
    [GHC-92971] PsErrCaseCmdInFunAppCmd
    [GHC-95644] PsErrBangPatWithoutSpace
    [GHC-97005] PsErrIfCmdInFunAppCmd
  
  Remove unused error constructors:
    [GHC-44524] PsErrExpectedHyphen
    [GHC-91382] TcRnIllegalKindSignature
  

• 3a9470fd
  by Torsten Schmits at 2026-02-27T18:47:34-05:00

  Avoid expensive computation for debug logging in `mergeDatabases` when log level is low
  
  This computed and traversed a set intersection for every single
  dependency unconditionally.
  

• ea4c2cbd
  by Brandon Chinn at 2026-02-27T16:22:38-08:00

  Implement QualifiedStrings (#26503)
  
  See Note [Implementation of QualifiedStrings]
  

• 08bc245b
  by sheaf at 2026-03-01T11:11:54-05:00

  Clean up join points, casts & ticks
  
  This commit shores up the logic dealing with casts and ticks occurring
  in between a join point binding and a jump.
  
  Fixes #26642 #26929 #26693
  Makes progress on #14610 #26157 #26422
  
  Changes:
  
    - Remove 'GHC.Types.Tickish.TickishScoping' in favour of simpler
      predicates 'tickishHasNoScope'/'tickishHasSoftScope', as things were
      before commit 993975d3. This makes the code easier to read and
      document (fewer indirections).
  
    - Introduce 'canCollectArgsThroughTick' for consistent handling of
      ticks around PrimOps and other 'Id's that cannot be eta-reduced.
      See overhauled Note [Ticks and mandatory eta expansion].
  
    - New Note [JoinId vs TailCallInfo] in GHC.Core.SimpleOpt that explains
      robustness of JoinId vs fragility of TailCallInfo.
  
    - Allow casts/non-soft-scoped ticks to occur in between a join point
      binder and a jump, but only in Core Prep.
      See Note [Join points, casts, and ticks] and
      Note [Join points, casts, and ticks... in Core Prep]
      in GHC.Core.Opt.Simplify.Iteration.
  
      Also update Core Lint to account for this.
      See Note [Linting join points with casts or ticks] in GHC.Core.Lint.
  
    - Update 'GHC.Core.Utils.mergeCaseAlts' to avoid pushing a cast in
      between a join point binding and its jumps. This fixes #26642.
      See the new (MC5) and (MC6) in Note [Merge Nested Cases].
  
    - Update float out to properly handle source note ticks. They are now
      properly floated out instead of being discarded.
      This increases the number of ticks in certain tests with -g.
  
  Test cases: T26642 and TrickyJoins.
  
  Metric increase due to more source note ticks with -g:
  
  -------------------------
  Metric Increase:
      libdir
      size_hello_artifact
      size_hello_unicode
  -------------------------
  

• 476c4cdf
  by Sean D. Gillespie at 2026-03-02T10:14:37-05:00

  Add SIMD absolute value on x86 and LLVM
  
  On x86, absolute value of 32 bits or less is implemented with
  PABSB/PABSW/PABSD if SSSE3 is available. Otherwise, there is a fallback
  for SSE2. For 64 bit integers it uses VPABSQ, required by AVX-512VL,
  with fallbacks for SSE4.2 and SSE2.
  
  There is no dedicated instruction for floating point absolute value on
  x86, so it is simulated using bitwise AND.
  
  Absolute value for signed integers and floats are implemented by the
  "llvm.abs/llvm.fabs" standard library intrinsics. This implementation
  uses MachOps constructors, unlike non-vector floating point absolute
  value, which uses CallishMachOps.
  

• 709448c0
  by Sean D. Gillespie at 2026-03-02T10:14:46-05:00

  Add SIMD floating point square root
  
  On x86, this is implemented with the SQRTPS and SQRTPD instructions. On
  LLVM, it uses the sqrt library intrinstic.
  

• 0deadf66
  by Sean D. Gillespie at 2026-03-02T10:14:47-05:00

  Improve error message for SIMD on aarch64
  
  When encountering vector literals on aarch64, previously it would
  throw:
  
      <no location info>: error:
          panic! (the 'impossible' happened)
        GHC version 9.15.20251219:
              getRegister' (CmmLit:CmmVec):
  
  Now it is more consistent with the other vector operations:
  
      <no location info>: error:
          sorry! (unimplemented feature or known bug)
        GHC version 9.15.20251219:
              SIMD operations on AArch64 currently require the LLVM backend
  

• 7d64031b
  by Vladislav Zavialov at 2026-03-03T11:09:28-05:00

  Replace maybeAddSpace with spaceIfSingleQuote
  
  Simplify pretty-printing of HsTypes by using spaceIfSingleQuote.
  This allows us to drop the unwieldy lhsTypeHasLeadingPromotionQuote
  helper function.
  
  Follow-up to 178c1fd830c78377ef5d338406a41e1d8eb5f0da
  

• 598db847
  by Wolfgang Jeltsch at 2026-03-06T06:25:25-05:00

  Correct `hIsReadable` and `hIsWritable` for duplex handles
  
  This contribution implements CLC proposal #371. It changes `hIsReadable`
  and `hIsWritable` such that they always throw a respective exception
  when encountering a closed or semi-closed handle, not just in the case
  of a file handle.
  

• b90201e5
  by Wolfgang Jeltsch at 2026-03-06T06:25:25-05:00

  Document `SemiClosedHandle`
  

• c9df72b5
  by Wolfgang Jeltsch at 2026-03-06T06:25:25-05:00

  Tell users what “semi-closed” means for duplex handles
  

• a8aa1868
  by Ilias Tsitsimpis at 2026-03-06T06:26:29-05:00

  Fix determinism of linker arguments
  
  The switch from Data.Map to UniqMap in 3b5be05ac29 introduced
  non-determinism in the order of packages passed to the linker.
  
  This resulted in non-reproducible builds where the DT_NEEDED entries in
  dynamic libraries were ordered differently across builds.
  
  Fix the regression by explicitly sorting the package list derived from
  UniqMap.
  
  Fixes #26838
  

• 9b64ad3a
  by Matthew Pickering at 2026-03-06T06:27:16-05:00

  determinism: Use a deterministic renaming when writing bytecode files
  
  Now when writing the bytecode file, a counter and substitution are used
  to provide deterministic keys to local variables (rather than relying on
  uniques). This change ensures that `.gbc` are produced
  deterministically.
  
  Fixes #26499
  

• d29800e0
  by Teo Camarasu at 2026-03-06T06:28:46-05:00

  ghc-internal: delete Version hs-boot loop
  
  Version has a Read instance which needs Unicode but part of the Unicode interface is the unicode version. This is easy to resolve. We simply don't re-export the version from the Unicode module.
  
  Resolves #26940
  

• ad25af90
  by Sylvain Henry at 2026-03-06T06:30:33-05:00

  Linker: implement support for COMMON symbols (#6107)
  
  Add some support for COMMON symbols. We don't support common symbols
  having different sizes where the larger one is allocated after the
  smaller one. The linker will fail with an appropriate error message if
  it happens.
  

• 3b59f158
  by Cheng Shao at 2026-03-06T06:31:16-05:00

  compiler: fix redundant import of GHC.Hs.Lit
  
  This patch removes a redundant import of `GHC.Hs.Lit` which causes a
  ghc build failure with validate flavours when bootstrapping from 9.14.
  Fixes #26972.
  

• 148d36f3
  by Cheng Shao at 2026-03-06T06:32:01-05:00

  compiler: avoid unneeded traversals in GHC.Unit.State
  
  Following !15591, this patch avoids unneeded traversals in
  `reportCycles`/`reportUnusable` when log verbosity is below given
  threshold. Also applies `logVerbAtLeast` when appropriate.
  
  Co-authored-by: Codex <codex@openai.com>
  

• 7e31367c
  by Cheng Shao at 2026-03-06T06:32:46-05:00

  ghc-internal: fix redundant import in GHC.Internal.Event.Windows.ManagedThreadPool
  
  This patch fixes redundant import in
  `GHC.Internal.Event.Windows.ManagedThreadPool` that causes a
  compilation error when building windows target with validate flavours
  and bootstrapping from 9.14. Fixes #26976.
  

• fc8b8e27
  by sheaf at 2026-03-06T06:33:28-05:00

  System.Info.fullCompilerVersion: add 'since' annot
  
  Fixes #26973

• c8238375
  by Sylvain Henry at 2026-03-06T06:34:23-05:00

  Hadrian: deprecate --bignum and automatically enable +native_bignum for JS
  
  Deprecate --bignum=... to select the bignum backend. It's only used to
  select the native backend, and this can be done with the +native_bignum
  flavour transformer.
  
  Additionally, we automatically enable +native_bignum for the JS target
  because the GMP backend isn't supported.
  

• a3ac7074
  by Sylvain Henry at 2026-03-06T06:35:17-05:00

  JS: fix putEnum/fromEnum (#24593)
  
  Don't go through Word16 when serializing Enums.
  

• 0b36e96c
  by Andreas Klebinger at 2026-03-06T06:35:58-05:00

  Docs: Document -fworker-wrapper-cbv default setting.
  
  Fixes #26841
  

• eca445e7
  by mangoiv at 2026-03-07T05:02:36-05:00

  drop deb9/10 from CI, add deb13
  
  debian 9 and 10 are end of life, hence we drop them
  from our CI, but we do add debian 13. Jobs that were
  previously run on 9 and 10 run on 13, too, jobs that
  were run on 10, are run on 11 now. Jobs that were
  previously run on debian 12 are run on debian 13 now.
  This MR also updates hadrian's bootstrap plans for that
  reason.
  
  Metric Decrease:
      T9872d
  

• 12f8b829
  by Luite Stegeman at 2026-03-07T05:03:33-05:00

  Fix GHC.Internal.Prim haddock
  
  Haddock used to parse Haskell source to generate documentation,
  but switched to using interface files instead. This broke documentation
  of the GHC.Internal.Prim module, since it's a wired-in interface that
  didn't provide a document structure.
  
  This patch adds the missing document structure and updates genprimopcode
  to make the section headers and descriptions available.
  
  fixes #26954
  

• f87e5e57
  by Luite Stegeman at 2026-03-07T05:03:33-05:00

  Remove obsolete --make-haskell-source from genprimopcode
  
  Now that haddock uses the wired-in interface for GHC.Internal.Prim,
  the generated Haskell source file is no longer needed. Remove the
  --make-haskell-source code generator from genprimopcode and replace
  the generated GHC/Internal/Prim.hs with a minimal static source file.
  

• 4a7ddc7b
  by Sylvain Henry at 2026-03-07T05:04:59-05:00

  JS: fix linking of exposed but non-preload units (#24886)
  
  Units exposed in the unit database but not explicitly passed on the
  command-line were not considered by the JS linker. This isn't an issue
  for cabal which passes every unit explicitly but it is an issue when
  using GHC directly (cf T24886 test).
  

• 689aafcd
  by mangoiv at 2026-03-07T05:05:52-05:00

  testsuite: double foundation timeout multiplier
  
  The runtime timeout in the foundation test was regularly hit by code
  generated by the wasm backend - we increase the timout since the high
  runtime is expected on the wasm backend for this rather complex test.
  
  Resolves #26938
  

• a46a1bb1
  by Cheng Shao at 2026-03-09T04:50:30-04:00

  compiler: add myCapabilityExpr to GHC.Cmm.Utils
  
  This commit adds `myCapabilityExpr` to `GHC.Cmm.Utils` which is
  computed from `BaseReg`. It's convenient for codegen logic where one
  needs to pass the current Capability's pointer.
  

• 4afc65b1
  by Cheng Shao at 2026-03-09T04:50:30-04:00

  compiler: lower tryPutMVar# into a ccall directly
  
  This patch addresses an old TODO of `stg_tryPutMVarzh` by removing it
  completely and making the compiler lower `tryPutMVar#` into a ccall to
  `performTryPutMVar` directly, without landing into an intermediate C
  or Cmm function. `performTryPutMVar` is promoted to a public RTS
  function with default visibility, and the compiler lowering logic
  takes into account the C ABI of `performTryPutMVar` and converts from
  C Bool to primop's `Int#` result properly.
  

• 9e3d6a58
  by Simon Hengel at 2026-03-09T04:51:15-04:00

  Don't use #line in haddocks
  
  This confuses the parser.  Haddock output is unaffected by this change.
  (read: this still produces the same documentation)
  

• f4e8fec2
  by Wolfgang Jeltsch at 2026-03-09T04:52:01-04:00

  Remove in-package dependencies on `GHC.Internal.System.IO`
  
  This contribution eliminates all dependencies on
  `GHC.Internal.System.IO` from within `ghc-internal`. It comprises the
  following changes:
  
    * Make `GHC.Internal.Fingerprint` independent of I/O support
    * Tighten the dependencies of `GHC.Internal.Data.Version`
    * Tighten the dependencies of `GHC.Internal.TH.Monad`
    * Tighten the dependencies of `GHCi.Helpers`
    * Move some code that needs `System.IO` to `template-haskell`
    * Move the `GHC.ResponseFile` implementation into `base`
    * Move the `System.Exit` implementation into `base`
    * Move the `System.IO.OS` implementation into `base`
  
  Metric Decrease:
      size_hello_artifact
      size_hello_artifact_gzip
      size_hello_unicode
      size_hello_unicode_gzip
  

• 91df4c82
  by Sylvain Henry at 2026-03-09T04:53:20-04:00

  T18832: fix Windows CI failure by dropping removeDirectoryRecursive
  
  On Windows, open file handles prevent deletion. After killThread, the
  closer thread may not have called hClose yet, causing removeDirectoryRecursive
  to fail with "permission denied". The test harness cleans up the run
  directory anyway, so the call is redundant.
  

• d7fe9671
  by Cheng Shao at 2026-03-09T04:54:04-04:00

  compiler: fix redundant import in GHC.StgToJS.Object
  
  This patch fixes a redundant import in GHC.StgToJS.Object that causes
  a build failure when compiling head from 9.14 with validate flavours.
  Fixes #26991.
  

• 0bfd29c3
  by Cheng Shao at 2026-03-09T04:54:46-04:00

  wasm: fix `Illegal foreign declaration` failure when ghci loads modules with JSFFI exports
  
  This patch fixes a wasm ghci error when loading modules with JSFFI
  exports; the `backendValidityOfCExport` check in `tcCheckFEType`
  should only makes sense and should be performed when not checking the
  JavaScript calling convention; otherwise, when the calling convention
  is JavaScript, the codegen logic should be trusted to backends that
  actually make use of it. Fixes #26998.
  

• e659610c
  by Duncan Coutts at 2026-03-09T12:08:35-04:00

  Apply NOINLINE pragmas to generated Typeable bindings
  
  For context, see the existing Note [Grand plan for Typeable]
  and the Note [NOINLINE on generated Typeable bindings] added in the
  subsequent commit.
  
  This is about reducing the number of exported top level names and
  unfoldings, which reduces interface file sizes and reduces the number of
  global/dynamic linker symbols.
  
  Also accept the changed test output and metric decreases.
  
  Tests that record the phase output for type checking or for simplifier
  end up with different output: the generated bindings now have an
  Inline [~] annotation, and many top level names are now local rather
  than module-prefixed for export.
  
  Also accept the numerous metric decreases in compile_time/bytes
  allocated, and a few in compile_time/max_bytes_used.
  
  There's also one instance of a decrease in runtime/max_bytes_used but
  it's a ghci-way test and so presumably the reason is that it loads
  smaller .hi files and/or links fewer symbols.
  
  -------------------------
  Metric Decrease:
      CoOpt_Singletons
      MultiLayerModulesTH_OneShot
      MultilineStringsPerf
      T10421
      T10547
      T12150
      T12227
      T12234
      T12425
      T13035
      T13056
      T13253
      T13253-spj
      T15304
      T15703
      T16875
      T17836b
      T17977b
      T18140
      T18223
      T18282
      T18304
      T18698a
      T18698b
      T18730
      T18923
      T20049
      T21839c
      T24471
      T24582
      T24984
      T3064
      T4029
      T5030
      T5642
      T5837
      T6048
      T9020
      T9198
      T9961
      TcPlugin_RewritePerf
      WWRec
      hard_hole_fits
      mhu-perf
  -------------------------
  

• 67df5161
  by Duncan Coutts at 2026-03-09T12:08:35-04:00

  Add documentation Note [NOINLINE on generated Typeable bindings]
  
  and refer to it from the code and existing documentation.
  

• c4ad6167
  by Duncan Coutts at 2026-03-09T12:08:35-04:00

  Switch existing note to "named wrinkle" style, (GPT1)..(GPT7)
  
  GPT = Grand plan for Typeable
  

• dc84f8e2
  by Cheng Shao at 2026-03-09T12:09:21-04:00

  ci: only build deb13 for validate pipeline aarch64-linux jobs
  
  This patch drops the redundant aarch64-linux deb12 job from validate pipelines
  and only keeps deb13; it's still built in nightly/release pipelines. Closes #27004.
  

• 23a50772
  by Rajkumar Natarajan at 2026-03-10T14:11:37-04:00

  chore: Merge GHC.Internal.TH.Quote into GHC.Internal.TH.Monad
  
  Move the QuasiQuoter datatype from GHC.Internal.TH.Quote to
  GHC.Internal.TH.Monad and delete the Quote module.
  
  Update submodule template-haskell-quasiquoter to use the merged
  upstream version that imports from the correct module.
  
  Co-authored-by: Cursor <cursoragent@cursor.com>
  

• a2bb6fc3
  by Simon Jakobi at 2026-03-10T14:12:23-04:00

  Add regression test for #16122
  

• 604e1180
  by Cheng Shao at 2026-03-11T15:00:42-04:00

  hadrian: remove the broken bench flavour
  
  This patch removes the bench flavour from hadrian which has been
  broken for years and not used for actual benchmarking (for which
  `perf`/`release` is used instead). Closes #26825.
  

• c3e64915
  by Simon Jakobi at 2026-03-11T15:01:31-04:00

  Add regression test for #18186
  
  The original TypeInType language extension is replaced with
  DataKinds+PolyKinds for compatibility.
  
  Closes #18186.
  

• 664996c7
  by Andreas Klebinger at 2026-03-11T15:02:16-04:00

  Bump nofib submodule.
  
  We accrued a number of nofib fixes we want to have here.
  

• 517cf64e
  by Simon Jakobi at 2026-03-11T15:03:03-04:00

  Add regression test for #15907
  
  Closes #15907.
  

• fff362cf
  by Simon Jakobi at 2026-03-11T15:03:49-04:00

  Ensure T14272 is run in optasm way
  
  Closes #16539.
  

• ec81ec2c
  by Simon Jakobi at 2026-03-11T15:03:49-04:00

  Add regression test for #24632
  
  Closes #24632.
  

• cefec47b
  by Simon Jakobi at 2026-03-11T15:03:50-04:00

  Fix module name of T9675: T6975 -> T9675
  

• d3690ae8
  by Andreas Klebinger at 2026-03-11T15:04:31-04:00

  User guide: Clarify phase control on INLINEABLE[foo] pragmas.
  
  Fixes #26851
  

• e7054934
  by Simon Jakobi at 2026-03-11T15:05:16-04:00

  Add regression test for #12694
  
  Closes #12694.
  

• 4756d9f6
  by Simon Jakobi at 2026-03-11T15:05:16-04:00

  Add regression test for #16275
  
  Closes #16275.
  

• 34b7e2c1
  by Simon Jakobi at 2026-03-11T15:05:16-04:00

  Add regression test for #14908
  
  Closes #14908.
  

• 4243db3d
  by Simon Jakobi at 2026-03-11T15:05:16-04:00

  Add regression test for #14151
  
  Closes #14151.
  

• 0e9f1453
  by Simon Jakobi at 2026-03-11T15:05:16-04:00

  Add regression test for #12640
  
  Closes #12640.
  

• ae606c7f
  by Simon Jakobi at 2026-03-11T15:05:16-04:00

  Add regression test for #15588
  
  Closes #15588.
  

• 5a38ce4e
  by Simon Jakobi at 2026-03-11T15:05:16-04:00

  Add regression test for #9445
  
  Closes #9445.
  

• d054b467
  by Cheng Shao at 2026-03-11T15:05:59-04:00

  compiler: implement string interning logic for BCONPtrFS
  
  This patch adds a `FastStringEnv`-based cache of `MallocStrings`
  requests to `Interp`, so that when we load bytecode with many
  breakpoints that share the same module names & unit ids, we reuse the
  allocated remote pointers instead of issuing duplicte `MallocStrings`
  requests and bloating the C heap. Closes #26995.
  

• b85a0293
  by Simon Jakobi at 2026-03-11T15:06:41-04:00

  Add perf test for #1216
  
  Closes #1216.
  

• cd7f7420
  by Sylvain Henry at 2026-03-11T15:07:58-04:00

  JS: check that tuple constructors are linked (#23709)
  
  Test js-mk_tup was failing before because tuple constructors weren't
  linked in. It's no longer an issue after the linker fixes.
  

• d57f01a4
  by Matthew Pickering at 2026-03-11T15:08:40-04:00

  testsuite: Add test for foreign import prim with unboxed tuple return
  
  This commit just adds a test that foreign import prim works with unboxed
  sums.
  

• 23d111ce
  by Matthew Pickering at 2026-03-11T15:08:41-04:00

  Return a valid pointer in advanceStackFrameLocationzh
  
  When there is no next stack chunk, `advanceStackFrameLocationzh` used to
  return NULL in the pointer-typed StackSnapshot# result slot.
  
  Even though the caller treats that case as "no next frame", the result is
  still materialized in a GC-visible pointer slot. If a GC observes the raw
  NULL there, stack decoding can crash.
  
  Fix this by ensuring the dead pointer slot contains a valid closure
  pointer. Also make the optional result explicit by returning an unboxed
  sum instead of a tuple with a separate tag.
  
  Fixes #27009
  

• 4c58a3ae
  by Cheng Shao at 2026-03-11T15:09:22-04:00

  hadrian: build profiled dynamic objects with -dynamic-too
  
  This patch enables hadrian to build profiled dynamic objects with
  `-dynamic-too`, addressing a build parallelism bottleneck in release
  pipelines. Closes #27010.
  

• 870243e4
  by Zubin Duggal at 2026-03-12T17:33:28+05:30

  DmdAnal: Take stable unfoldings into account when determining argument demands
  
  Previously, demand analysis only looked at the RHS to compute argument demands.
  If the optimised RHS discarded uses of an argument that the stable unfolding
  still needed, it would be incorrectly marked absent. Worker/wrapper would then
  replace it with LitRubbish, and inlining the stable unfolding would use the
  rubbish value, causing a segfault.
  
  To fix, we introduce addUnfoldingDemands which analyses the stable unfolding
  with dmdAnal and combines its DmdType with the RHS's via the new `maxDmdType`
  which combines the demands of the stable unfolding with the rhs, so we can avoid
  any situation where we give an absent demand to something which is still used
  by the stable unfolding.
  
  Fixes #26416.
  

• 669d09f9
  by Cheng Shao at 2026-03-13T15:06:07-04:00

  hadrian: remove redundant library/rts ways definitions from stock flavours
  
  This patch removes redundant library/rts ways definitions from stock
  flavours in hadrian; they can be replaced by applying appropriate
  filters on `defaultFlavour`.
  

• a27dc081
  by Teo Camarasu at 2026-03-13T15:06:51-04:00

  ghc-internal: move bits Weak of finalizer interface to base
  
  We move parts of the Weak finalizer interface to `base` only the parts
  that the RTS needs to know about are kept in `ghc-internal`.
  
  This lets us then prune our imports somewhat and get rid of some SOURCE imports.
  
  Resolves #26985
  

• 6eef855b
  by Sylvain Henry at 2026-03-13T15:08:18-04:00

  Stg/Unarise: constant-folding during unarisation (#25650)
  
  When building an unboxed sum from a literal argument, mkUbxSum
  previously emitted a runtime cast via `case primop [lit] of var -> ...`.
  This wrapper prevented GHC from recognising the result as a static
  StgRhsCon, causing top-level closures to be allocated as thunks instead
  of being statically allocated.
  
  Fix: try to perform the numeric literal cast at compile time using
  mkLitNumberWrap (wrapping semantics). If successful, return the cast
  literal directly with an identity wrapper (no case expression). The
  runtime cast path is kept as fallback for non-literal arguments.
  
  Test: codeGen/should_compile/T25650
  

• 905f8723
  by Simon Jakobi at 2026-03-13T15:09:09-04:00

  Add regression test for #2057
  
  Test that GHC stops after an interface-file error instead of
  continuing into the linker.
  
  The test constructs a stale package dependency on purpose. `pkgB` is compiled
  against one version of package `A`, then the same unit id is replaced by an
  incompatible build of `A`. When `Main` imports `B`, GHC has to read `B.hi`,
  finds an unfolding that still mentions the old `A`, and should fail while
  loading interfaces.
  
  Closes #2057.
  
  Assisted-by: Codex
  

• a13245a9
  by Sylvain Henry at 2026-03-13T15:10:06-04:00

  JS: fix recompilation avoidance (#23013)
  
  - we were checking the mtime of the *.jsexe directory, not of a file
  - we were not computing the PkgsLoaded at all
  

• 07442653
  by Cheng Shao at 2026-03-13T15:10:51-04:00

  hadrian: bump index state & bootstrap plans
  
  This patch bumps hadrian index state & bootstrap plans:
  
  - The updated index state allows bootstrapping from 9.14 without cabal
    allow-newer hacks
  - The updated bootstrap plans all contain shake-0.19.9 containing
    important bugfix, allowing a subsequent patch to bump shake bound to
    ensure the bugfix is included
  - ghc 9.14.1 bootstrap plan is added
  

• fdc1dbad
  by Cheng Shao at 2026-03-13T15:10:51-04:00

  ci: add ghc 9.14.1 to bootstrap matrix
  
  This patch adds ghc 9.14.1 to bootstrap matrix, so that we test
  bootstrapping from ghc 9.14.1.
  

• 91916079
  by Sylvain Henry at 2026-03-13T15:11:43-04:00

  T17912: wait for opener thread to block before killing it (#24739)
  
  Instead of a fixed 1000ms delay, poll threadStatus until the opener
  thread is in BlockedOnForeignCall, ensuring killThread only fires once
  the thread is provably inside the blocking open() syscall. This prevents
  the test from accidentally passing on Windows due to scheduling races.
  

• baa4ebb4
  by Cheng Shao at 2026-03-13T15:12:26-04:00

  template-haskell: fix redundant import in Language.Haskell.TH.Quote
  
  This patch fixes a redundant import in `Language.Haskell.TH.Quote`
  that causes a ghc build failure when bootstrapping from 9.14 with
  validate flavours. Fixes #27014.
  

• 02e68a86
  by Brandon Simmons at 2026-03-13T15:13:19-04:00

  Add a cumulative gc_sync_elapsed_ns counter to GHC.Internal.Stats
  
  This makes it possible to get an accurate view of time spent in sync
  phase when using prometheus-style sampling. Previously this was only
  available for the most recent GC.
  
  This intentionally leaves GHC.Stats API unchanged since it is marked as
  deprecated, and API changes there require CLC approval.
  
  Fixes #26944
  

• a18fa3c1
  by Cheng Shao at 2026-03-14T05:12:14-04:00

  configure: make $LLVMAS default to $CC when $CcLlvmBackend is YES
  
  This patch changes the $LLVMAS detection logic in configure so that
  when it's not manually specified by the user, it defaults to $CC if
  $CcLlvmBackend is YES. It's a more sensible default than auto-detected
  clang from the environment, especially when cross-compiling, $CC as
  the cross target's LLVM assembler is more compatible with the use case
  than the system-wide clang. Fixes #26769.
  

• 3774086e
  by Matthew Pickering at 2026-03-14T05:13:00-04:00

  exceptions: annotate onException continuation with WhileHandling
  
  Before this patch, an exception thrown in the `onException` handler
  would loose track of where the original exception was thrown.
  
  ```
  import Control.Exception
  
  main :: IO ()
  main = failingAction `onException` failingCleanup
    where
      failingAction = throwIO (ErrorCall "outer failure")
      failingCleanup = throwIO (ErrorCall "cleanup failure")
  ```
  
  would report
  
  ```
  T28399: Uncaught exception ghc-internal:GHC.Internal.Exception.ErrorCall:
  
  cleanup failure
  
  HasCallStack backtrace:
    throwIO, called at T28399.hs:<line>:<column> in <package-id>:Main
  ```
  
  notice that the "outer failure" exception is not present in the error
  message.
  
  With this patch, any exception thrown is in the handler is annotated
  with WhileHandling. The resulting message looks like
  
  ```
  T28399: Uncaught exception ghc-internal:GHC.Internal.Exception.ErrorCall:
  
  cleanup failure
  
  While handling outer failure
  
  HasCallStack backtrace:
    throwIO, called at T28399.hs:7:22 in main:Main
  ```
  
  CLC Proposal: https://github.com/haskell/core-libraries-committee/issues/397
  
  Fixes #26759
  

• 63ae8eb3
  by Andreas Klebinger at 2026-03-14T05:13:43-04:00

  Fix missing profiling header for origin_thunk frame.
  
  Fixes #27007
  

• 213d2c0e
  by Cheng Shao at 2026-03-14T05:14:28-04:00

  ci: fix ci-images revision
  
  The current ci-images revision was a commit on the WIP branch of
  https://gitlab.haskell.org/ghc/ci-images/-/merge_requests/183, and
  it's not on the current ci-images master branch. This patch fixes the
  image revision to use the current tip of ci-images master.
  

• fc2b083f
  by Andreas Klebinger at 2026-03-14T05:15:14-04:00

  Revert "hadrian/build-cabal: Better respect and utilize -j"
  
  This reverts commit eab3dbba79650e6046efca79133b4c0a5257613d.
  
  While it's neat this currently isn't well supported on all platforms.
  
  It's time will come, but for now I'm reverting this to avoid issues for
  users on slightly unconvential platforms.
  
  This will be tracked at #26977.
  

• 12a706cf
  by Cheng Shao at 2026-03-14T16:37:54-04:00

  base: fix redundant imports in GHC.Internal.Weak.Finalize
  
  This patch fixes redundant imports in GHC.Internal.Weak.Finalize that
  causes a regression in bootstrapping head from 9.14 with validate
  flavours. Fixes #27026.
  

• b5d39cad
  by Matthew Pickering at 2026-03-14T16:38:37-04:00

  Use explicit syntax rather than pure
  

• 43638643
  by Andreas Klebinger at 2026-03-15T18:15:48-04:00

  Configure: Fix check for --target support in stage0 CC
  
  The check FP_PROG_CC_LINKER_TARGET used $CC unconditionally to check for
  --target support. However this fails for the stage0 config where the C
  compiler used is not $CC but $CC_STAGE0.
  
  Since we already pass the compiler under test into the macro I simply
  changed it to use that instead.
  
  Fixes #26999
  

• 18fd0df6
  by Simon Hengel at 2026-03-15T18:16:33-04:00

  Fix typo in recursive_do.rst

• 86bd9bfc
  by fendor at 2026-03-17T23:46:09-04:00

  Introduce `-fimport-loaded-targets` GHCi flag
  
  This new flag automatically adds all loaded targets to the GHCi session
  by adding an `InteractiveImport` for the loaded targets.
  
  By default, this flag is disabled, as it potentially increases memory-usage.
  
  This interacts with the flag `-fno-load-initial-targets` as follows:
  
  * If no module is loaded, no module is added as an interactive import.
  * If a reload loads up to a module, all loaded modules are added as
    interactive imports.
  * Unloading modules removes them from the interactive context.
  
  Fixes #26866 by rendering the use of a `-ghci-script` to achieve the
  same thing redundant.
  

• e3d4c1bb
  by mniip at 2026-03-17T23:47:03-04:00

  ghc-internal: Remove GHC.Internal.Data.Eq
  
  It served no purpose other than being a re-export.
  

• 6f4f6cf0
  by mniip at 2026-03-17T23:47:03-04:00

  ghc-internal: Refine GHC.Internal.Base imports
  
  Removed re-exports from GHC.Internal.Base. This reveals some modules
  that don't actually use anything *defined* in GHC.Internal.Base, and
  that can be pushed down a little in the import graph.
  
  Replaced most imports of GHC.Internal.Base with non-wildcard imports
  from modules where the identifiers are actually defined.
  
  Part of #26834
  
  Metric Decrease:
      T5321FD
  

• 7fb51f54
  by mangoiv at 2026-03-17T23:48:00-04:00

  ci: clone, don't copy when creating the cabal cache
  
  Also removed WINDOWS_HOST variable detected via uname - we now just
  check whether the CI job has windows in its name. This works because we
  only ever care about it if the respective job is not a cross job. We
  also statically detect darwin cross jobs in the same way. We only ever have
  darwin -> darwin cross jobs so this is enough to detect the host
  reliably.
  

• f8817879
  by mangoiv at 2026-03-17T23:48:44-04:00

  ci: mark size_hello_artifact fragile on darwin x86
  
  The size of the x86_64 hello artifact is not stable which results in flaky testruns.
  
  Resolves #26814
  

• e34cb6da
  by Adam Gundry at 2026-03-20T12:20:00-04:00

  ghci: Mention active language edition in startup banner
  
  Per GHC proposal 632, this makes the GHCi startup banner include
  the active language edition, plus an indication of whether this
  was the default (as opposed to being explicitly selected via an
  option such as `-XGHC2024`). For example:
  
  ```
  $ ghci
  GHCi, version 9.14.1: https://www.haskell.org/ghc/  :? for help
  Using default language edition: GHC2024
  ghci>
  ```
  
  Fixes #26037.
  

• 52c3e6ba
  by sheaf at 2026-03-20T12:21:09-04:00

  Improve incomplete record selector warnings
  
  This commit stops GHC from emitting spurious incomplete record selector
  warnings for bare selectors/projections such as .fld
  
  There are two places we currently emit incomplete record selector
  warnings:
  
    1. In the desugarer, when we see a record selector or an occurrence
       of 'getField'. Here, we can use pattern matching information to
       ensure we don't give false positives.
    2. In the typechecker, which might sometimes give false positives but
       can emit warnings in cases that the pattern match checker would
       otherwise miss.
  
  This is explained in Note [Detecting incomplete record selectors]
  in GHC.HsToCore.Pmc.
  
  Now, we obviously don't want to emit the same error twice, and generally
  we prefer (1), as those messages contain fewer false positives. So we
  suppress (2) when we are sure we are going to emit (1); the logic for
  doing so is in GHC.Tc.Instance.Class.warnIncompleteRecSel,
  and works by looking at the CtOrigin.
  
  Now, the issue was that this logic handled explicit record selectors as
  well as overloaded record field selectors such as "x.r" (which turns
  into a simple GetFieldOrigin CtOrigin), but it didn't properly handle
  record projectors like ".fld" or ".fld1.fld2" (which result in other
  CtOrigins such as 'RecordFieldProjectionOrigin').
  
  To solve this problem, we re-use the 'isHasFieldOrigin' introduced in
  fbdc623a (slightly adjusted).
  
  On the way, we also had to update the desugarer with special handling
  for the 'ExpandedThingTc' case in 'ds_app', to make sure that
  'ds_app_var' sees all the type arguments to 'getField' in order for it
  to indeed emit warnings like in (1).
  
  Fixes #26686
  

• 309d7e87
  by Cheng Shao at 2026-03-20T12:21:53-04:00

  rts: opportunistically grow the MutableByteArray# in-place in resizeMutableByteArray#
  
  Following !15234, this patch improves `resizeMutableByteArray#` memory
  efficiency by growing the `MutableByteArray#` in-place if possible,
  addressing an old todo comment here. Also adds a new test case
  `resizeMutableByteArrayInPlace` that stresses this behavior.
  

• 7d4ef162
  by Matthew Craven at 2026-03-20T12:22:47-04:00

  Change representation of floating point literals
  
  This commit changes the representation of floating point literals
  throughough the compiler, in particular in Core and Cmm.
  The Rational type is deficient for this purpose, dealing poorly
  with NaN, +/-Infinity, and negative zero. Instead, the new module
  GHC.Types.Literal.Floating uses the host Float/Double type to represent
  NaNs, infinities and negative zero. It also contains a Rational
  constructor, for the benefit of -fexcess-precision.
  
  Other changes:
  
    - Remove Note [negative zero] and related code
      This also removes the restrictions on constant-folding of division
      by zero, and should make any problems with NaN/Infinity more obvious.
  
    - Use -0.0 as the additive identity for Core constant folding rules
      for floating-point addition, fixing #21227.
  
    - Manual worker-wrapper for GHC.Float.rationalToDouble. This is
      intended to prevent the compiler's WW on this function from
      interfering with constant-folding. This change means that we now
      avoid allocating a box for the result of a 'realToFrac' call in
      T10359.
  
    - Combine floatDecodeOp and doubleDecodeOp.
      This change also fixes a bug in doubleDecodeOp wherein it
      would incorrectly produce an Int# instead of an Int64#
      literal for the mantissa component with 64-bit targets.
  
    - Use Float/Double for assembly immediates, and update the X86 and
      PowerPC backends to properly handle special values such as NaN and
      infinity.
  
    - Allow 'rational_to' to handle zero denominators, fixing a
      TODO in GHC.Core.Opt.ConstantFold.
  
  Fixes #8364 #9811 #18897 #21227
  Progress towards #26919
  
  Metric Decrease:
      T10359
  
  Co-authored-by: sheaf <sam.derbyshire@gmail.com>
  
  -------------------------
  Metric Decrease:
      T1969
      T5321FD
  -------------------------
  

• 80e2dd4f
  by Zubin Duggal at 2026-03-20T12:23:33-04:00

  compiler/ffi: Collapse void pointer chains in capi wrappers
  
  New gcc/clang treat -Wincompatible-pointer-types as an error by
  default. Since C only allows implicit conversion from void*, not void**,
  capi wrappers for functions taking e.g. abstract** would fail to compile
  when the Haskell type Ptr (Ptr Abstract) was naively translated to void**.
  
  Collapse nested void pointers to a single void* when the pointee type
  has no known C representation.
  
  Fixes #26852
  

• 1c50bd7b
  by Luite Stegeman at 2026-03-20T12:24:37-04:00

  Move some functions related to pointer tagging to a separate module
  

• bfd7aafd
  by Luite Stegeman at 2026-03-20T12:24:37-04:00

  Branchless unpacking for enumeration types
  
  Change unpacking for enumeration types to go to Word8#/Word16#/Word#
  directly instead of going through an intermediate unboxed sum. This
  allows us to do a branchless conversion using DataToTag and TagToEnum.
  
  Fixes #26970
  

• 72b20fc0
  by Luite Stegeman at 2026-03-20T12:25:30-04:00

  bytecode: Carefully SLIDE off the end of a stack chunk
  
  The SLIDE bytecode instruction was not checking for stack chunk
  boundaries and could corrupt the stack underflow frame, leading
  to crashes.
  
  We add a check to use safe writes if we cross the chunk boundary
  and also handle stack underflow if Sp is advanced past the underflow
  frame.
  
  fix #27001
  

• 2e22b43c
  by Cheng Shao at 2026-03-20T12:26:14-04:00

  ghci: serialize BCOByteArray buffer directly when possible
  
  This patch changes the `Binary` instances of `BCOByteArray` to
  directly serialize the underlying buffer when possible, while also
  taking into account the issue of host-dependent `Word` width. See
  added comments and amended `Note [BCOByteArray serialization]` for
  detailed explanation. Closes #27020.
  

• 89d9ba37
  by Sylvain Henry at 2026-03-20T12:27:34-04:00

  JS: replace BigInt with Number arithmetic for 32/64-bit quot/rem (#23597)
  
  Replace BigInt-based implementations of quotWord32, remWord32,
  quotRemWord32, quotRem2Word32, quotWord64, remWord64, quotInt64, and
  remInt64 with pure Number (double/integer) arithmetic to avoid the
  overhead of BigInt promotion.
  

• ae4ddd60
  by Sylvain Henry at 2026-03-20T12:28:28-04:00

  Core: add constant-folding rules for Addr# eq/ne (#18032)
  

• 3e767f98
  by Matthew Pickering at 2026-03-20T12:29:11-04:00

  Use OsPath rather than FilePath in Downsweep cache
  
  This gets us one step closure to uniformly using `OsPath` in the
  compiler.
  

• 2c57de29
  by Cheng Shao at 2026-03-20T12:29:55-04:00

  hadrian: fix ghc-in-ghci flavour stage0 shared libraries
  
  This patch fixes missing stage0 shared libraries in hadrian
  ghc-in-ghci flavour, which was accidentally dropped in
  669d09f950a6e88b903d9fd8a7571531774d4d5d and resulted in a regression
  in HLS support on linux/macos. Fixes #27057.
  

• 5b1be555
  by Sylvain Henry at 2026-03-20T12:30:48-04:00

  JS: install rts/Types.h header file (#27033)
  
  It was an omission, making HsFFI.h not usable with GHC using the JS
  backend.
  

• b883f08f
  by Cheng Shao at 2026-03-20T12:31:33-04:00

  hadrian: don't compile RTS with -Winline
  
  This patch removes `-Winline` from cflags when compiling the RTS,
  given that:
  
  1. It generates a huge pile of spam and hurts developer experience
  2. Whether inlining happens is highly dependent on toolchains,
     flavours, etc, and it's not really an issue to fix if inlining
     doesn't happen; it's a hint to the C compiler anyway.
  
  Fixes #27060.
  

• 333387d6
  by Cheng Shao at 2026-03-20T12:31:33-04:00

  hadrian: compile libffi-clib with -Wno-deprecated-declarations
  
  This patch adds `-Wno-deprecated-declarations` to cflags of
  `libffi-clib`, given that it produces noise at compile-time that
  aren't really our issue to fix anyway, it's from vendored libffi
  source code.
  

• 67c47771
  by Rodrigo Mesquita at 2026-03-20T12:32:17-04:00

  Expose decodeStackWithIpe from ghc-experimental
  
  This decoding is useful to the debugger and it wasn't originally
  exported as an oversight.
  

• 18513365
  by Matthew Pickering at 2026-03-21T04:43:26-04:00

  Add support for custom external interpreter commands
  
  It can be useful for GHC API clients to implement their own external
  interpreter commands.
  
  For example, the debugger may want an efficient way to inspect the
  stacks of the running threads in the external interpreter.
  

• 4636d906
  by mangoiv at 2026-03-21T04:44:10-04:00

  ci: remove obsolete fallback for old debian and ubuntu versions
  

• 2e3a2805
  by mangoiv at 2026-03-21T04:44:10-04:00

  ci: drop ubuntu 18 and 20
  
  Ubuntu 18 EOL: May 2023
  Ubuntu 20 EOL: May 2025
  
  We should probably not make another major release supporting these platforms.
  
  Also updates the generator script.
  
  Resolves #25876
  

• de54e264
  by Cheng Shao at 2026-03-21T17:52:08+01:00

  rts: fix -Wcompare-distinct-pointer-types errors
  
  This commit fixes `-Wcompare-distinct-pointer-types` errors in the RTS
  which should have been caught by the `validate` flavour but was
  warnings in CI due to the recent `+werror` regression.
  

• b9bd73de
  by Cheng Shao at 2026-03-21T17:52:08+01:00

  ghc-internal: fix unused imports
  
  This commit fixes unused imports in `ghc-internal` which should have
  been caught by the `validate` flavour but was warnings in CI due to
  the recent `+werror` regression. Fixes #26987 #27059.
  

• da946a16
  by Cheng Shao at 2026-03-21T17:03:51+00:00

  ghci: fix unused imports
  
  This commit fixes unused imports in `ghci` which should have been
  caught by the `validate` flavour but was warnings in CI due to the
  recent `+werror` regression. Fixes #26987 #27059.
  

• 955b1cf8
  by Cheng Shao at 2026-03-21T17:03:51+00:00

  compiler: fix unused imports in GHC.Tc.Types.Origin
  
  This commit fixes unused imports in `GHC.Tc.Types.Origin` which should
  have been caught by the `validate` flavour but was warnings in CI due
  to the recent `+werror` regression. Fixes #27059.
  

• 3b1aeb50
  by Cheng Shao at 2026-03-21T17:03:51+00:00

  hadrian: fix missing +werror in validate flavour
  
  This patch fixes missing `+werror` in validate flavour, which was an
  oversight in bb3a2ba1eefadf0b2ef4f39b31337a23eec67f29. Fixes #27066.
  

• 44f118f0
  by Cheng Shao at 2026-03-22T04:54:01-04:00

  ci: bump CACHE_REV and add the missing reminder
  
  This patch bumps `CACHE_REV` to address recent `[Cabal-7159]` CI
  errors due to stale cabal cache on some runners, and also adds a
  reminder to remind future maintainers. Fixes #27075.
  

• 2a218737
  by ARATA Mizuki at 2026-03-23T11:11:39-04:00

  Add 128-bit SIMD support to AArch64 NCG
  
  Changes:
  
  - Add `Format` field to vector-capable instructions.
    These instructions will emit `vN.4s` (for example) as a operand.
  - Additional constructors for `Operand`:
    `OpVecLane` represents a vector lane and will be emitted as `vN.<width>[<index>]` (`vN.s[3]` for example).
    `OpScalarAsVec` represents a scalar, but printed as a vector lane like `vN.<width>[0]` (`vN.s[0]` for example).
  - Integer quot/rem are implemented in C, like x86.
  
  Closes #26536
  
  Metric Increase:
      T3294
  

• 5d6e2be9
  by ARATA Mizuki at 2026-03-23T11:11:39-04:00

  AArch64 NCG: Improve code generation for floating-point and vector constants
  
  Some floating-point constants can be directly encoded using the FMOV instruction.
  Similarly, a class of vectors with same values can be encoded using FMOV, MOVI, or MVNI.
  

• c6d262aa
  by Simon Jakobi at 2026-03-23T11:12:22-04:00

  Add regression test for #13729
  
  Closes #13729.
  

• aa5dfe67
  by Sylvain Henry at 2026-03-26T03:48:56-04:00

  Check that shift values are valid
  
  In GHC's codebase in non-DEBUG builds we silently substitute shiftL/R
  with unsafeShiftL/R for performance reasons. However we were not
  checking that the shift value was valid for unsafeShiftL/R, leading to
  wrong computations, but only in non-DEBUG builds.
  
  This patch adds the necessary checks and reports an error when a wrong
  shift value is passed.
  

• c8a7b588
  by Sylvain Henry at 2026-03-26T03:48:56-04:00

  Implement basic value range analysis (#25718)
  
  Perform basic value range analysis to try to determine at compile time
  the result of the application of some comparison primops (ltWord#, etc.).
  
  This subsumes the built-in rewrite rules used previously to check if one
  of the comparison argument was a bound (e.g. (x :: Word8) <= 255 is
  always True). Our analysis is more powerful and handles type
  conversions: e.g. word8ToWord x <= 255 is now detected as always True too.
  
  We also use value range analysis to filter unreachable alternatives in
  case-expressions. To support this, we had to allow case-expressions for
  primitive types to not have a DEFAULT alternative (as was assumed before
  and checked in Core lint).
  

• a5ec467e
  by ARATA Mizuki at 2026-03-26T03:49:49-04:00

  rts: Align stack to 64-byte boundary in StgRun on x86
  
  When LLVM spills AVX/AVX-512 vector registers to the stack, it requires
  32-byte (__m256) or 64-byte (__m512) alignment. If the stack is not
  sufficiently aligned, LLVM inserts a realignment prologue that reserves
  %rbp as a frame pointer, conflicting with GHC's use of %rbp as an STG
  callee-saved register and breaking the tail-call-based calling convention.
  
  Previously, GHC worked around this by lying to LLVM about the stack
  alignment and rewriting aligned vector loads/stores (VMOVDQA, VMOVAPS)
  to unaligned ones (VMOVDQU, VMOVUPS) in the LLVM Mangler. This had two
  problems:
  
  - It did not extend to AVX-512, which requires 64-byte alignment. (#26595)
  - When Haskell calls a C function that takes __m256/__m512 arguments on
    the stack, the callee requires genuine alignment, which could cause a
    segfault. (#26822)
  
  This patch genuinely aligns the stack to 64 bytes in StgRun by saving
  the original stack pointer before alignment and restoring it in
  StgReturn. We now unconditionally advertise 64-byte stack alignment to
  LLVM for all x86 targets, making rewriteAVX in the LLVM Mangler
  unnecessary. STG_RUN_STACK_FRAME_SIZE is increased from 48 to 56 bytes
  on non-Windows x86-64 to store the saved stack pointer.
  
  Closes #26595 and #26822
  
  Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
  

• 661da815
  by Teo Camarasu at 2026-03-26T03:50:33-04:00

  ghc-internal: Float Generics to near top of module graph
  
  We remove GHC.Internal.Generics from the critical path of the
  `ghc-internal` module graph. GHC.Internal.Generics used to be in the
  middle of the module graph, but now it is nearer the top (built later).
  This change thins out the module graph and allows us to get rid of the
  ByteOrder hs-boot file.
  
  We implement this by moving Generics instances from the module where the
  datatype is defined to the GHC.Internal.Generics module. This trades off
  increasing the compiled size of GHC.Internal.Generics with reducing the
  dependency footprint of datatype modules.
  
  Not all instances are moved to GHC.Internal.Generics. For instance,
  `GHC.Internal.Control.Monad.Fix` keeps its instance as it is one of the
  very last modules compiled in `ghc-internal` and so inverting the
  relationship here would risk adding GHC.Internal.Generics back onto the
  critical path.
  We also don't change modules that are re-exported from the `template-haskell` or `ghc-heap`.
  This is done to make it easy to eventually move `Generics` to `base`
  once something like #26657 is implemented.
  
  Resolves #26930
  
  Metric Decrease:
      T21839c
  

• 45428f88
  by sheaf at 2026-03-26T03:51:31-04:00

  Avoid infinite loop in deep subsumption
  
  This commit ensures we only unify after we recur in the deep subsumption
  code in the FunTy vs non-FunTy case of GHC.Tc.Utils.Unify.tc_sub_type_deep,
  to avoid falling into an infinite loop.
  
  See the new Wrinkle [Avoiding a loop in tc_sub_type_deep] in
  Note [FunTy vs non-FunTy case in tc_sub_type_deep] in GHC.Tc.Utils.Unify.
  
  Fixes #26823
  
  Co-authored-by: simonpj <simon.peytonjones@gmail.com>
  

• 2823b039
  by Ian Duncan at 2026-03-26T03:52:21-04:00

  AArch64: fix MOVK regUsageOfInstr to mark dst as both read and written
  
  MOVK (move with keep) modifies only a 16-bit slice of the destination
  register, so the destination is both read and written. The register
  allocator must know this to avoid clobbering live values. Update
  regUsageOfInstr to list the destination in both src and dst sets.
  
  No regression test: triggering the misallocation requires specific
  register pressure around a MOVK sequence, which is difficult to
  reliably provoke from Haskell source.
  

• 57b7878d
  by Simon Jakobi at 2026-03-26T03:53:07-04:00

  Add regression test for #12002
  
  Closes #12002.
  

• c8f9df2d
  by Simon Jakobi at 2026-03-26T03:53:07-04:00

  Add regression test for #12046
  
  Closes #12046.
  
  Co-authored-by: Andreas Klebinger <klebinger.andreas@gmx.at>
  

• 615d72ac
  by Simon Jakobi at 2026-03-26T03:53:07-04:00

  Add regression test for #13180
  
  Closes #13180.
  

• 423eebcf
  by Simon Jakobi at 2026-03-26T03:53:07-04:00

  Add regression test for #11141
  
  Closes #11141.
  

• 286849a4
  by Simon Jakobi at 2026-03-26T03:53:07-04:00

  Add regression test for #11505
  
  Closes #11505.
  

• 7db149d9
  by Simon Jakobi at 2026-03-26T03:53:07-04:00

  Add regression perf test for #13820
  
  Closes #13820.
  

• e73c4adb
  by Simon Jakobi at 2026-03-26T03:53:07-04:00

  Add regression test for #10381
  
  Closes #10381.
  

• 5ebcfb57
  by Benjamin Maurer at 2026-03-26T03:54:02-04:00

  Generate assembly on x86 for word2float (#22252)
  
  We used to emit C function call for MO_UF_Conv primitive.
  Now emits direct assembly instead.
  
  Co-Authored-By: Sylvain Henry <sylvain@haskus.fr>
  Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
  

• 5b550754
  by Matthew Pickering at 2026-03-26T03:54:51-04:00

  rts: forward clone-stack messages after TSO migration
  
  MSG_CLONE_STACK assumed that the target TSO was still owned by the
  capability that received the message. This is not always true: the TSO
  can migrate before the inbox entry is handled.
  
  When that happened, handleCloneStackMessage could clone a live stack from
  the wrong capability and use the wrong capability for allocation and
  performTryPutMVar, leading to stack sanity failures such as
  checkStackFrame: weird activation record found on stack.
  
  Fix this by passing the current capability into
  handleCloneStackMessage, rechecking msg->tso->cap at handling time, and
  forwarding the message if the TSO has migrated. Once ownership matches,
  use the executing capability consistently for cloneStack, rts_apply, and
  performTryPutMVar.
  
  Fixes #27008
  

• ef0a1bd2
  by mangoiv at 2026-03-26T03:55:34-04:00

  release tracking: adopt release tracking ticket from #16816
  

• a7f40fd9
  by mangoiv at 2026-03-26T03:55:34-04:00

  release tracking: add a release tracking ticket
  
  Brings the information in the release tracking ticket up to date with
  https://gitlab.haskell.org/ghc/ghc-hq/-/blob/main/release-management.mkd
  
  Resolves #26691
  

• 161d3285
  by Teo Camarasu at 2026-03-26T03:56:18-04:00

  Revert "Set default eventlog-flush-interval to 5s"
  
  Flushing the eventlog forces a synchronisation of all the capabilities
  and there was a worry that this might lead to a performance cost for
  some highly parallel workloads.
  
  This reverts commit 66b96e2a591d8e3d60e74af3671344dfe4061cf2.
  

• 36eed985
  by Cheng Shao at 2026-03-26T03:57:03-04:00

  ghc-boot: move GHC.Data.SmallArray to ghc-boot
  
  This commit moves `GHC.Data.SmallArray` from the `ghc` library to
  `ghc-boot`, so that it can be used by `ghci` as well:
  
  - The `Binary` (from `ghc`) instance of `SmallArray` is moved to
    `GHC.Utils.Binary`
  - Util functions `replicateSmallArrayIO`, `mapSmallArrayIO`,
    `mapSmallArrayM_`, `imapSmallArrayM_` , `smallArrayFromList` and
    `smallArrayToList` are added
  - The `Show` instance is added
  - The `Binary` (from `binary`) instance is added
  

• fdf828ae
  by Cheng Shao at 2026-03-26T03:57:03-04:00

  compiler: use `Binary` instance of `BCOByteArray` for bytecode objects
  
  This commit defines `Binary` (from `compiler`) instance of
  `BCOByteArray` which serializes the underlying buffer directly, and
  uses it directly in bytecode object serialization. Previously we reuse
  the `Binary` (from `binary`) instance, and this change allows us to
  avoid double-copying via an intermediate `ByteString` when using
  `put`/`get` in `binnary`. Also see added comment for explanation.
  

• 3bf62d0a
  by Cheng Shao at 2026-03-26T03:57:03-04:00

  ghci: use SmallArray directly in ResolvedBCO
  
  This patch makes ghci use `SmallArray` directly in `ResolvedBCO` when
  applicable, making the memory representation more compact and reducing
  marshaling overhead. Closes #27058.
  

• 3d6492ce
  by Wen Kokke at 2026-03-26T03:57:53-04:00

  Fix race condition between flushEventLog and start/endEventLogging.
  
  This commit changes `flushEventLog` to acquire/release the `state_change` mutex to prevent interleaving with `startEventLogging` and `endEventLogging`. In the current RTS, `flushEventLog` _does not_ acquire this mutex, which may lead to eventlog corruption on the following interleaving:
  
  - `startEventLogging` writes the new `EventLogWriter` to `event_log_writer`.
  - `flushEventLog` flushes some events to `event_log_writer`.
  - `startEventLogging` writes the eventlog header to `event_log_writer`.
  
  This causes the eventlog to be written out in an unreadable state, with one or more events preceding the eventlog header.
  
  This commit renames the old function to `flushEventLog_` and defines `flushEventLog` simply as:
  
  ```c
  void flushEventLog(Capability **cap USED_IF_THREADS)
  {
    ACQUIRE_LOCK(&state_change_mutex);
    flushEventLog_(cap);
    RELEASE_LOCK(&state_change_mutex);
  }
  ```
  
  The old function is still needed internally within the compilation unit, where it is used in `endEventLogging` in a context where the `state_change` mutex has already been acquired. I've chosen to mark `flushEventLog_` as static and let other uses of `flushEventLog` within the RTS refer to the new version. There is one use in `hs_init_ghc` via `flushTrace`, where the new locking behaviour should be harmless, and one use in `handle_tick`, which I believe was likely vulnerable to the same race condition, so the new locking behaviour is desirable.
  
  I have not added a test. The behaviour is highly non-deterministic and requires a program that concurrently calls `flushEventLog` and `startEventLogging`/`endEventLogging`. I encountered the issue while developing `eventlog-socket` and within that context have verified that my patch likely addresses the issue: a test that used to fail within the first dozen or so runs now has been running on repeat for several hours.
  

• 7b9a75f0
  by Phil Hazelden at 2026-03-26T03:58:37-04:00

  Fix build with werror on glibc 2.43.
  
  We've been defining `_XOPEN_SOURCE` and `_POSIX_C_SOURCE` to the same
  values as defined in glibc prior to 2.43. But in 2.43, glibc changes
  them to new values, which means we get a warning when redefining them.
  By `#undef`ing them first, we no longer get a warning.
  
  Closes #27076.
  

• fe6e76c5
  by Tobias Haslop at 2026-03-26T03:59:30-04:00

  Fix broken Haddock link to Bifunctor class in description of Functor class
  

• 404b71c1
  by Luite Stegeman at 2026-03-27T04:40:49-04:00

  Fix assert in Interpreter.c
  
  If we skip exactly the number of words on the stack we end up on
  the first word in the next chunk.
  

• a85bd503
  by Luite Stegeman at 2026-03-27T04:40:49-04:00

  Support arbitrary size unboxed tuples in bytecode
  
  This stores the size (number of words on the stack) of the next
  expected tuple in the TSO, ctoi_spill_size field, eliminating
  the need of stg_ctoi_tN frames for each size.
  
  Note: On 32 bit platform there is still a bytecode tuple size
  limit of 255 words on the stack.
  
  Fixes #26946
  

• e2209031
  by Luite Stegeman at 2026-03-27T04:40:49-04:00

  Add specialized frames for small tuples
  
  Small tuples are now returned more efficiently to the interpreter.
  They use one less word of stack space and don't need manipulation
  of the TSO anymore.
  

• b26bb2ea
  by VeryMilkyJoe at 2026-03-27T04:41:38-04:00

  Remove backwards compatibility pattern synonym `ModLocation`
  
  Fixes #24932
  

• 66e5e324
  by Vladislav Zavialov at 2026-03-27T04:42:25-04:00

  Extend HsExpr with the StarIsType syntax (#26587, #26967)
  
  This patch allows kinds of the form `k -> *` and `* -> k` to occur in
  expression syntax, i.e. to be used as required type arguments.
  
  For example:
  
  	{-# LANGUAGE RequiredTypeArguments, StarIsType #-}
  	x1 = f (* -> * -> *)
  	x2 = f (forall k. k -> *)
  	x3 = f ((* -> *) -> Constraint)
  
  Summary of the changes:
  
  * Introduce the HsStar constructor of HsExpr and its extension field XStar.
    It is analogous to HsStarTy in HsType.
  
  * Refactor HsStarTy to store the unicode flag as TokStar, defined as
      type TokStar = EpUniToken "*" "★"  -- similar to TokForall, TokRArrow, etc.
    The token is stored in the extension field and replaces the Bool field.
  
  * Extend the `infixexp2` nonterminal to parse `*` as a direct argument of `->`.
    This is more limited than the full StarIsType syntax, but has the nice
    property of not conflicting with the multiplication operator `a * b`.
  
  Test case: T26967 T26967_tyop
  

• f8de456f
  by Sylvain Henry at 2026-03-27T04:43:22-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.
  
  This is the second attempt at implementing this. The first attempt
  triggered segfaults (#26291) and has been reverted.
  
  Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
  

• fcf092dd
  by Luite Stegeman at 2026-03-27T04:44:17-04:00

  Windows: remove StgAsyncIOResult and fix crash/leaks
  
  In stg_block_async{_void}, a stack slot was reserved for
  an StgAsyncIOResult. This slot would be filled by the IO
  manager upon completion of the async call.
  
  However, if the blocked thread was interrupted by an async
  exception, we would end up in an invalid state:
  
   - If the blocked computation was never re-entered, the
     StgAsyncIOResult would never be freed.
   - If the blocked computation was re-entered, the thread would
     find an unitialized stack slot for the StgAsyncIOResult,
     leading to a crash reading its fields, or freeing the pointer.
  
  We fix this by removing the StgAsyncIOResult altogether and writing
  the result directly to the stack.
  
  Fixes #26341
  

• 05094993
  by Luite Stegeman at 2026-03-27T04:45:12-04:00

  Don't refine DEFAULT alt for unary typeclasses
  
  A non-DEFAULT data alt for a unary typeclass dictionary would
  interfere with Unary Class Magic, leading to segfaults.
  
  fixes #27071
  

• 4ee260cf
  by sheaf at 2026-03-27T04:46:06-04:00

  Fix several oversights in hsExprType
  
  This commit fixes several oversights in GHC.Hs.Syn.Type.hsExprType:
  
    - The 'RecordCon' case was returning the type of the constructor,
      instead of the constructor application. This is fixed by using
      'splitFunTys'.
    - The 'ExplicitTuple' case failed to take into account tuple sections,
      and was also incorrectly handling 1-tuples (e.g. 'Solo') which can
      be constructed using Template Haskell.
    - The 'NegApp' case was returning the type of the negation operator,
      again failing to apply it to the argument. Fixed by using
      'funResultTy'.
    - The 'HsProc' case was computing the result type of the arrow proc
      block, without taking into account the argument type. Fix that by
      adding a new field to 'CmdTopTc' that stores the arrow type, so that
      we can construct the correct result type `arr a b` for
      `proc (pat :: a) -> (cmd :: b)`.
    - The 'ArithSeq' and 'NegApp' cases were failing to take into account
      the result 'HsWrapper', which could e.g. silently drop casts.
      This is fixed by introducing 'syntaxExpr_wrappedFunResTy' which, on
      top of taking the result type, applies the result 'HsWrapper'.
  
  These fixes are validated by the new GHC API test T26910.
  
  Fixes #26910
  

• e97232ce
  by Hai at 2026-03-27T04:47:04-04:00

  Parser.y: avoid looking at token with QualifiedDo
  
  This changes the behavior of 'hintQualifiedDo' so that the supplied
  token is not inspected when the QualifiedDo language extension bit is
  set.
  

• 9831385b
  by Vladislav Zavialov at 2026-03-27T17:22:30-04:00

  Infix holes in types (#11107)
  
  This patch introduces several improvements that follow naturally from
  refactoring HsOpTy to represent the operator as an HsType, aligning it
  with the approach taken by OpApp and HsExpr.
  
  User-facing changes:
  
  1. Infix holes (t1 `_` t2) are now permitted in types, following the
     precedent set by term-level expressions.
  
     Test case: T11107
  
  2. Error messages for illegal promotion ticks are now reported at more
     precise source locations.
  
     Test case: T17865
  
  Internal changes:
  
  * The definition of HsOpTy now mirrors that of OpApp:
  
      | HsOpTy (XOpTy p)  (LHsType p) (LHsType p) (LHsType p)
      | OpApp  (XOpApp p) (LHsExpr p) (LHsExpr p) (LHsExpr p)
  
    This moves us one step closer to unifying HsType and HsExpr.
  
  * Ignoring locations,
      the old pattern match (HsOpTy x prom lhs op rhs)
      is now written as     (HsOpTy x lhs (HsTyVar x' prom op) rhs)
      but we also handle    (HsOpTy x lhs (HsWildCardTy x')    rhs)
  
    Constructors other than HsTyVar and HsWildCardTy never appear
    in the operator position.
  
  * The various definitions across the compiler have been updated to work
    with the new representation, drawing inspiration from the term-level
    pipeline where appropriate.  For example,
  
       ppr_infix_ty       <=> ppr_infix_expr
       get_tyop           <=> get_op
       lookupTypeFixityRn <=> lookupExprFixityRn
             (the latter is factored out from rnExpr)
  
  Test cases: T11107 T17865
  

• 5b6757d7
  by mangoiv at 2026-03-27T17:23:19-04:00

  ci: build i386 non-validate for deb12
  
  This is a small fix that will unlock ghcup metadata to run, i386 debian
  12 was missing as a job.
  

• cf942119
  by Cheng Shao at 2026-03-30T15:24:37-04:00

  ghc-boot: remove unused SizedSeq instances and functions
  
  This commit removes unused `SizedSeq` instances and functions, only
  keeping the bits we need for hpc tick sequence for now.
  

• 22c5b7cc
  by Cheng Shao at 2026-03-30T15:24:38-04:00

  ghci: remove unused GHCi.BinaryArray
  
  This patch removes the unused `GHCi.BinaryArray` module from `ghci`.
  Closes #27108.
  

• 77abb4ab
  by Cheng Shao at 2026-03-30T15:25:21-04:00

  testsuite: mark T17912 as fragile on Windows
  
  T17912 is still fragile on Windows, it sometimes unexpectedly pass in
  CI. This especially strains our already scarce Windows CI runner
  resources. Mark it as fragile on Windows for the time being.
  

• d741a6cc
  by Andreas Klebinger at 2026-03-31T04:39:33-04:00

  Bump minimum shake version for hadrian.
  
  We also add the shake version we want to stack.yaml
  
  Fixes #26884
  

• 5e556f9e
  by Vladislav Zavialov at 2026-03-31T04:40:16-04:00

  Status check for the HsType~HsExpr refactoring (#25121)
  
  Add a test case to track the status of a refactoring project within GHC
  whose goal is to arrive at the following declaration:
  
  	type HsType = HsExpr
  
  The rationale for this is to increase code reuse between the term- and
  type-level code in the compiler front-end (AST, parser, renamer, type checker).
  
  The status report is saved to testsuite/tests/ghc-api/T25121_status.stdout
  and provides useful insights into what needs to happen to make progress on
  the ticket.
  

• acffb1b1
  by fendor at 2026-03-31T04:41:02-04:00

  Extract Binary instances to `GHC.ByteCode.Binary`
  

• e2ea8e25
  by fendor at 2026-03-31T04:41:02-04:00

  Add `seqNonEmpty` for evaluating `NonEmpty a`
  

• 048b00b7
  by fendor at 2026-03-31T04:41:02-04:00

  Record `LinkableUsage` instead of `Linkable` in `LoaderState`
  
  Retaining a ByteCode `Linkable` after it has been loaded retains its
  `UnlinkedBCO`, keeping it alive for the remainder of the program.
  This starts accumulating a lot of `UnlinkedBCO` and memory over time.
  However, the `Linkable` is merely used to later record its usage in
  `mkObjectUsage`, which  is used for recompilation checking.
  
  However, this is incorrect, as the interface file and bytecode objects
  could be in different states, e.g. the interface changes, but the
  bytecode library hasn't changed so we don't need to recompile and vice
  versa.
  
  By computing a `Fingerprint` for the `ModuleByteCode`, and recording it
  in the `LinkableUsage`, we know precisely whether the `ByteCode` object
  on disk is outdated.
  
  Thus, parts of this commit just makes sure that we efficiently compute a
  `Fingerprint` for `ModuleByteCode` and store it in the on-disk
  representation of `ModuleByteCode`.
  
  We change the `LoaderState` to retain `LinkableUsage`, which is smaller
  representation of a `Linkable`. This allows us to free the unneeded
  fields of `Linkable` after linking them.
  
  We declare the following memory invariants that this commit implements:
  
  * No `LinkablePart` should be retained from `LoaderState`.
  * `Linkable`s should be unloaded after they have been loaded.
  
  These invariants are unfortunately tricky to automatically uphold, so we
  are simply documenting our assumptions for now.
  
  We introduce the `linkable-space` test which makes sure that after
  loading, no `DotGBC` or `UnlinkedBCO` is retained.
  
  -------------------------
  Metric Increase:
      MultiLayerModulesTH_OneShot
  -------------------------
  
  We allocate a bit more, but the peak number of bytes doesn't change.
  While a bit unfortunate, accepting the metric increase.
  
  We add multiple new performance measurements where we were able to
  observe the desired memory invariants. Further, we add regression tests
  to validate that the recompilation checker behaves more correct than
  before.
  

• 2d1c1997
  by Simon Jakobi at 2026-03-31T04:41:46-04:00

  Eliminate dictionary-passing in ListMap operations
  
  Mark the ListMap helpers 'INLINABLE' so importing modules can specialise
  the 'TrieMap (ListMap m)' methods and avoid recursive dictionary-passing.
  
  See Note [Making ListMap operations specialisable].
  
  Fixes #27097
  

• ed2c6570
  by Cheng Shao at 2026-03-31T04:42:33-04:00

  testsuite: fix testdir cleanup logic on Windows
  
  testdir cleanup is unreliable on Windows (#13162) and despite existing
  hacks in the driver, new failure mode has occurred. This patch makes
  it print the warning and carry on when failed to clean up a testdir,
  instead of reporting a spurious framework failure. See added comment
  for detailed explanation.
  

• d9388e29
  by Simon Jakobi at 2026-03-31T13:14:59-04:00

  Add regression test for #18177
  
  Closes #18177.
  
  Assisted-by: Codex
  

• 6a10045c
  by mangoiv at 2026-03-31T13:15:43-04:00

  ci: allow metric decrease for two tests on i386
  
  There has been a nightly failure on i386 due to a compiler runtime
  improvement on i386 debian 12. We allow that.
  
  Metric Decrease (test_env='i386-linux-deb12'):
    T12707 T8095
  

• 7fbb4fcb
  by Rodrigo Mesquita at 2026-04-01T12:16:33+00:00

  Bump default language edition to GHC2024
  
  As per the accepted ghc-proposal#632
  
  Fixes #26039
  

• 5ae43275
  by Peng Fan at 2026-04-01T19:01:06-04:00

  NCG/LA64: add cmpxchg and xchg primops
  
  And append some new instructions for LA664 uarch.
  
  Apply fix to cmpxchg-prim by Andreas Klebinger.
  
  Suggestions in https://gitlab.haskell.org/ghc/ghc/-/merge_requests/15515
  

• 8f95534a
  by Duncan Coutts at 2026-04-01T19:01:52-04:00

  Remove signal-based ticker implementations
  
  Fixes issue #27073
  
  All supported platforms should work with the pthreads + nanosleep based
  ticker implementation. This avoids all the problems with using signals.
  
  In practice, all supported platforms were probably using the non-signal
  tickers already, which is probably why we do not get lots of reports
  about deadlocks and other weirdness: we were definately using functions
  that are not async signal safe in the tick handler (such as fflush to
  flussh the eventlog).
  
  Only Solaris was explicitly using the timer_create ticker impl, and even
  Solaris could probably use the pthreads one (if anyone cared: Solaris is
  no longer a Teir 3 supported platform).
  
  Plausibly the only supported platform that this will change will be AIX,
  which should now use the pthreads impl.
  

• 51b32b0d
  by Duncan Coutts at 2026-04-01T19:01:52-04:00

  Tidy up some timer/ticker comments elsewhere
  

• 7562bcd7
  by Duncan Coutts at 2026-04-01T19:01:52-04:00

  Remove now-unused install_vtalrm_handler
  
  Support function used by both of the signal-based ticker
  implementations.
  

• 6da127c7
  by Duncan Coutts at 2026-04-01T19:01:52-04:00

  No longer probe for timer_create in rts/configure
  
  It was only used by the TimerCreate.c ticker impl.
  

• 3fd490fa
  by Duncan Coutts at 2026-04-01T19:01:53-04:00

  Note that rtsTimerSignal is deprecated.
  

• 63099b0f
  by Simon Jakobi at 2026-04-01T19:02:39-04:00

  Add perf test for #13960
  
  Closes #13960.
  

• 58009c14
  by Apoorv Ingle at 2026-04-02T09:51:24+01:00

  Streamline expansions using HsExpansion (#25001)
  
  Notes added [Error Context Stack] [Typechecking by expansion: overview]
  Notes updated Note [Expanding HsDo with XXExprGhcRn] [tcApp: typechecking applications]
  
  -------------------------
  Metric Decrease:
      T9020
  -------------------------
  
  There are 2 key changes:
  
  1. `HsExpand` datatype mediates between expansions
  2. Replace `ErrCtxtM` to a simpler `HsCtxt` that does not depend on a `TidyEnv`
  
  This has some consequences detailed below:
  
  1. `HsExpand` datatype mediates between expansions
     * Simplifies the implementations of `tcExpr` to work on `XExpr`
     * Removes `VACtxt` (and its associated `VAExpansion` and `VACall`) datatype, it is subsumed by simply a `SrcSpan`.
     * Removes the function `addHeadCtxt` as it is now mearly setting a location
     * The function `tcValArgs` does its own argument number management
     * move `splitHsTypes` out of `tcApp`
     * Removes special case of tcBody from `tcLambdaMatches`
     * Removes special case of `dsExpr` for `ExpandedThingTc`
     * Renames `tcMonoExpr` -> `tcMonoLExpr`, `tcMonoExprNC` -> `tcMonoLExpr`
     * Renames `EValArg`, `EValArgQL` fields: `ea_ctxt` -> `ea_loc_span` and `eaql_ctx` -> `eaql_loc_span`
     * Remove `PopErrCtxt` from `XXExprGhcRn`
     * `fun_orig` in tcInstFun depends on the SrcSpan of the head of the application chain (similar to addArgCtxt)
       - it references the application chain head if it is user located, or
        uses the error context stack  as a fallback if it's a generated
        location
     * Make a new variant `GeneratedSrcSpan` in `SrcSpan` for HIEAst Nodes
      - Expressions wrapped around `GeneratedSrcSpan` are ignored and never added to the error context stack
      - In Explicit list expansion `fromListN` is wrapped with a `GeneratedSrcSpan` with `GeneratedSrcSpanDetails` field to store the original srcspan
  
  2. Replace `ErrCtxtM` to a simpler `HsCtxt` that does not depend on a `TidyEnv`
     * Merge `HsThingRn` to `HsCtxt`
     * Landmark Error messages are now just computed on the fly
     * Make HsExpandedRn and HsExpandedTc payload a located HsExpr GhcRn
     * `HsCtxt` are tidied and zonked at the end right before printing
  
  Co-authored-by: simonpj <simon.peytonjones@gmail.com>
  

• bc4b4487
  by Zubin Duggal at 2026-04-03T14:22:27-04:00

  driver: recognise .dyn_o as a valid object file to link if passed on the command line.
  This allows plugins compiled with this suffix to run.
  
  Fixes #24486
  

• 5ebb9121
  by Simon Jakobi at 2026-04-03T14:23:11-04:00

  Add regression test for #16145
  
  Closes #16145.
  

• c1fc1c44
  by Simon Peyton Jones at 2026-04-03T19:56:07-04:00

  Refactor eta-expansion in Prep
  
  The Prep pass does eta-expansion but I found cases where it was
  doing bad things.  So I refactored and simplified it quite a bit.
  
  In the new design
  * There is no distinction between `rhs` and `body`; in particular,
    lambdas can now appear anywhere, rather than just as the RHS of
    a let-binding.
  
  * This change led to a significant simplification of Prep, and
    a more straightforward explanation of eta-expansion. See the new
       Note [Eta expansion]
  
  * The consequences is that CoreToStg needs to handle naked lambdas.
    This is very easy; but it does need a unique supply, which forces
    some simple refactoring.  Having a unique supply to hand is probably
    a good thing anyway.
  

• 21beda2c
  by Simon Peyton Jones at 2026-04-03T19:56:07-04:00

  Clarify Note [Interesting dictionary arguments]
  
  Ticket #26831 ended up concluding that the code for
  GHC.Core.Opt.Specialise.interestingDict was good, but the
  commments were a bit inadequate.
  
  This commit improves the comments slightly.
  

• 3eaac1f2
  by Simon Peyton Jones at 2026-04-03T19:56:07-04:00

  Make inlining a bit more eager for overloaded functions
  
  If we have
     f d = ... (class-op d x y) ...
  we should be eager to inline `f`, because that may change the
  higher order call (class-op d x y) into a call to a statically
  known function.
  
  See the discussion on #26831.
  
  Even though this does a bit /more/ inlining, compile times
  decrease by an average of 0.4%.
  
  Compile time changes:
  
   DsIncompleteRecSel3(normal)     431,786,104  -2.2%
      ManyAlternatives(normal)     670,883,768  -1.6%
      ManyConstructors(normal)   3,758,493,832  -2.6% GOOD
  MultilineStringsPerf(normal)      29,900,576  -2.8%
              T14052Type(ghci)   1,047,600,848  -1.2%
                T17836(normal)     392,852,328  -5.2%
                T18478(normal)     442,785,768  -1.4%
               T21839c(normal)     341,536,992 -14.1% GOOD
                 T3064(normal)     174,086,152  +5.3%  BAD
                 T5631(normal)     506,867,800  +1.0%
        hard_hole_fits(normal)     209,530,736  -1.3%
   info_table_map_perf(normal)  19,523,093,184  -1.2%
            parsing001(normal)     377,810,528  -1.1%
            pmcOrPats(normal)       60,075,264  -0.5%
  
                                   geo. mean    -0.4%
                                   minimum     -14.1%
                                   maximum      +5.3%
  
  Runtime changes
      haddock.Cabal(normal)   27,351,988,792  -0.7%
       haddock.base(normal)   26,997,212,560  -0.6%
   haddock.compiler(normal)  219,531,332,960  -1.0%
  
  Metric Decrease:
      LinkableUsage01
      ManyConstructors
      T17949
      T21839c
      T13035
      TcPlugin_RewritePerf
      hard_hole_fits
  
  Metric Increase:
      T3064
  

• 5cbc2c82
  by Matthew Pickering at 2026-04-03T19:57:02-04:00

  bytecode: Add magic header/version to bytecode files
  
  In order to avoid confusing errors when using stale interface files (ie
  from an older compiler version), we add a simple header/version check
  like the one for interface files.
  
  Fixes #27068
  

• d95a1936
  by fendor at 2026-04-03T19:57:02-04:00

  Add constants for bytecode in-memory buffer size
  
  Introduce a common constant for the default size of the .gbc and
  .bytecodelib binary buffer.
  
  The buffer is by default set to 1 MB.
  

• b822c30a
  by mangoiv at 2026-04-03T19:57:49-04:00

  testsuite: filter stderr for static001 on darwin
  
  This reactivates the test on x86_64 darwin as this should have been done
  long ago and ignores warnings emitted by ranlib on newer version of the
  darwin toolchain since they are benign. (no symbols for stub libraries)
  
  Fixes #27116
  

• 28ce1f8a
  by Andreas Klebinger at 2026-04-03T19:58:44-04:00

  Give the Data instance for ModuleName a non-bottom toConstr implementation.
  
  I've also taken the liberty to add Note [Data.Data instances for GHC AST Types]
  describing some of the uses of Data.Data I could find.
  
  Fixes #27129
  

• 8ca41ffe
  by mangoiv at 2026-04-03T19:59:30-04:00

  issue template: fix add bug label
  

• 3981db0c
  by Sylvain Henry at 2026-04-03T20:00:33-04:00

  Add more canned GC functions for common register patterns (#27142)
  
  Based on analysis of heap-check sites across the GHC compiler and Cabal,
  the following patterns were not covered by existing canned GC functions
  but occurred frequently enough to warrant specialisation:
  
    stg_gc_ppppp  -- 5 GC pointers
    stg_gc_ip     -- unboxed word + GC pointer
    stg_gc_pi     -- GC pointer + unboxed word
    stg_gc_ii     -- two unboxed words
    stg_gc_bpp    -- byte (I8) + two GC pointers
  
  Adding these reduces the fraction of heap-check sites falling back to
  the generic GC path from ~1.4% to ~0.4% when compiling GHC itself.
  
  Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
  

• d17d1435
  by Matthew Pickering at 2026-04-03T20:01:19-04:00

  Make home unit dependencies stored as sets
  
  Co-authored-by: Wolfgang Jeltsch <wolfgang@well-typed.com>
  

• 92a97015
  by Simon Peyton Jones at 2026-04-05T00:58:57+01:00

  Add Invariant (NoTypeShadowing) to Core
  
  This commit addresses #26868, by adding
  a new invariant (NoTypeShadowing) to Core.
  
  See Note [No type-shadowing in Core] in GHC.Core
  

• 8b5a5020
  by Simon Peyton Jones at 2026-04-05T00:58:57+01:00

  Major refactor of free-variable functions
  
  For some time we have had two free-variable mechanims for types:
  
  * The "FV" mechanism, embodied in GHC.Utils.FV, which worked OK, but
    was fragile where eta-expansion was concerned.
  
  * The TyCoFolder mechanism, using a one-shot EndoOS accumulator
  
  I finally got tired of this and refactored the whole thing, thereby
  addressing #27080.   Now we have
  
  * `GHC.Types.Var.FV`, which has a composable free-variable result type,
    very much in the spirit of the old `FV`, but much more robust.
    (It uses the "one shot trick".)
  
  * GHC.Core.TyCo.FVs now has just one technology for free variables.
  
  All this led to a lot of renaming.
  
  There are couple of error-message changes.  The change in T18451
  makes an already-poor error message even more mysterious.  But
  it really needs a separate look.
  
  We also now traverse the AST in a different order leading to a different
  but still deterministic order for FVs and test output has been adjusted
  accordingly.
  

• 4bf040c6
  by sheaf at 2026-04-05T14:56:29-04:00

  Add utility pprTrace_ function
  
  This function is useful for quick debugging, as it can be added to a
  where clause to pretty-print debugging information:
  
    fooBar x y
      | cond      = body1
      | otherwise = body2
      where
        !_ = pprTrace_ "fooBar" $
             vcat [ text "x:" <+> ppr x
                  , text "y:" <+> ppr y
                  , text "cond:" <+> ppr cond
                  ]
  

• 502e6ffe
  by Andrew Lelechenko at 2026-04-07T04:47:21-04:00

  base: improve error message for Data.Char.chr
  
  As per https://github.com/haskell/core-libraries-committee/issues/384
  

• b21bd52e
  by Simon Peyton Jones at 2026-04-07T04:48:07-04:00

  Refactor FunResCtxt a bit
  
  Fixes #27154
  

• 7fe84ea5
  by Zubin Duggal at 2026-04-07T19:11:52+05:30

  compiler: Warn when -finfo-table-map is used with -fllvm
  
  These are currently not supported together.
  
  Fixes #26435
  

• 4a45a7da
  by Matthew Pickering at 2026-04-08T04:37:29-04:00

  packaging: correctly propagate build/host/target to bindist configure script
  
  At the moment the host and target which we will produce a compiler for
  is fixed at the initial configure time. Therefore we need to persist
  the choice made at this time into the installation bindist as well so we
  look for the right tools, with the right prefixes at install time.
  
  In the future, we want to provide a bit more control about what kind of
  bindist we produce so the logic about what the host/target will have to
  be written by hadrian rather than persisted by the configure script. In
  particular with cross compilers we want to either build a normal stage 2
  cross bindist or a stage 3 bindist, which creates a bindist which has a
  native compiler for the target platform.
  
  Fixes #21970
  
  Co-authored-by: Sven Tennie <sven.tennie@gmail.com>
  

• b0950df6
  by Sven Tennie at 2026-04-08T04:37:29-04:00

  Cross --host and --target no longer required for cross (#21970)
  
  We set sane defaults in the configure script. Thus, these paramenters
  aren't required any longer.
  

• fef35216
  by Sven Tennie at 2026-04-08T04:37:30-04:00

  ci: Define USER_CONF_CC_OPTS_STAGE2 for aarch64/mingw
  
  ghc-toolchain doesn't see $CONF_CC_OPTS_STAGE2 when the bindist gets
  configured. So, the hack to override the compiler gets lost.
  

• 8dd6f453
  by Cheng Shao at 2026-04-08T04:38:11-04:00

  ghci: use ShortByteString for LookupSymbol/LookupSymbolInDLL/LookupClosure messages
  
  This patch refactors ghci to use `ShortByteString` for
  `LookupSymbol`/`LookupSymbolInDLL`/`LookupClosure` messages as the
  first part of #27147.
  
  Co-authored-by: Codex <codex@openai.com>
  

• 371ef200
  by Cheng Shao at 2026-04-08T04:38:11-04:00

  ghci: use ShortByteString for MkCostCentres message
  
  This patch refactors ghci to use `ShortByteString` for `MkCostCentres`
  messages as a first part of #27147. This also considerably lowers the
  memory overhead of breakpoints when cost center profiling is enabled.
  
  -------------------------
  Metric Decrease:
      interpreter_steplocal
  -------------------------
  
  Co-authored-by: Codex <codex@openai.com>
  

• 4a122bb6
  by Phil Hazelden at 2026-04-08T20:49:42-04:00

  Implement modifiers syntax.
  
  The `%m` syntax of linear types is now accepted in more places, to allow
  use by future extensions, though so far linear types is still the only
  consumer.
  
  This may break existing code where it
  
  * Uses -XLinearTypes.
  * Has code of the form `a %m -> b`, where `m` can't be inferred to be
    kind Multiplicity.
  
  The code can be fixed either by adding a kind annotation, or by setting
  `-XLinearTypes -XNoModifiers`.
  
  Proposal:
  https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0370-modifiers.rst
  

• 07267f79
  by Zubin Duggal at 2026-04-08T20:50:25-04:00

  hadrian: Don't include the package hash in the haddock directory
  
  Since GHC 9.8 and hash_unit_ids, haddock urls have looked like`ghc-9.10.3/doc/html/libraries/base-4.20.2.0-39f9/**/*.html`
  
  The inclusion of the hash makes it hard for downstream non-boot packages to properly link to these files, as the hash is not
  part of a standard cabal substitution.
  
  Since we only build one version of each package, we don't need the hash to disambiguate anything, we can just remove it.
  
  Fixes #26635
  

• 0a83b95b
  by ARATA Mizuki at 2026-04-08T20:51:18-04:00

  testsuite: Allow multiple ways to be run by setting multiple command-line options
  
  This patch allows multiple `--test-way`s to take effect, like:
  
  $ hadrian/build test --test-way=normal --test-way=llvm
  
  Previously, only one way was run if the test speed was 'normal' or 'fast'.
  
  Closes #26926
  
  Co-authored-by: sheaf <sam.derbyshire@gmail.com>
  

• e841931c
  by Teo Camarasu at 2026-04-08T20:52:00-04:00

  doc: improve eventlog-flush-interval flag documentation
  
  We mention the performance cost and how this flag can be turned off.
  
  Resolves #27056
  

• e332db25
  by Teo Camarasu at 2026-04-08T20:52:01-04:00

  docs/user_guide: fix typo
  

• 5b82080a
  by Simon Jakobi at 2026-04-08T20:52:44-04:00

  Fix -dsuppress-uniques for free variables in demand signatures
  
  Before:          Str=b{sXyZ->S}
  With this patch: Str=b{S}
  
  T13143.stderr is updated accordingly.
  
  Fixes #27106.
  

• b7a084cc
  by Simon Jakobi at 2026-04-08T20:53:27-04:00

  Documentation fixes for demand signature notation
  
  Fixes #27115.
  

• 59391132
  by Simon Jakobi at 2026-04-08T20:54:08-04:00

  Use upsert for non-deleting map updates
  
  Some compiler functions were using `alter`, despite never removing
  any entries: they only update an existing entry or insert a new one.
  
  These functions are converted to using `upsert`:
  
      alter  :: (Maybe a -> Maybe a) -> Key -> Map a -> Map a
      upsert :: (Maybe a ->       a) -> Key -> Map a -> Map a
  
  `upsert` variants are also added to APIs of the various Word64Map
  wrapper types.
  
  The precedent for this `upsert` operation is in the containers library:
  see https://github.com/haskell/containers/pull/1145
  
      Metrics: compile_time/bytes allocated
      -------------------------------------
  
          geo. mean:    -0.1%
          minimum:      -0.5%
          maximum:      +0.0%
  
  Resolves #27140.
  

• da7e82f4
  by Cheng Shao at 2026-04-08T20:54:49-04:00

  testsuite: fix testsuite run for +ipe again
  
  This patch makes the +ipe flavour transformer pass the entire
  testsuite again by dropping stdout/stderr checks of certain tests that
  are sensitive to stack layout changes with `+ipe`. Related: #26799.
  

• b135a87d
  by Zubin Duggal at 2026-04-09T19:36:50+05:30

  Bump directory submodule to 1.3.11.0 (unreleased)
  

• 3a291d07
  by Zubin Duggal at 2026-04-09T19:36:50+05:30

  Bump file-io submodule to 0.2.0
  

• e0ab606d
  by Zubin Duggal at 2026-04-10T18:40:20+05:30

  Release notes for GHC 10.0
  

• e08b9b34
  by Zubin Duggal at 2026-04-10T18:40:20+05:30

  Bump ghc-prim version to 0.14.0
  

• a92aac6e
  by Zubin Duggal at 2026-04-10T18:40:20+05:30

  Bump template-haskell to 2.25.0.0; update submodule exceptions for TH 2.25
  

• f254d9e8
  by Zubin Duggal at 2026-04-10T18:40:20+05:30

  Bump GHC version to 10.0
  

• 6ce0368a
  by Zubin Duggal at 2026-04-10T18:40:28+05:30

  Bump base to 4.23.0.0; update submodules for base 4.24 upper bound
  

• 702fb8a5
  by Zubin Duggal at 2026-04-10T18:40:28+05:30

  Bump GHC version to 10.1; update submodules template-haskell-lift and template-haskell-quasiquoter for ghc-internal 10.200
  

• 75df1ca4
  by Zubin Duggal at 2026-04-10T18:40:28+05:30

  Use changelog.d for release notes (#26002)
  
  GHC now uses a fragment-based changelog workflow using a custom script adapted from https://codeberg.org/fgaz/changelog-d.
  
  Contributors add a file in changelog.d/ for each user-facing change.
  At release time, these are assembled into release notes for sphinx (in RST) format, using
  the tool.
  
  New hadrian `changelog` target to generate changelogs
  
  CI job to validate changelog entries for MRs unless skipped with ~"no-changelog" label
  
  Teach sphinx about ghc-mr: extlink to link to MRs
  
  Remove `ghc-package-list` from sphinx, and implement it in changelog-d instead (Fixes #26476).
  
  (cherry picked from commit 989c07249978f418dfde1353abfad453f024d61a)
  

• 585d7450
  by Luite Stegeman at 2026-04-11T02:17:13-04:00

  tc: discard warnings in tcUserStmt Plan C
  
  We typecheck let_stmt twice, but we don't want the warnings twice!
  
  see #26233
  

• 2df604e9
  by Sylvain Henry at 2026-04-11T02:19:30-04:00

  Introduce TargetInt to represent target's Int (#15973)
  
  GHC was using host 'Int' in several places to represent values that
  live in the target machine's 'Int' type.  This is silently wrong when
  cross-compiling from a 32-bit host to a 64-bit target: the host Int
  is 32 bits while the target Int is 64 bits.
  
  See Note [TargetInt] in GHC.Platform.
  
  Also used the opportunity to make DynTag = Word8.
  
  Fixes #15973
  
  Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
  

• d419e972
  by Luite Stegeman at 2026-04-13T15:16:04-04:00

  Suppress desugaring warnings in the pattern match checker
  
  Avoid duplicating warnings from the actual desugaring pass.
  
  fixes #25996
  

• c5b80dd0
  by Phil de Joux at 2026-04-13T15:16:51-04:00

  Typo ~/ghc/arch-os-version/environments
  

• 71462fff
  by Luite Stegeman at 2026-04-13T15:17:38-04:00

  add changelog entry for #26233
  

• d1ddfd4b
  by Rodrigo Mesquita at 2026-04-14T18:41:12-04:00

  Add test for #25636
  
  The existing test behaviour of "T23146_liftedeq" changed because the
  simplifier now does a bit more inlining. We can restore the previous bad
  behavior by using an OPAQUE pragma.
  
  This test doubles as a test for #25636 when run in ghci, so we add it as
  such.
  

• b9df40ee
  by Rodrigo Mesquita at 2026-04-14T18:41:12-04:00

  refactor: protoBCOName is always a Name
  
  Simplifies the code by removing the unnecessary type argument to
  ProtoBCO which was always 'Name'
  

• 5c2a179e
  by Rodrigo Mesquita at 2026-04-14T18:41:12-04:00

  Allocate static constructors for bytecode
  
  This commit adds support for static constructors when compiling and
  linking ByteCode objects.
  
  Top-level StgRhsCon get lowered to ProtoStaticCons rather than to
  ProtoBCOs. A ProtoStaticCon gets allocated directly as a data con
  application on the heap (using the new primop newConApp#).
  
  Previously, we would allocate a ProtoBCO which, when evaluated, would
  PACK and return the constructor.
  A few more details are given in Note [Static constructors in Bytecode].
  
  Secondly, this commit also fixes issue #25636 which was caused by
  linking *unlifted* constructors in BCO instructions as
      - (1) a thunk indexing the array of BCOs in a module
      - (2) which evaluated to a BCO which still had to be evaluated to
        return the unlifted constructor proper.
  
  The (2) issue has been resolved by allocating the static constructors
  directly. The (1) issue can be resolved by ensuring that we allocate all
  unlifted top-level constructors eagerly, and leave the knot-tying for
  the lifted BCOs and top-level constructors only.
  
  The top-level unlifted constructors are never mutually recursive, so we
  can allocate them all in one go as long as we do it in topological
  order. Lifted fields of unlifted constructors can still be filled by the
  knot-tied lifted variables since in those fields it is fine to keep
  those thunks. See Note [Tying the knot in createBCOs] for more details.
  
  Fixes #25636
  
  -------------------------
  Metric Decrease:
      LinkableUsage01
  -------------------------
  

• cde47053
  by Rodrigo Mesquita at 2026-04-14T18:41:12-04:00

  Revert "StgToByteCode: Assert that PUSH_G'd values are lifted"
  
  This reverts commit ec26c54d818e0cd328276196930313f66b780905.
  
  Ever since f7a22c0f4e9ae0dc767115d4c53fddbd8372b777, we now do support
  and will link top-level unlifted constructors into evaluated and
  properly tagged values which we can reference with PUSH_G.
  
  This assertion is no longer true and triggered a failure in T25636
  

• c7a7e5b8
  by Rodrigo Mesquita at 2026-04-14T18:41:12-04:00

  refactor: Tag more remote Ptrs as RemotePtr
  
  Pure refactor which improves the API of
  
  - GHC.ByteCode.Linker
  - GHC.Runtime.Interpreter
  - GHC.Runtime.Interpreter.Types.SymbolCache
  
  by using `RemotePtr` for more functions which used to return `Ptr`s that
  could potentially be in a foreign process. E.g. `lookupIE`,
  `lookupStaticPtr`, etc...
  

• fc59494c
  by Rodrigo Mesquita at 2026-04-14T18:41:12-04:00

  Add float# and subword tests for #25636
  
  These tests cover that static constructors in bytecode work correctly
  for Float# and subword values (Word8#, Word16#)
  

• 477f521b
  by Rodrigo Mesquita at 2026-04-14T18:41:12-04:00

  test: Validate topoSort logic in createBCOs
  
  This test validates that the topological sorting and ordering of the
  unlifted constructors and lifted constructors in `createBCOs` is
  correct.
  
  See `Note [Tying the knot in createBCOs]` for why tying the knot for the
  created BCOs is slightly difficult and why the topological sorting is
  necessary.
  
  This test fails when `let topoSortedObjs = topSortObjs objs` is
  substituted by `let topoSortedObjs = zip [0..] objs`, thus witnessing
  the toposort logic is correct and necessary.
  
  The test calls the ghci `createBCOs` directly because it is currently
  impossible to construct in Source Haskell a situation where a top-level
  static unlifted constructor depends on another (we don't have top-level
  unlifted constructors except for nullary constructors like `Leaf ::
  (UTree :: UnliftedType)`).
  
  This is another test for fix for #25636
  

• 2d9c30be
  by Simon Jakobi at 2026-04-14T18:42:00-04:00

  Improve tests for `elem`
  
  ...in order to simplify the work on #27096.
  
  * Improve T17752 by including the Core output in golden files, checking
    both -O1 and -O2.
  * Add tests for fusion and no-fusion cases.
  
  Fixes #27101.
  

• 2dadf3b0
  by sheaf at 2026-04-16T13:28:39-04:00

  Simplify mkTick
  
  This commit simplifies 'GHC.Core.Utils.mkTick', removing the
  accumulating parameter 'rest' which was suspiciously treating a bunch of
  different ticks as a group, and moving the group as a whole around the
  AST, ignoring that the ticks in the group might have different placement
  properties.
  
  The most important change is that we revert the logic (added in 85b0aae2)
  that allowed ticks to be placed around coercions, which caused serious
  issues (e.g. #27121). It was just a mistake, as it doesn't make sense
  to put a tick around a coercion.
  
  Also adds Note [Pushing SCCs inwards] which clarifies the logic for
  pushing SCCs into lambdas, constructor applications, and dropping SCCs
  around non-function variables (in particular the treatment of splittable
  ticks).
  
  A few other changes are also implemented:
  
    - simplify 'can_split' predicate (no functional change)
    - combine profiling ticks into one when possible
  
  Fixes #26878, #26941 and #27121
  
  Co-authored-by: simonpj <simon.peytonjones@gmail.com>
  

• a0d6f1f4
  by Simon Jakobi at 2026-04-16T13:29:28-04:00

  Add regression test for #9074
  
  Closes #9074.
  

• d178ee89
  by Sylvain Henry at 2026-04-16T13:30:25-04:00

  Add changelog for #15973
  

• e8a196c6
  by sheaf at 2026-04-16T13:31:19-04:00

  Deal with 'noSpec' in 'coreExprToPmLit'
  
  This commit makes two separate changes relating to
  'GHC.HsToCore.Pmc.Solver.Types.coreExprAsPmLit':
  
    1. Commit 7124e4ad mistakenly marked deferred errors as non-canonical,
       which led to the introduction of 'nospec' wrappers in the
       generated Core. This reverts that accident by declaring deferred
       errors as being canonical, avoiding spurious 'nospec' wrapping.
    2. Look through magic identity-like Ids such as 'nospec', 'inline' and
       'lazy' in 'coreExprAsPmLit', just like Core Prep does.
       There might genuinely be incoherent evidence, but that shouldn't
       obstruct the pattern match checker. See test T27124a.
  
  Fixes #25926 #27124
  
  -------------------------
  Metric Decrease:
      T3294
  -------------------------
  

• 8cb99552
  by Sylvain Henry at 2026-04-16T19:22:43-04:00

  hadrian: warn when package index is missing (#16484)
  
  Since cabal-install 3.0 we can query the path of remote-repo-cache and
  check if hackage package index is present.
  
  Fixes #16484
  

• d6ce7477
  by Richard Eisenberg at 2026-04-16T19:23:25-04:00

  Teach hadrian to --skip-test.
  
  Fixes #27188.
  
  This adds the --skip-test flag to `hadrian build`, as documented in the
  patch.
  

• 7666f4a9
  by Fendor at 2026-04-17T22:29:51-04:00

  Migrate `ghc-pkg` to use `OsPath` and `file-io`
  
  `ghc-pkg` should use UNC paths as much as possible to avoid MAX_PATH
  issues on windows.
  
  `file-io` uses UNC Paths by default on windows, ensuring we use the
  correct APIs and that we finally are no longer plagued by MAX_PATH
  issues in CI and private machines.
  
  On top of it, the higher correctness of `OsPath` is appreciated in this
  small codebase. Also, we improve memory usage very slightly, due to the
  more efficient memory representation of `OsPath` over `FilePath`
  
  Adds `ghc-pkg` regression test for MAX_PATH on windows
  
  Make sure `ghc-pkg` behaves as expected when long paths (> 255) are
  involved on windows.
  
  Let's generate a testcase where we can actually observe that `ghc-pkg`
  behaves as epxected.
  
  See the documentation for windows on Maximum Path Length Limitation:
  
  * `https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation`
  
  Adds changelog entry for long path support in ghc-pkg.
  

• 78434e8c
  by Simon Peyton Jones at 2026-04-17T22:30:38-04:00

  Kill off the substitution in Lint
  
  Now that we have invariant (NoTypeShadowing) we no longer
  need Lint to carry an ambient substitution.  This makes it
  simpler and faster.  A really worthwhile refactor.
  
  There are some knock-on effects
  
  * Linting join points after worker/wrapper.  See
    Note [Join points and beta redexes]
  
  * Running a type substitution after the desugarer.
    See Note [Substituting type-lets] in
    the new module GHC.Core.SubstTypeLets
  
  Implements #27078
  
  Most perf tests don't use Lint so we won't see a perf incresae.
  But T1969, which uses -O0 and Lint, gets 1.3% worse because it has
  to run the SubstTypeLets pass which is a somewhat expensive no-op
  
  Overall though compile-time allocations are down 0.1%.
  
  Metric Increase:
      T1969
  

• 86ca6c2c
  by mangoiv at 2026-04-17T22:31:22-04:00

  testsuite: inline elemCoreTest
  
  Some weird (probably python scoping) rule caused elemCoreTest, a regex
  being out of scope on ubuntu, presumably because of a newer python version.
  This patch just inlines the regex, which fixes the issue.
  
  Fixes #27193
  

• 72d6dc74
  by aparker at 2026-04-20T20:15:44-04:00

  NCG: Implement constant folding for vector simd ops (Issue #25030)
  

• b9cab907
  by sheaf at 2026-04-20T20:15:44-04:00

  Mark some SIMD tests as broken on i386 optllvm
  
  As seen in #25498, several SIMD tests are broken on i386 in the optllvm
  way. This commit marks them as "expect_broken".
  

• 76528cc3
  by Wolfgang Jeltsch at 2026-04-20T20:16:25-04:00

  Move most of the `System.IO` implementation into `base`
  
  This involves a rewrite of the `combine` helper function to avoid the
  use of `last`, which would now be flagged as an error.
  
  Metric Decrease:
      LinkableUsage01
      T3294
  Metric Increase:
      T12227
      T12707
      T5642
  

• 04d143c0
  by Luite Stegeman at 2026-04-21T14:05:33-04:00

  rts: add a few missing i386 relocations in the rts linker
  

• 014087e7
  by Luite Stegeman at 2026-04-21T14:05:34-04:00

  CodeOutput: Fix finalizers on multiple platforms
  
   - ELF platforms: emit .fini_array section
   - wasm32/Darwin: emit initializer with __cxa_atexit call
   - Windows: use -Wl,--whole-archive to prevent dropping finalizer symbols
   - rts linker: fix crash/assertion failure unloading objects with finalizers
  
  fixes #27072
  

• 915bba6f
  by Simon Jakobi at 2026-04-21T14:06:16-04:00

  Add regression test for #10531
  
  Closes #10531.
  

• 86a646a6
  by Andreas Klebinger at 2026-04-22T13:00:05-04:00

  Revert use of generic instances for compiler time perf reasons.
  
  Revert "Derive Semigroup/Monoid for instances believed could be derived in #25871"
  
  This reverts commit 11a04cbb221cc404fe00d65d7c951558ede4caa9.
  
  Revert "add Ghc.Data.Pair deriving"
  
  This reverts commit 15d9ce449e1be8c01b89fd39bdf1e700ea7d1dce.
  

• bc9ee1cf
  by Wen Kokke at 2026-04-22T13:00:51-04:00

  hadrian: Fix docs to remove static flavour
  
  In 638f6548, the static flavour was turned into into the fully_static
  flavour transformer. However, this commit did not update flavours.md.
  

• cc9cc6d5
  by Cheng Shao at 2026-04-23T09:40:46+00:00

  configure: bump LlvmMaxVersion to 23
  
  This patch bumps `LlvmMaxVersion` to 23 to support LLVM 22.x releases.
  

• 2ea7ef8e
  by Cheng Shao at 2026-04-23T09:46:26+00:00

  changelog: add llvm 22.x support
  

• 5574ee10
  by Cheng Shao at 2026-04-24T08:24:30-04:00

  compiler: avoid unused temporary `appendFS` operands
  
  This patch fixes unused temporary `appendFS` operands in the codebase
  that are retained in the `FastString` table after concatenation.
  Rewrite rules are added so that if an operand is
  `fsLit`/`mkFastString`, the `appendFS` application is rewritten to
  append the `ShortByteString` operands first. The patch also fixes
  `sconcat` behavior to align with `mconcat` for the same reason. Fixes #27205.
  

• 4ed78760
  by mangoiv at 2026-04-24T08:25:13-04:00

  contributing: adjust MR template to be less verbose
  
  - MR template only shows text that is relevant for submissiong
  - MR template was rewritten so it's readable from a user's and reviewer's
    perspective
  
  Resolves #27165
  
  Co-Authored-By: @sheaf
  

• 87db83e2
  by Cheng Shao at 2026-04-24T14:37:21-04:00

  ci: bump freebsd boot ghc to 9.10.3
  
  This commit bumps freebsd boot ghc to 9.10.3 to align with other
  platforms and prevent outdated boot libs in boot ghc to block the
  freebsd job.
  

• 17e3a0b7
  by Cheng Shao at 2026-04-24T14:37:21-04:00

  compiler: improve Binary instance of Array
  
  This patch improves the `Binary` instance of `Array`:
  
  - We no longer allocate intermediate lists. When serializing an
    `Array`, we iterate over the elements directly; when deserializing
    it, we allocate the result `Array` and fill it in a loop.
  - Now we only serialize the array bounds tuple; the length field is
    not needed.
  
  Closes #27109.
  

• 2d30f7d3
  by sheaf at 2026-04-24T14:38:23-04:00

  Vendor mini-QuickCheck for testsuite
  
  This commit extracts the vendored QuickCheck implementation from the
  foundation testsuite to make it more broadly available in the GHC
  testsuite, and makes use of it in the simd006 test (which also used
  a vendored QuickCheck implementation).
  
  On the way, we update the linear congruential generator to avoid the
  shortcoming of only generating 31 bit large numbers.
  
  Fixes #25990 and #25969.
  

• 1350271b
  by sheaf at 2026-04-27T09:32:53-04:00

  Ensure TcM plugins are only initialised once
  
  This commit ensures we keep TcM plugins (typechecker plugins,
  defaulting plugins and hole fit plugins) running all the way through
  desugaring, instead of stopping them at the end of typechecking.
  
  To do this, the "stop" actions of TcPlugin and DefaultingPlugin are
  split into two: one for the "post-typecheck" action, and one for the
  final shutdown action (after desugaring).
  
  This allows the plugins to be invoked by the pattern match checker
  (during desugaring) without having to be repeatedly re-initialised and
  stopped, fixing #26839.
  
  In the process, this commit modifies 'initTc' and 'initTcInteractive',
  adding an extra argument that describes whether to start/stop the 'TcM'
  plugins.
  
  See Note [Stop TcM plugins after desugaring] for an overview.
  

• 42549222
  by sheaf at 2026-04-27T09:33:50-04:00

  Hadrian: add --keep-response-files
  
  This commit adds a Hadrian flag that allows response files to be
  retained. This is useful for debugging a failing Hadrian command line.
  

• 40564e8d
  by sheaf at 2026-04-27T09:34:46-04:00

  hadrian/build-cabal.bat: fix build on Windows
  
  Commit 8cb99552f6 introduced a warning for a missing package index.
  However, the logic was faulty on Windows: the piping was broken, and
  "remote-repo-cache:" was being interpreted as a (malformed) drive letter,
  leading to the error:
  
    The filename, directory name, or volume label syntax is incorrect.
  
  This commit fixes that by using a temporary file instead of piping.
  

• 14bc71e4
  by Sven Tennie at 2026-04-28T13:22:47-04:00

  ghc: Distinguish between having an interpreter and having an internal one
  
  Actually, these are related but different things:
  
  - ghc can run an interpreter (either internal or external)
  - ghc is compiled with an internal interpreter
  
  Splitting the logic solves compiler warnings and expresses the intent
  better.
  

• df691563
  by Vladislav Zavialov at 2026-04-28T13:23:29-04:00

  Refactor HsWildCardTy to use HoleKind (#27111)
  
  The payload of this patch is that the extension fields of HsWildCardTy
  and HsHole now match:
  
  	type instance XWildCardTy Ghc{Ps,Rn} = HoleKind
  	type instance XHole       Ghc{Ps,Rn} = HoleKind
  
  This is progress towards unification of HsExpr and HsType.
  Test case: T25121_status
  
  In addition to that, exact-printing of infix holes is fixed.
  Test case: PprInfixHole
  

• f3485446
  by fendor at 2026-04-28T13:24:12-04:00

  Expose startupHpc as an rts symbol
  

• 28f07d70
  by fendor at 2026-04-28T13:24:12-04:00

  Make HPC work with bytecode interpreter
  
  Add support to generate .tix files from bytecode objects and the
  bytecode interpreter.
  
  Conceptually, we insert HPC ticks into the bytecode similar to how we insert
  breakpoints.
  HPC and breakpoints do not share the same tick array but we use a separate
  tick-array for hpc/breakpoint ticks during bytecode generation.
  
  We teach the bytecode interpreter to handle hpc ticks.
  The implementation is quite trivial, simply increment the counter in the
  global hpc_ticks array for the respective module.
  
  This hpc_ticks array is generated as part of the `CStub`, so we can rely
  on it existing.
  
  A tricky bit is "registering" a bytecode object for HPC instrumentation.
  In the compiled case, this is achieved via CStub and initializer/finalizers
  `.init` sections which are called when the executable is run.
  After the initializers have been invoked, which is before `hs_init_ghc`,
  we then call `startup_hpc` in `hs_init_ghc` iff any modules were "registered"
  for hpc instrumentation via `hs_hpc_module`.
  
  Since bytecode objects are loaded after starting up GHCi, this workflow
  doesn't work for supporting `hpc` and the `hpc` run-time is never
  started, even if a module is added for instrumentation.
  
  We fix this issue by employing the same technique as is for `SptEntry`s:
  
  * We introduce a new field to `CompiledByteCode`, called `ByteCodeHpcInfo`
    which contains enough information to call `hs_hpc_module`, allowing us to
    register the module for `hpc` instrumentation`.
  * After registering the module, we unconditionally call `startupHpc`, to make
    sure the .tix file is written.
  
  Calling `startupHpc` multiple times is safe.
  Calling `hs_hpc_module` multiple times for the same module is also safe.
  
  If we didn't register the hpc module in this way, evaluating a bytecode object
  instrumented with `-fhpc` without registering it in the `hpc` run-time will
  simply not generate any `.tix` files for this bytecode object.
  
  However, this shouldn't happen if everything is set up correctly.
  
  Closes #27036
  

• 950879f0
  by Vladislav Zavialov at 2026-04-28T13:24:55-04:00

  Move NamespaceSpecifier from x-fields into the AST proper (#26678)
  
  This refactoring moves NamespaceSpecifier out of extension fields and into the
  AST proper, as it is part of the user-written source, and is not pass-specific.
  
  Summary of changes:
  
  * Move NamespaceSpecifier from GHC/Hs/Basic.hs to Language/Haskell/Syntax/ImpExp.hs
    and parameterise it by the compiler pass, creating the necessary extension points
  * Move NamespaceSpecifier out of XFixitySig into FixitySig
  * Move NamespaceSpecifier out of XIEThingAll (IEThingAllExt) into IEThingAll
  * Move NamespaceSpecifier out of XIEWholeNamespace (IEWholeNamespaceExt) into IEWholeNamespace
  
  This is a pure refactoring with no change in behaviour.
  

• 9797052b
  by Simon Peyton Jones at 2026-04-28T13:25:37-04:00

  Fix assertion check in checkResultTy
  
  As #27210 shows, the assertion was a little bit too eager.
  
  I refactored a bit by moving some code from GHC.Tc.Gen.App
  to GHC.Tc.Utils.Unify; see the new function tcSubTypeApp,
  which replaces tcSubTypeDS
  

• 9f85f034
  by Duncan Coutts at 2026-04-30T04:52:42-04:00

  Make cmm 'import "package" name;' syntax use consistent label types
  
  There is a little-used syntactic form in cmm imports:
  
  import "package" foo;
  
  Which means to import foo from the given package (unit id, specified as
  a string). This syntax is somewhat reminiscent of GHC's package import
  extension.
  
  This syntax form is not used in the rts cmm code, nor any of the boot
  libraries. It may not be used at all. Unclear.
  
  Change the kind of CLabel this syntax generates to be consistent with
  the others. The other cmm imports use ForeignLabel with
  ForeignLabelInExternalPackage. For some reason this form was using
  CmmLabel. Change that to also be ForeignLabel but with
  ForeignLabelInPackage. This specifies a specific package, rather
  than an unnamed external package.
  

• a811f68f
  by Duncan Coutts at 2026-04-30T04:52:42-04:00

  Change default cmm import statements to be internal
  
  Previously a cmm statement like:
  
  import foo;
  
  meant to expect the symbol from a different shared library than the
  current one.
  
  Now it means to expect the symbol from the same shared library as the
  current one. We'll add explicit syntax to indicate that it's a foreign
  import. Most existing uses are in fact intenal (rts to rts), so few
  imports will need to be annotated foreign. Examples would include cmm
  code in libraries (other than the rts) that need to access RTS APIs.
  
  In practice, this makes no difference whatsoever at the moment on any
  platform other than windows (where building Haskell libs as shared libs
  does not fully work yet), since the 'labelDynamic' treats all such
  labels as foreign, irrespective of the foreign label source.
  

• 17fe5d1d
  by Duncan Coutts at 2026-04-30T04:52:42-04:00

  Add cmm import syntax 'import DATA foo;' as better name for CLOSURE
  
  The existing syntax is:
  
  import CLOSURE foo;
  
  The new syntax is
  
  import DATA foo;
  
  This means to interpret the symbol foo as refering to data (i.e. a
  global constant or variable) rather than to code (a function). The
  historical syntax for this uses CLOSURE, which is rather misleading.
  Presumably this was done to avoid introducing new reserved words.
  
  Be less squemish about new reserved words and add DATA and use that.
  Keep the existing CLOSURE syntax as an alias for compatibility.
  

• 3a530d68
  by Duncan Coutts at 2026-04-30T04:52:42-04:00

  Add cmm 'import extern name;' syntax
  
  Since the default for cmm imports is now for symbols within the same
  shared object, we need a way to indicate we want a symbol from an
  external shared object:
  
  import extern foo;      -- for a function
  import extern DATA foo; -- for data
  
  This adds a new reserved word 'extern'.
  
  We don't expect to have to use this much. Most cmm imports are
  intra-DSO.
  
  This makes no difference currently on ELF and MachO platforms, but does
  make a difference to the linking conventions on PE (Windows).
  
  In future it's plausible we could take make distinctions on ELF or
  MachO, so it's worth trying to get it right. Windows can be the guinea
  pig.
  

• 2b8e44c7
  by Duncan Coutts at 2026-04-30T04:52:42-04:00

  Add cmm syntax 'import "package" DATA foo;' for completeness
  
  We already have:
  
  import DATA foo;      -- for data imports
  import "package" foo; -- for imports from a given unitid
  
  There's no reason not to have both at once:
  
  import "package" DATA foo;
  
  So add that.
  

• ee05e5cc
  by Duncan Coutts at 2026-04-30T04:52:42-04:00

  Improve the commentary for the cmm import grammar.
  
  AFAIK, this is the only place where GHC-style Cmm syntax is documented.
  

• b35946ad
  by Duncan Coutts at 2026-04-30T04:52:42-04:00

  Add a changelog.d entry for the .cmm import syntax changes
  

• d59b7c71
  by Wolfgang Jeltsch at 2026-04-30T04:53:25-04:00

  Move code that uses `GHC.Internal.Text.Read` into `base`
  
  This contribution serves to remove all dependencies on
  `GHC.Internal.Text.Read` from within `ghc-internal`, so that the
  implementation of `Text.Read` and ultimately more reading-related code
  can be moved to `base` as well.
  
  The following things are moved from `ghc-internal` to `base`:
  
    * I/O-related `Read` instances
    * Most of the `Numeric` implementation
    * The instance `Read ByteOrder`
    * The `parseVersion` operation
    * The `readConstr` operation
  
  Metric Increase:
      LinkableUsage01
      T9198
      T12425
      T13035
      T13820
      T18140
  

• 5bd6a964
  by Rodrigo Mesquita at 2026-04-30T04:54:08-04:00

  New rts Message to {set,unset} TSO flags
  
  This commit introduces stg_MSG_SET_TSO_FLAG_info and
  stg_MSG_UNSET_TSO_FLAG_info, which allows setting flags of a TSO other
  than yourself.
  
  This is especially useful/necessary to set breakpoints and toggle
  breakpoints of different threads, which is needed to safely implement
  features like pausing, toggling step-out, toggling step-in per thread,
  etc.
  
  Fixes #27131
  
  -------------------------
  Metric Decrease:
      T3294
  -------------------------
  

• ce97fd3e
  by Rodrigo Mesquita at 2026-04-30T04:54:08-04:00

  test: Add test setting another TSO's flags
  
  Introduces a test that runs on two capabilities. The main thread running
  on Capability 0 sets the flags on a TSO running on Capability 1.
  The TSO from Capability 1 itself checks whether its flags were set and
  reports that back.
  
  This validates that the RTS messages for setting TSO flags work, even if
  it doesn't test a harsher scenario with race conditions to exercise why
  the message passing is necessary for safely setting another TSO's flags.
  
  Part of #27131
  

• a4ff6315
  by David Eichmann at 2026-04-30T04:54:51-04:00

  Hadrian: withResponseFile outputs response file when verbodity is Verbose
  
  At the Verbose verbosity, shake will display full commandlines. With the
  use of response files, the full command is hidden. That makes it hard to run
  the command manually. This commit outputs the contents of the response
  file so that that full command can be recreated and also hints at the
  use of the --keep-response-files hadrian flag.
  

• cd732ee3
  by Duncan Coutts at 2026-04-30T04:54:51-04:00

  Use response files for hadrian linking with ghc (support long command lines)
  
  In future support for windows dynamic linking, we expect long command
  lines for linking dll files with ghc. Experiments with dynamic linking the
  ghc-internal library yielded a link command well over 32kb. We did not
  encounter this before for static libs, since we already use ar's @file
  feature (if available, which it is for the llvm toolchain).
  
  Co-authored-by: David Eichmann <davide@well-typed.com>
  

• 3d41368f
  by Andreas Klebinger at 2026-04-30T04:55:32-04:00

  Split GHC.Driver.Main.hs up into multiple components.
  
  This commit splits GHC.Driver.Main into four components:
  
  * GHC.Driver.Main.Compile
  * GHC.Driver.Main.Hsc
  * GHC.Driver.Main.Interactive
  * GHC.Driver.Main.Passes
  
  We might improve that separation further in the future but this should
  hopefully make it easier to reason about and work with this part of the
  code.
  

• 2128ba85
  by Cheng Shao at 2026-04-30T04:56:14-04:00

  compiler: avoid unique OccNames for internal Names in bytecode objects
  
  This patch improves bytecode object serialization logic by avoiding
  the construction of unique `OccName`s when serializing/deserializing
  internal `Name`s. Closes #27213.
  
  -------------------------
  Metric Decrease:
      LinkableUsage01
  -------------------------
  

• e16854c3
  by Vladislav Zavialov at 2026-04-30T04:56:57-04:00

  Replace GHC 9.16 references with GHC 10.0
  

• 39141343
  by Alice Rixte at 2026-05-01T14:09:32+02:00

  Add Bounded instances for Double, Float, CDouble and CFloat
  

• 5c4c3bf4
  by Sylvain Henry at 2026-05-02T03:39:28-04:00

  testsuite: fix flaky foundation Divisible / mulIntMayOflo# tests (#27222)
  
  Since the LCG was widened to 64 bits and the seed randomised per CI run
  (commit 2d30f7d3400 "Vendor mini-QuickCheck for testsuite"), two latent
  bugs in the foundation test surface stochastically:
  
  * The Divisible property `(x `div` y) * y + (x `mod` y) == x` raises
    ArithException(Overflow) when (a, b) = (minBound, -1) for fixed-width
    signed Integral types. Split testNumber/testDivisible into Bounded and
    unbounded variants and skip just that one pair, gated by
    `(minBound :: a) < 0` so unsigned types lose no coverage.
  
  * The `mulIntMayOflo#` test compared raw Int# bit-for-bit, but the primop
    is only specified to return 0/non-zero -- the exact non-zero indicator
    legitimately differs between backends and inlining choices. Add a
    dedicated `testPrimopMayOflo` helper that only compares zero / non-zero.
  
  Also fix the long-standing typo "Dividible" -> "Divisible" in identifiers.
  
  Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
  

• e242ce4f
  by Sylvain Henry at 2026-05-02T03:39:28-04:00

  testsuite: catch and display exceptions in MiniQuickCheck
  
  Exceptions raised while evaluating a property are now caught and reported
  as a normal failure (with arguments and seed), instead of aborting the
  test.
  
  Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
  

• 3b75cccd
  by fendor at 2026-05-02T03:40:14-04:00

  Fix name of Note [Structure of dep_boot_mods]
  

• 9a9ae4df
  by Duncan Coutts at 2026-05-05T14:44:37-04:00

  Use __attribute__((dllimport)) for external RTS symbol declarations
  
  This is needed to be hygenic about DLL symbol imports and exports.
  The attribute is ignored on platforms other than Windows.
  
  Use of the attribute however means that external data symbols do not
  have a compile-time constant address (they are loaded using an
  indirection). This means we have to adjust the rtsSyms initial linker
  table so that it is a local constant in a function, rather than a global
  constant. We now define it within a function that pre-populates the
  symbol table with the RTS symbols.
  

• 2ad3e01e
  by Duncan Coutts at 2026-05-05T14:44:37-04:00

  Fix the rts linker declarations for a few data symbols
  
  and ensure that the (windows only) rts_IOManagerIsWin32Native data
  symbol is marked as externally visible.
  

• 8ff4fdb5
  by David Eichmann at 2026-05-05T14:44:37-04:00

  Hadrian: Disable runtime pseudo relocations for RTS on windows hosts
  

• 96974723
  by Teo Camarasu at 2026-05-05T14:45:20-04:00

  ghci/TH: refactor to use IORef QState
  
  This is a pure refactor and shouldn't modify semantics at all
  

• eff6bfaf
  by Teo Camarasu at 2026-05-05T14:45:20-04:00

  iserv: recover/getQ/putQ should behave same as internal interpreter
  
  The internal and external interpreter should behave the same when
  handling `recover`, the exeception recovery method of Q.
  In practice, they diverge. In case of failure, the internal interpreter
  only restores error message state to before the computation, wheras the
  external interperter restores error message state *and* the state of putQ/getQ.
  
  As far as I can tell this is a simple mistake in the implementation.
  Note [TH recover with -fexternal-interpreter] describes the correct
  behaviour but the implementation doesn't mirror this.
  
  This change restores the correct behaviour by keeping the effects of
  putQ in the erroring computation.
  
  This is a breaking change since it modifies the behaviour of programs
  that rely on recover ignoring putQ from failling computations when used
  with the external interpreter. Although I highly doubt anyone relies on
  this behaviour.
  
  This divergence was first introduced in d00c308633fe7d216d31a1087e00e63532d87d6d.
  As far as I can tell this was unintentional and tha commit was trying to solve a different bug.
  
  Resolves #27022
  

• 1cb1d672
  by Wen Kokke at 2026-05-06T09:53:40-04:00

  rts: Add dynamic trace flags API
  
  This commit adds an API to the RTS (exposed via Rts.h) that allows users to dynamically change the trace flags.
  Prior to this commit, users were able to stop and start the profiling and heap profiling timers (via startProfTimer/stopProfTimer and startHeapProfTimer/stopHeapProfTimer).
  This extends that functionality to also cover the core event types.
  
  The getTraceFlag/setTraceFlag functions read and write the values of the trace flag cache, which is allocated by Trace.c, rather than modifying the members of RtsFlags.TraceFlags.
  This is done under the assumption that the members of RtsFlags should not be modified after RTS initialisation.
  Consequently, if the user modifies the trace flags using setTraceFlag, the object returned by getTraceFlags (from base) will not reflect these changes.
  
  The trace flags are not protected by locks of any sort.
  Hence, these functions are not thread-safe.
  However, the trace flags are not modified by the RTS after initialisation, only read, so the race conditions introduced by one user modifying them are most likely benign.
  
  This PR also puts the trace flag cache in a single global struct, as opposed to a collection of global variables, and changes the types of the individual flags from uint8_t to bool, as these have the same size on both Clang and GCC and are a better semantic match.
  Prior to the change to uint8_t, they had type int, see 42c47cd6.
  Even with its deprecation in C23, I don't think there should be any issue depending on stdbool.h.
  The TRACE_X macros are redefined to access the global struct, with values cast to const bool to ensure they are read-only.
  

• 9d54dc94
  by Wen Kokke at 2026-05-06T09:53:40-04:00

  rts: Ensure TRACE_X values are used in place of RtsFlags.TraceFlags.X
  

• 418d737b
  by Wen Kokke at 2026-05-06T09:53:40-04:00

  rts: Fix nonmoving-GC tracing
  
  The current nonmoving-GC tracing functions were written in a different
  style from the other tracing functions. They were directly implemented
  as, e.g., a traceConcMarkEnd function that called postConcMarkEnd.
  The other tracing functions are implemented as, e.g., traceThreadLabel_,
  a function that posts the thread label event, and traceThreadLabel, a
  macro that checks whether TRACE_scheduler is set. This commit fixes that
  implementation, and ensures that the nonmoving-GC tracing functions only
  emit events if nonmoving-GC tracing is enabled.
  

• 99f4afa4
  by Wen Kokke at 2026-05-06T09:53:40-04:00

  rts: Add SymI_HasProto for get/setTraceFlag
  

• 7e9eb8b9
  by Wen Kokke at 2026-05-06T09:53:40-04:00

  rts: Add SymI_HasProto for start/endEventLogging
  

• 3a3045fb
  by Wen Kokke at 2026-05-06T09:53:41-04:00

  rts: Add changelog entry
  

• a3b339a4
  by Teo Camarasu at 2026-05-06T09:54:25-04:00

  interface-stability/base: don't distinguish ws-32
  
  The interface of base is identical when the Word size is 32bits.
  Therefore, there is no need to have another file for this case.
  So, we delete it.
  
  Step towards: #26752
  

• eb922183
  by Duncan Coutts at 2026-05-07T14:28:50+01:00

  Add a rts posix FdWakup utility module
  
  This will be used to implement wakeupIOManager for in-RTS I/O managers.
  
  It provides a notification/wakeup mechanism using FDs, suitable for
  situations when a thread is blocked on a set of fds anyway. It uses the
  classic self-pipe trick, or equivalently eventfd on supported platforms.
  
  This will initially be used to implement prompt interrupt or shutdown of
  the posix ticker thread.
  

• 01b0e233
  by Duncan Coutts at 2026-05-07T14:28:50+01:00

  Add prompt shutdown to the pthread ticker implementation.
  
  The Linux timerfd ticker monitors a pipe which is used by exitTicker to
  ensure a prompt wakeup and shutdown. The pthread ticker lacked this and
  so would only exit at the next ticker wakeup (10ms by default).
  
  This patch adds the same mechanism to the pthread ticker.
  
  This changes the pthread ticker from waiting by using nanosleep() to
  waiting using either ppoll() or select(), so that it can wait on both
  a time and a file descriptor. On Linux at least, a test program to
  compare the timing jitter of these APIs shows that using nanpsleep,
  ppoll or select makes no statistical difference to the maximum or
  average jitter.
  
  This is a step towards unifying the posix ticker implementations, so
  that we can have just one portable one (albeit with some limited cpp).
  It is also a step towards using the ticker as part of a more general
  implementation of wakeUpRts, since this will require a method to wake
  the rts from a signal handler context (ctl-c handler).
  

• bc41d646
  by Duncan Coutts at 2026-05-07T14:28:50+01:00

  Update ticker header commentary
  
  It was antique and didn't apply even to the previous implementation, and
  certainly not to the updated one.
  

• 4ed9a386
  by Duncan Coutts at 2026-05-07T14:28:50+01:00

  Remove the timerfd-based ticker implementation
  
  There does not appear to be any remaining advantage on Linux to using
  the timerfd ticker implementation over the portable one (using ppoll on
  Linux for precise timing).
  
  The eventfd implementation was originally added at a time when Linux was
  still using a signal based implementation. So it made sense at the time.
  See (closed) issue #10840.
  

• 97504fa6
  by Duncan Coutts at 2026-05-07T14:28:50+01:00

  Consolidate to a single posix ticker implementation
  
  Previously we had four implementations, two using signals and two using
  threads. Having just one should make behaviour more consistent between
  platforms, and should make maintenance easier.
  

• 1e60023b
  by Facundo Domínguez at 2026-05-07T18:01:16-04:00

  Generalize so_inline to specify which bindings should be preserved
  
  This commit generalizes the so_inline option of the simple optimizer
  so we can indicate with a predicate the specific bindings that should
  be kept.
  
  This feature is important for the LiquidHaskell plugin, which relies on the
  simple optimizer to make core programs easier to read, but needs to preserve
  bindings that are relevant for verification.
  
  See https://gitlab.haskell.org/ghc/ghc/-/issues/24386 for the full discussion.
  

• 44cf9cd7
  by Wolfgang Jeltsch at 2026-05-12T09:48:18-04:00

  Move the `Text.Read` implementation into `base`
  

• 4ac3f7d6
  by Vladislav Zavialov at 2026-05-12T09:49:03-04:00

  EPA: Use AnnParen for tuples and sums
  
  Summary of changes
  
  * Do not use AnnParen in XListTy, replace it with EpToken "[" and "]"
  * Specialise AnnParen to tuple/sums by dropping the AnnParensSquare
    and keeping only AnnParens and AnnParensHash
  * Use AnnParen in XExplicitTuple
  * Use AnnParen in XExplicitTupleTy
  * Use AnnParen in XTuplePat
  * Use AnnParen in XExplicitSum (via AnnExplicitSum)
  * Use AnnParen in XSumPat (via EpAnnSumPat)
  
  This is a refactoring with no user-facing changes.
  

• 1bdcddec
  by Duncan Coutts at 2026-05-12T09:49:48-04:00

  Add minimal dlltool support to ghc-toolchain
  
  The dlltool is a tool that can create dll import libraries from .def
  files. These .def files list the exported symbols of dlls. Its somewhat
  like gnu linker scripts, but more limited.
  
  We will need dlltool to build the rts and ghc-internal libraries as DLLs
  on Windows. The rts and ghc-internal libraries have a recursive
  dependency on each other. Import libraries can be used to resolve
  recursive dependencies between dlls. We will use an import library for
  the rts when linking the ghc-internal library.
  

• f7fc3770
  by Duncan Coutts at 2026-05-12T09:49:48-04:00

  Add minimal dlltool support into ./configure
  
  Find dlltool, and hopefully support finding it within the bundled llvm
  toolchain on windows.
  

• e4e22bfb
  by Duncan Coutts at 2026-05-12T09:49:48-04:00

  Update the default host and target files for dlltool support
  

• 5666c8f9
  by Duncan Coutts at 2026-05-12T09:49:48-04:00

  Add dlltool as a hadrian builder
  
  Optional except on windows.
  

• 5e14fe3f
  by Duncan Coutts at 2026-05-12T09:49:48-04:00

  Update and generate libHSghc-internal.def from .def.in file
  
  The only symbol that the rts imports from the ghc-internal package now
  is init_ghc_hs_iface. So the rts only needs an import lib that defines
  that one symbol.
  
  Also, remove the libHSghc-prim.def because it is redundant. The rts no
  longer imports anything from ghc-prim.
  
  Keep libHSffi.def for now. We may yet need it once it is clear how
  libffi is going to be built/used for ghc.
  

• 3d91e4a6
  by Duncan Coutts at 2026-05-12T09:49:48-04:00

  Add rule to build libHSghc-internal.dll.a and link into the rts
  
  On windows only, with dynamic linking.
  
  This is needed because on windows, all symbols in dlls must be resolved.
  No dangling symbols allowed. References to external symbols must be
  explicit. We resolve this with an import library. We create an import
  library for ghc-internal, a .dll.a file. This is a static archive
  containing .o files that define the symbols we need, and crucially have
  ".idata" sections that specifies the symbols the dll imports and from
  where.
  
  Note that we do not install this libHSghc-internal.dll.a, and it does
  not need to list all the symbols exported by that package. We create a
  special purpose import lib and only use it when linking the rts dll, so
  it only has to list the symbols that the rts uses from ghc-internal
  (which is exactly one symbol: init_ghc_hs_iface).
  

• c8dae539
  by Alice Rixte at 2026-05-12T09:50:52-04:00

  Script for downloading and copying `base-exports` file
  

• 5fab2238
  by Wolfgang Jeltsch at 2026-05-12T21:24:27+03:00

  Introduce a cache of home module name providers
  
  This contribution introduces to the module graph a cache that maps home
  module names to sets of units providing them and changes the finder to
  use that cache. This is a performance optimization, especially for
  multi-home-unit builds.
  
  The particular changes are as follows:
  
    * In `GHC.Unit.Module.Graph`, `ModuleGraph` is extended with a new
      field `mg_home_module_name_providers_map`, exposed as
      `mgHomeModuleNameProvidersMap`. This is a cache that assigns to each
      home module name the set of IDs of home units that define it.
      Operations that construct module graphs are updated such that this
      cache stays synchronized.
  
    * In `GHC.Unit.Finder`, `findImportedModule` is changed to pull
      `mgHomeModuleNameProvidersMap` from `hsc_mod_graph` and pass it to
      `findImportedModuleNoHsc`, which now does not search home units in
      arbitrary order but prioritizes those units that the cache mentions
      as potential providers of the requested module.
  
  In addition, this contribution adds variants of the two multi-component
  compiler performance tests that use 100 units instead of 20, because
  with just 20 units the benefits from caching of home module name
  providers are still negligible.
  
  The following table shows the total time needed for running both
  multi-component tests before and after this contribution and with
  different numbers of units:
  
  | # of units | Before | After |
  |-----------:|-------:|------:|
  |         20 |   0:12 |  0:12 |
  |        100 |   0:47 |  0:42 |
  |        200 |   3:05 |  2:08 |
  
  Note that there seems to be a general overhead of 12 seconds that is not
  attributable to the actual tests, so that the real running times should
  be 12 seconds smaller than shown above.
  
  Resolves #27055.
  
  Metric Decrease:
      MultiComponentModules
      MultiComponentModulesRecomp
  
  Co-authored-by: Matthew Pickering <matthewtpickering@gmail.com>
  Co-authored-by: Fendor <fendor@posteo.de>
  

• 38b76b2f
  by Cheng Shao at 2026-05-13T17:48:48-04:00

  testsuite: mark T22159 as fragile
  
  This patch marks T22159 as fragile on Windows for issue described in #27248.
  Before we get to the bottom of those failures, this unblocks newer
  Windows runners.
  

• 50188615
  by Ian Duncan at 2026-05-14T13:45:07+02:00

  AArch64: use ASR not LSR for MO_U_Shr at W8/W16
  
  The unsigned right shift (MO_U_Shr) for sub-word widths (W8, W16)
  with a variable shift amount was emitting ASR (arithmetic/signed shift
  right) after zero-extending with UXTB/UXTH. This should be LSR
  (logical/unsigned shift right). After zero-extension the upper bits
  happen to be 0 so ASR produces the same result, but it is semantically
  wrong and would break if the zero-extension were ever optimized away.
  Includes assembly output test (grep for lsr) and runtime test
  verifying unsigned right shift of Word8 and Word16 values.
  

• 28666fbf
  by Vladislav Zavialov at 2026-05-19T12:44:05-04:00

  Add type families: Tuple, Constraints, Tuple#, Sum# (#27179)
  
  These type families map tuples of types to the corresponding Tuple<N>,
  Tuple<N>#, CTuple<N>, and Sum<N># types. Some examples at N=2:
  
  	Tuple (Int, Bool)          = Tuple2 Int Bool
  	Constraints (Show a, Eq a) = CTuple2 (Show a) (Eq a)
  	Tuple# (Int#, Float#)      = Tuple2# Int# Float#
  	Sum# (Int#, Float#)        = Sum2# Int# Float#
  
  See GHC Proposal #145 "Non-punning list and tuple syntax".
  
  To make the Sum# instance at N=64 possible, this patch also introduces
  the Sum64# constructor declaration and bumps mAX_SUM_SIZE from 63 to 64.
  
  Metric Increase:
      ghc_experimental_dir
  

• 41c2448b
  by Wen Kokke at 2026-05-19T12:44:53-04:00

  rts: Add IPE event class for -l
  
  This commit adds a new IPE event class to the -l RTS flag.
  Previously, IPE events were enabled unconditionally.
  However, the IPE events can easily grow to hundreds or thousands of megabytes.
  With the new event class you can pass, e.g., -l-I to disable IPE events.
  

• 62536551
  by Wen Kokke at 2026-05-19T12:44:53-04:00

  ghc-internal: Add TraceFlags.traceIPE
  

• e45312d1
  by Wen Kokke at 2026-05-19T12:44:53-04:00

  testsuite: Add test for TraceFlags.traceIpe
  

• 4768d9aa
  by Wen Kokke at 2026-05-19T12:44:53-04:00

  ghc-internal: Add DebugFlags.ipe
  

• bc1b5c69
  by Wen Kokke at 2026-05-19T12:44:53-04:00

  testsuite: Add test for DebugFlags.ipe
  

• 0da1543f
  by Duncan Coutts at 2026-05-19T12:45:37-04:00

  Document removal of the signal-based interval timer
  
  Update mentions within the RTS section of the users guide.
  
  Add a changelog entry.
  

• b2911514
  by Duncan Coutts at 2026-05-19T12:45:37-04:00

  Fix section for an recent changelog entry
  

• d6d76a7a
  by David Eichmann at 2026-05-19T12:46:19-04:00

  ghc-toolchain: implement llvm program versioning logic
  

• 2dd36fa3
  by Wolfgang Jeltsch at 2026-05-20T04:49:52-04:00

  Turn `Trustworthy` into `Safe` in `base` where possible
  

• f4399dd1
  by Wolfgang Jeltsch at 2026-05-20T04:50:37-04:00

  Make the current `base` buildable with GHC 10.0
  

• 1a7de232
  by Duncan Coutts at 2026-05-20T12:26:25-04:00

  Hadrian: remove legacy rts .so symlinks
  
  For compatibility with the old makefile based build system, hadrian had
  rules to generate symlinks from unversioned to versioned names for the
  rts .so/.dynlib file, like libHSrts-ghcx.y.so -> libHSrts-1.0.3-ghcx.y.so
  
  We no longer need these symlinks since the makefile build system has
  been retired some time ago. The need for these symlinks is awkward on
  windows where we cannot (in practice) create symlinks. So rather than
  make them conditional (non-windows), just remove them entirely.
  

• 286f1adf
  by fendor at 2026-05-20T12:27:09-04:00

  Fix regression T27202: `:load` and `:add` work in GHCi
  
  To fix the regression there are conceptually two major things that we
  fix:
  
  * We don't remove the `importDirs` from `interactive-session`
  * When `:add`ing a module, we don't try to find them via PackageImports
      * The PackageImport is wrong as we can't know the package-name at
        this stage in ghc/UI.hs
  
  What does it mean to not remove the `importDirs` from
  `interactive-session`?
  It means that, given some initial `DynFlags`, we will use those
  `importDirs` in `interactive-session`.
  
  The initial `DynFlags`, however, depend on how you initialise the GHC
  session.
  For a simple session, initialised by
  
      ghc -isrc -this-unit-id main
  
  It is simple, just use the `DynFlags` given on the cli.
  Thus, `main` and `interactive-session` will have the same `DynFlags`,
  except for the `homeUnitId` and `interactive-session` depends on `main`
  by construction of the GHCi session.
  
  What about a multiple home unit session, though?
  
      ghc -unit @unit1 -unit @unit2
  
  What are the `DynFlags` in this cli invocation? It shouldn't be either
  `@unti1` nor `@unit2`, as the order shouldn't matter or any other
  implicit condition.
  
  For consistency, we decide that the initial `DynFlags` are the top
  `DynFlags` on the cli, ignoring `-unit` flags.
  Thus, in this example, there are no `importsDirs` regardless of what we
  might find in `@unit1` and `@unit2`.
  
  But in this invocation:
  
      ghc -isrc -unit @unit1 -unit @unit2
  
  The `interactive-session` will have the `importsDirs` `src`.
  Note, `-isrc` will be inherited in `@unit1` and `@unit2`, so you need to
  explicitly use `-i` to clear the `importsDirs`, in order to avoid
  accidentally adding `src` as an import directory to all other home
  units.
  
  This fix has been made possible by the improvements introduced in
  !15888, which avoids ambiguity when a home unit shares the `importsDirs`
  with the `interactive-session`, on top of being much faster for multiple
  home units.
  
  Adds regression tests for T27202 for `:load`ing and `:add`ing modules
  that are located in import directories.
  

• 728662de
  by fendor at 2026-05-20T12:27:09-04:00

  Use home unit package db stacks in GHCi prompt and session unit
  
  In order to import modules from home unit dependencies (e.g., `Data.Map`),
  the ghci prompt unit needs to populate its `UnitState`.
  This is tricky to handle correctly, which `PackageDBFlag`s should we use
  to populate the `UnitState`?
  We decide, the most intuitive solution for users is to depend on all
  `PackageDBFlag`s, so that any dependency can be imported in GHCi.
  This assumes consistency in the `PackageDBFlag`s, so no two home units
  specify `PackageDBFlag`s that are inconsistent with each other.
  
  We could simply concat all the `PackageDBFlag`s of the existing home
  units, but later `PackageDBFlag`s shadow earlier ones, leading to the
  last processed home units' `PackageDBFlag`s to shadow the earlier ones.
  This is hard to fix, we need to give users the capability to provide ghc
  options for the ghci prompt home unit.
  However, as this is considerably more work, we decided on an
  approximation that should work out most of the time.
  
  Package Db stacks in cabal and stack follow a certain structure:
  
      -no-user-package-db > -package-db $cabal-store > -package-db $local-db
  
  The first two arguments are always the same, namely the
  `-no-user-package-db` and `-package-db`.
  We compute the longest common prefix over all home units, and use that
  as the start of the package db stack. Then, over the rest of the
  `PackageDBFlag`s, we simply take the union and append them to our
  initial stack.
  We assume, that the rest of package dbs only defines very few, "local"
  units that are usually not shadowing each other.
  
  This allows us to get a relatively consistent package database stack for
  the ghci prompt home unit.
  
  Similar reasoning applies to the session unit in order to add modules to
  the session and have dependencies available in the module.
  
  We do something similar for `-package` flags, to make sure only the
  correct units are actually visible in the ghci session.
  This time, we simply take the union of all `PackageFlag`s, allowing us
  to import modules from the home unit dependencies.
  
  In the future, it would be beneficial to allow the user to provide the
  exact ghc options to control the visibilities. For now, this will have
  to do.
  

• 740d89a0
  by Simon Peyton Jones at 2026-05-20T17:20:44-04:00

  Do not use mkCast during typechecking
  
  This commit fixes #27219.  The problem was that the typechecker was using
  `mkCast`, whose assertion checks legitimately fail when applied to types
  that contain unification variables.
  

• a50fdb06
  by Simon Peyton Jones at 2026-05-20T17:20:45-04:00

  Major refactor of the Simplifier
  
  The main payload of this patch is to refactor the Simplifer to avoid
  repeated simplification when using Plan (AFTER) for rule rewrites.
  The need for this was shown up by #26989.
  
  See Note [Avoid repeated simplification] in GHC.Core.Opt.Simplify.Iteration.
  
  Related refactoring:
  
  * Refactor the two fields `sc_dup` and `sc_env` in `ApplyToVal` into one, `sc_env`.
    Reason: the envt is irrelevant in the "simplified" case, so the data type describes
    the possiblitiies much more accurately now.
  
  * Some refactoring in `knownCon` to split off `wrapDataConFloats`.
  
  * Refactor `lookupRule` and its auxiliary functions to return `RuleMatch`,
    a new data type. See Note [data RuleMatch] in GHC.Core. Ditto for BuiltinRule.
  
    This RuleMatch returns fragments of the target in rm_args and rm_floats,
    leaving `rm_rhs` to be the stuff from the RULE itself.
  
    Doing this has routine consequences in GHC.Core.Opt.ConstantFold. Many changes
    there but all routine.
  
  * When doing occurrence analysis on RULEs, make the occ-info on the rule
    binders relate just to the RHS, not the LHS.  See (OUR1) in
    Note Note [OccInfo in unfoldings and rules]
  
    This means that Lint must not complain about the fact that the patterns
    in the RULE mentions binders that are marked dead.
    See Note [Dead occurrences] in GHC.Core.Lint.
  
    I changed the Core pretty-printer so that it didn't suppress dead binders,
    else I can't see those binders in RULEs.  That led to quite a lot of testsuite wibbles.
  
  * Refactor FloatBinds, so that it is used both by
    `exprIsConApp_mabye` and by `lookupRule`
    * Move the definition of FloatBinds out of GHc.Core.Make, into GHC.Core.
    * Add FloatTick as an extra constructor.
    * Refactor `lookupRule` to use `FloatBinds` instead of `BindWrapper`.
    This refactor just shares more code.
  
    (Rename GHC.Core.Opt.FloatOut.FloatBinds to FloatLets, to avoid gratuitious
    name clash with GHC.Core.FloatBinds.)
  
  Corecion optimisation
  
  * In simpleOpt, when composing coercions, call new function `optTransCo`.
    This is much lighter weight than full blown coercion optimisation.
  
  * Make `GHC.Core.Opt.Arity.pushCoValArg` and `pushCoTyArg` return the
    coercionLKind of the coercion. This saves recomputing that coercionLKind
    at the key call sites in GHC.Core.Opt.Simplify.Iteration.pushCast.
  
  * Rename `addCoerce` in GHC.Core.Simplify.Iteration to become `pushCast`.
  
  * In the `ApplyToVal` case of `pushCast` we had a very unsavoury call to `simplArg`.
    I eliminated it by adding a field `sc_cast` to `ApplyToVal` that records any
    pending casts.  Much nicer now.  See Note [The sc_cast field of ApplyToVal].
  
  * Don't optimise coercions if the type-substitution is empty.
    See Note [Optimising coercions] in GHC.Core.Opt.Simplify.Iteration.
  
  The fix for #26838 is dramatic.  For the test in perf/compiler/T26839 we have
  
     Compiler allocs:  Before: 7,363M
                       After:    688M
  
  Compile time goes down generally.  Here are compiler-alloc changes
  over 0.5%:
             CoOpt_Read(normal)    729,184,920   -0.7%
       CoOpt_Singletons(normal)    666,916,960   -4.6% GOOD
            LargeRecord(normal)  1,227,056,876   +1.1%
                 T12227(normal)    256,827,604   -4.6% GOOD
                 T12425(optasm)     76,879,410   -0.8%
                 T12545(normal)    787,826,918  -10.8% GOOD
                 T12707(normal)    775,186,464   -0.9%
                 T13253(normal)    318,599,596   -0.8%
                 T14766(normal)    685,857,320   -1.0%
                 T15304(normal)  1,123,333,422   -2.2%
                 T15630(normal)    123,142,330   -2.6%
                T15630a(normal)    123,092,100   -2.6%
                 T15703(normal)    299,751,682   -2.9% GOOD
                 T17516(normal)    964,072,280   +1.0%
                 T18223(normal)    367,016,820   -6.2% GOOD
                 T18730(optasm)    130,643,770   -3.3% GOOD
                 T20261(normal)    535,608,584   -0.7%
                T21839c(normal)    340,340,436   -0.9%
                 T24984(normal)     85,568,392   -1.9%
                  T3064(normal)    174,631,992   -1.2%
                  T3294(normal)  1,215,886,432   -0.7%
                  T5030(normal)    141,449,704  -17.2% GOOD
               T5321Fun(normal)    258,484,744   -1.9%
                  T8095(normal)    770,532,232   -2.7%
                  T9630(normal)    858,423,408  -14.5% GOOD
                 T9872c(normal)  1,591,709,448   +0.7%
    info_table_map_perf(normal) 19,700,614,458   -1.3%
  
                      geo. mean                  -0.7%
                      minimum                   -17.2%
                      maximum                    +1.1%
  
  However, strangely there seems to be a 5.0% increase in CoOpt_Read in
  the x86_64-linux-fedora43-validate+debug_info+ubsan job, although
  there generally a /decrease/ in this test in other builds.  The baseline
  value looks strange.  Anyway I'll just accept it.
  
  Metric Decrease:
      CoOpt_Singletons
      T12227
      T12545
      T12707
      T15703
      T18223
      T18730
      T21839c
      T5030
      T9630
  
  Metric Increase:
      CoOpt_Read
  

• 834623d4
  by Mrjtjmn at 2026-05-20T17:21:41-04:00

  users-guide: Fix weird notation in "Summary of stolen syntax"
  

• 6f9d7c71
  by Markus Läll at 2026-05-21T15:25:34-04:00

  Use "grimily" instead of "grimly"
  
  Fixes https://gitlab.haskell.org/ghc/ghc/-/issues/27221
  

• 50e999ca
  by fendor at 2026-05-21T15:26:18-04:00

  Speed up 'closure' computation in `ghc-pkg`
  
  Cache the set of already seen `UnitId`s and use `Set` operations to
  speed up 'closure' computation.
  
  Further simplify the implementation of 'closure' to account for the
  actual usage.
  As a consequence, we rename 'closure' to 'brokenPackages' to reflect its
  purpose better after the simplification.
  

• 7ecc6184
  by sheaf at 2026-05-21T15:27:10-04:00

  TcMPluginHandling: be more lenient when no plugins
  
  This change ensures that, if a function such as 'typecheckModule' was
  invoked with 'NoTcMPlugins', GHC doesn't spuriously complain about TcM
  plugins having already been stopped, as there were none to start with.
  

• 72c8de5c
  by Simon Jakobi at 2026-05-23T18:41:42-04:00

  Implement List.elem via foldr
  
  ...in order to allow specialization to Eq instances.
  
  The implementation of notElem is updated for consistency.`
  
  Corresponding CLC proposal:
  https://github.com/haskell/core-libraries-committee/issues/412
  
  Addresses #27096.
  

• 3268c610
  by Alan Zimmerman at 2026-05-23T18:42:30-04:00

  EPA: Fix span for qualified multiline string
  
  Fix the span for a qualified multiline string like
  
    Text."""
      I'm a multiline
      Text value
      !
    """
  
  to extend to the end of the entire string, not just the first line.
  
  Closes #27274
  

• 1f096790
  by Alan Zimmerman at 2026-05-23T18:43:20-04:00

  EPA: Fix exact printing namespace-specified wildcards
  
  Ensures correct printing of imports of the form
  
     import Data.Bool (data True(data ..))
     import Data.Bool (data True(type ..))
  
  Closes #27291
  

• 56ada7c0
  by Mrjtjmn at 2026-05-23T18:44:19-04:00

  Fix ambiguous syntax of BangPatterns in users guide
  
  Update documentation for the BangPatterns extension to specify
  how surrounding whitespace affects interpretation of `!`.
  
  * Only when there is whitespace before `!` and no whitespace after,
    it is recognized as a BangPattern.
  * Other cases `⟨varid⟩!⟨varid⟩`, `⟨varid⟩ ! ⟨varid⟩`, `⟨varid⟩! ⟨varid⟩`
    are treated as infix operators.
  

• 579aa0b7
  by Simon Jakobi at 2026-05-25T16:31:26-04:00

  Ensure that SetOps.{minusList,unionListsOrd} can be specialized
  
  ...by marking them INLINABLE. Haddock allocates 0.1–0.3% less as a
  result.
  
  This also removes some redundant constraints on unionListsOrd.
  

• cccf45da
  by Cheng Shao at 2026-05-25T16:32:13-04:00

  wasm: ensure post-linker output is synchronous ESM
  
  This patch fixes wasm backend's post-linker output script to ensure
  it's synchronous ESM and doesn't use top-level await, which doesn't
  work in ServiceWorkers. Fixes #27257.
  

• 8db331a3
  by Zubin Duggal at 2026-05-26T04:54:03-04:00

  Update to semaphore-compat 2.0.0 using v2 of the protocol
  
  On Linux and other POSIX platforms, GHC's -jsem jobserver client now
  speaks v2 of the semaphore-compat protocol, which uses Unix domain
  sockets in place of POSIX named semaphores. This avoids the libc-ABI
  issues that affected the old implementation. Windows is unaffected
  and continues to use the v1 protocol (Win32 named semaphores); its
  reported protocol version remains v1.
  
  When GHC receives a -jsem name whose protocol version it does not
  support, it emits a -Wsemaphore-version-mismatch warning and falls
  back to -j<N> rather than crashing. ghc --info exposes the supported
  version in a new "Semaphore version" entry so cabal-install can detect
  a mismatch before invoking GHC.
  
  Users on a cabal-install that predates the v2 update will continue to
  build successfully on Linux/POSIX, but will lose the cross-process
  -jsem coordination and fall back to -j<N> per GHC invocation. Users
  must upgrade to a cabal-install that supports protocol v2 to recover
  full parallelism.
  
  Also fix a leak in cleanupSem (#27253): cleanupSem used to snapshot
  heldTokens and release them before killing the loop, while the loop's
  in-flight acquire/release children could still be mutating it.
  Cleanup now runs inside the loop's own exit handler, after draining
  the active child via a new activeChild TVar, so the snapshot has no
  concurrent mutator.
  
  See also:
    - GHC proposal amendment:  https://github.com/ghc-proposals/ghc-proposals/pull/673
    - cabal-install patch:     https://github.com/haskell/cabal/pull/11628
    - semaphore-compat MR:     https://gitlab.haskell.org/ghc/semaphore-compat/-/merge_requests/8
  
  Bump semaphore-compat submodule to 2.0.0
  
  Fixes #25087 and #27253
  

• 17be4f1f
  by Alan Zimmerman at 2026-05-26T04:54:52-04:00

  EPA: Record semicolons in HsModifier
  
  Ensure the semi colons are captured in the ParsedSource for code like
  
    %True;; %False;
    instance C D
  
  It makes HsModifier (and hence HsModifierOf) LocatedA, so the semi
  colons can be recorded as [TrailingAnn]
  
  Also rename pprHsModifiers to pprLHsModifiers to match.
  
  Closes #27294
  

• 8f991755
  by fendor at 2026-05-26T11:02:52-04:00

  Revert prog003 acceptance
  
  We thought the commit 286f1adff3e78d775ff325caff71d0cee25d710b fixed the
  test, but due to changes to ghci, modules loaded during the GHCi
  session, the test was actually no longer testing what it set out to do,
  "fixing" the broken test.
  
  As modules are added to the `interactive-session` home unit, the object code needs
  to be compiled with `-this-unit-id interactive-session`, otherwise the
  object code won't be used.
  Once this has been fixed in the test, the test fails as expected again.
  

• 277a3687
  by mangoiv at 2026-05-26T11:03:40-04:00

  libraries/process: bump submodule to v1.6.29.0
  
  This submodule bump resolves a segfault on macos 15.
  Fixes #27144
  

• 6779bb0c
  by mangoiv at 2026-05-26T11:03:40-04:00

  libraries/unix: in submodule, don't pick branch 2.7
  
  The 2.7 branch is outdated and the module has been advanced far beyond
  it anyway, so remove that line.
  

• 4a645683
  by Simon Peyton Jones at 2026-05-27T21:41:59-04:00

  Trim the continuation in mkDupableContWithDmds
  
  When there are no remaining argument demands, it means the application
  is bottoming. In this case, we can trim the continuation to avoid the
  panic that was observed in #27261.
  
  See Note [Trimming the continuation for bottoming functions] in
  GHC.Core.Opt.Simplify.Iteration.
  

• 8ab506ff
  by Cheng Shao at 2026-05-27T21:42:47-04:00

  ghci: fix module name string lifetime in hs_hpc_module invocation
  
  This patch makes hpcAddModule pass a properly malloced module name
  string to hs_hpc_module, instead of using useAsCString which causes
  use-after-free of module name string. Fixes #27297.
  
  Co-authored-by: Codex <codex@openai.com>
  

• b0233814
  by sheaf at 2026-05-27T21:43:31-04:00

  Relax acceptance threshold for T10421
  
  As seen in #27289, the 1% acceptance threshold for this text was
  overly narrow, resulting in spurious test failures. This commit widens
  the acceptance threshold to 2%. Fixes #27289.

• 63ce5770
  by Luite Stegeman at 2026-05-28T12:23:35-04:00

  Fixes for black holes
  
   - suspend duplicate work for eager black holes
   - detect eager black holes in checkBlockingQueues
   - don't overwrite existing black holes even if they're not
       in an eager blackhole frame
   - don't deadlock on self when thunk is already blackholed
  
  Fixes #26936
  

• 037a80dc
  by Tom McLaughlin at 2026-05-28T12:24:36-04:00

  Event/Windows.hsc: rethrow exceptions in overlapped IO
  
  This prevents the WinIO manager from swallowing exceptions in overlapped IO. It
  was added to make WinIO support possible in the `network` library. See
  https://gitlab.haskell.org/ghc/ghc/-/issues/27283.
  
  We also bump __IO_MANAGER_WINIO__ to 2 so libraries can gate on this using CPP.
  

• 2d53bcdb
  by Wolfgang Jeltsch at 2026-05-28T12:25:21-04:00

  Allow `downsweep` to use nodes of an existing module graph
  
  To this end, `downsweep` has not been able to use the nodes of a module
  graph obtained from a previous downsweeping round. In some GHC API
  applications, downsweeping is performed somewhat incrementally and
  therefore could profit from reusing such existing results. This
  contribution makes this possible.
  
  Resolves #27054.
  
  Co-authored-by: Matthew Pickering <matthewtpickering@gmail.com>
  

• f4fbb583
  by Simon Jakobi at 2026-05-28T12:26:04-04:00

  Add regression test for T11226
  
  Closes #11226.
  

• ed29a5e6
  by Sven Tennie at 2026-05-28T17:30:36-04:00

  Add optional config setting for LibDir (#19174)
  
  Previously, the `libDir` was derived from `topDir`. This won't work for
  inplace stage2 cross-compilers where binaries and libraries are in
  different stage dirs (`_build/stage1/` for executables and
  `_build/stage2` for libraries).
  
  `LibDir` is set in the inplace `settings` files. For bindists, we
  generate a new `settings` file with no `LibDir` entry. GHC then defaults
  to use `topDir` as `libDir` again. This keeps the bindist relocatable.
  
  If `LibDir` is a relative path, it is interpreted relatively to
  `topDir`.
  
  The global package db is part of the `lib/` folder. If we want to point
  for inplace cross-compilers to the succeeding stage's folder, this is
  done by setting `LibDir`. Thus, the global package db must be found
  relative to `libDir`` (which may default to `topDir` or be set by
  `LibDir`).
  
  The complexity of settings becomes scary. So, add a test to ensure
  `LibDir` works as expected.
  

• 8339cf8f
  by Sven Tennie at 2026-05-28T17:30:36-04:00

  Add Haddock to FileSettings
  
  Helping to understand the fields' meanings without deeper analyses.
  

• 4ce251e4
  by Sylvain Henry at 2026-05-28T17:31:39-04:00

  foundation test: skip signed minBound `quot` (-1) (#27222)
  
  `minBound `quot` (-1)` for fixed-width signed integers is platform
  dependent: the mathematical result -minBound is not representable in
  the type. On x86, IDIV traps; LLVM's sdiv is undefined behaviour in
  this case; on AArch64/RISC-V, SDIV wraps to minBound.
  
  Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
  

• b8ba7e61
  by Simon Jakobi at 2026-05-28T17:32:23-04:00

  Prevent dictionary-passing in checkTyEqRhs
  
  ...by pre-specializing it to TcM.
  
  Previously, wherever checkTyEqRhs was used in other modules, the
  Core showed dictionary passing ($fMonadIOEnv). The added SPECIALIZE
  pragma prevents this.
  

• d603477f
  by David Eichmann at 2026-05-29T13:17:12-04:00

  Hadrian: create a ghc-internal .def file per ghc-internal dll
  
  The .def file generated from rts/win32/libHSghc-internal.def.in contains
  the name of the ghc-internal dll. The correct dll name differs based
  on if the dll is inplace/final and if using the Dynamic way. Previously,
  this was not accounted for and inconsistent dlls names where used. That
  led to failure when loading dlls at runtime in experiments with windows
  dynamic linking.
  

• 1fc21753
  by Sylvain Henry at 2026-05-29T13:18:14-04:00

  ghc-bignum: copy backend interface haddocks to Native backend (#27305)
  
  The haddock comments documenting the BigNat backend interface (function
  contracts, expected MutableWordArray# sizes, return-value semantics, etc.)
  were attached to the FFI backend module. Copy them to the Native backend
  so they remain in tree once the FFI backend is removed.
  
  Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
  

• 717059df
  by Sylvain Henry at 2026-05-29T13:18:14-04:00

  ghc-bignum: remove FFI backend (#27305)
  
  The FFI backend of ghc-bignum (now part of ghc-internal) had no known
  users and is easy to recreate by relinking ghc-internal with a custom
  backend. Remove the backend module, the bignum-ffi cabal flag, and the
  ffi option from Hadrian's --bignum selector. The backend interface
  documentation now lives in the Native backend module.
  
  Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
  

• 4bb3b1d8
  by Sylvain Henry at 2026-05-29T13:18:14-04:00

  ghc-bignum: remove Check backend (#27305)
  
  The Check backend of ghc-bignum (now part of ghc-internal) compared the
  selected backend's output against the Native backend for validation.
  It had no known users. Remove the backend module, the bignum-check
  cabal flag, the bignumCheck Hadrian flavour field, and the check-
  prefix in Hadrian's --bignum selector.
  
  Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
  

• 6b3044a0
  by David Eichmann at 2026-05-30T11:58:48-04:00

  Add code comments to allocator code
  

• f4e04210
  by Matthew Pickering at 2026-05-30T11:59:34-04:00

  hadrian: Refactor system-cxx-std-lib rules
  
  I noticed a few things wrong with the hadrian rules for
  `system-cxx-std-lib` rules.
  
  * For `text` there is an ad-hoc check to depend on `system-cxx-std-lib`
  outside of `configurePackage`.
  * The `system-cxx-std-lib` dependency is not read from cabal files.
  * Recache is not called on the packge database after the `.conf` file is
  generated, a more natural place for this rule is `registerRules`.
  
  Treating this uniformly like other packages is complicated by it not
  having any source code or a cabal file. However we can do a bit better
  by reporting the dependency firstly in `PackageData` and then needing
  the `.conf` file in the same place as every other package in
  `configurePackage`.
  
  This commit increases the `shakeVersion`, to provide backwards
  compatibility to previous builds with different PackageData.
  
  Fixes #25303
  
  Co-authored-by: Sven Tennie <sven.tennie@gmail.com>
  

• 576987d0
  by Simon Jakobi at 2026-06-02T04:53:36-04:00

  compiler: use nubOrd from containers
  
  Address #27103 by replacing GHC.Utils.Misc.ordNub[On] with
  Data.Containers.ListUtils.nubOrd[On].
  
  Note that nubOrd suffers from a small inefficiency, a fix for which
  will be included in the next containers release:
  
    https://github.com/haskell/containers/issues/1202
  

• deea53c3
  by David Eichmann at 2026-06-02T04:54:22-04:00

  Hadrian: disable response files for GHC/Haddock builders on non-Windows
  
  This makes debugging build errors easier on non-windows hosts.
  See issue #27230
  

• f2f5c6ba
  by Nikita Efremov at 2026-06-02T16:04:54+00:00

  fix typo : compete with performance, not complete

• 5524ea0e
  by Wolfgang Jeltsch at 2026-06-03T08:01:26-04:00

  Make the current `base` buildable with GHC 9.14
  
  This comprises the following changes:
  
    * Disable some imports into `GHC.Base` for GHC 9.14
    * Disable some imports into `Prelude` for GHC 9.14
    * Disable separate `ArrowLoop` import for GHC 9.14
    * Disable `GHC.Internal.STM` import for GHC 9.14
    * Disable `GHC.Internal.Unicode.Version` import for GHC 9.14
    * Disable `GHC.Internal.TH.Monad` import for GHC 9.14
    * Add alternative `fixIO` import for GHC 9.14
    * Add alternative `unsafeCodeCoerce` import for GHC 9.14
    * Disable hiding of imported SIMD operations for GHC 9.14
    * Disable use of GHC 9.14’s `printToHandleFinalizerExceptionHandler`
    * Enable use of `getFileHash` from `ghc-internal` for GHC 9.14
    * Make `thenA` available for GHC 9.14
    * Make `thenM` available for GHC 9.14
    * Disable translation of `IoManagerFlagPoll` for GHC 9.14
    * Add `hGetNewlineMode` for GHC 9.14
  

• d3438055
  by Enrico Maria De Angelis at 2026-06-03T08:02:17-04:00

  Fix #27067 - Clarify haddocks on `minusNaturalMaybe`
  

• f9bcfac2
  by sheaf at 2026-06-03T14:47:19-04:00

  Avoid mkTick in Core Prep breaking ANF
  
  As discovered in #27182, mkTick can break ANF. This patch introduces a
  variant of mkTick that skips the single optimisation that could break
  ANF. This is preferrable over switching to the raw Tick constructor,
  as the latter may introduce spurious cost centres in profiling reports.
  
  This is a temporary measure until we more thoroughly refactor how
  mkTick works (see #27141).
  
  See Note [mkTick breaks ANF] in GHC.CoreToStg.Prep.
  
  Fixes #27182
  

• cf1fd661
  by Artem Pelenitsyn at 2026-06-03T14:48:09-04:00

  clarify comment for getSizeofMutableByteArray#: we get the size in bytes, not "elements"

• a3b431f3
  by David Eichmann at 2026-06-04T10:10:19+00:00

  Hadrian: convert env variable ACLOCAL_PATH to unix paths.
  
  Convert ACLOCAL_PATH to a unix style path when invoking autoreconf.
  Autoreconf doesn't handle windows paths.
  See Note [Autoreconf unix paths from ACLOCAL_PATH].
  
  Fixes #27311
  

• 18f6138a
  by Simon Jakobi at 2026-06-04T20:20:31-04:00

  testsuite: Deduplicate --only test names
  
  config.only is assumed to be a set, but supplying --only overwrote it
  with the (list) argparse result, which can contain duplicates. When a
  test ran, config.only.remove(name) dropped only the first occurrence,
  so a duplicated name lingered and was later misreported as a
  "test not found" framework failure. Store it as a set instead.
  
  Fixes #27322
  
  Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
  

• 2f3cc9ff
  by Simon Jakobi at 2026-06-08T07:55:49-04:00

  testsuite: detect fast bignum via ghc-internal, not removed ghc-bignum
  
  The ghc-bignum package was merged into ghc-internal, so the BIGNUM_GMP
  probe in test.mk ran `ghc-pkg field ghc-bignum exposed-modules`, which
  fails with "cannot find package ghc-bignum". That error went to stderr
  and leaked into the captured stderr of every makefile_test, causing
  spurious [bad stderr] failures across the suite. The probe also silently
  returned empty, so config.have_fast_bignum was wrongly False even on GMP
  builds.
  
  Probe ghc-internal's extra-libraries for the gmp library instead: the
  GMP backend module is an other-module (not exposed), but GMP_LIBS adds
  gmp to extra-libraries only on a GMP build, so this distinguishes the
  backends. Redirect stderr to keep any future missing-package error off
  the harness's stderr.
  
  This also removes a stale comment as per suggestion from hsyl20.
  
  Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
  

• eb3bf6e7
  by Alan Zimmerman at 2026-06-08T07:56:32-04:00

  EPA: Rename Transform.anchorEof to addModuleCommentOrigDeltas
  
  This now matches what it actually does.
  

• 498bb21a
  by David Eichmann at 2026-06-09T18:02:39-04:00

  Hadrian: avoid response files when command line is short enough
  
  This replaces the logic of always using response files on Windows.
  With the new condition based on command line lenght, reponse files
  can be avoided in many more cases (on windows).
  
  Now that response files are only used in a small number of cases,
  response files are always kept and the -r / --keep-response-files
  command line options have been removed
  
  The response file paths are nolonger randomized. They are placed in the
  `_build/rsp` directory. This ensures they are ignored by git and we
  that Hadrian reuses response file paths when rebuilding rather than
  leaving stale response files around.
  
  Update user guide putting response files in its own section
  

• 87f510a5
  by Simon Hengel at 2026-06-09T18:03:25-04:00

  Don't use non-breaking spaces
  

• 41a19379
  by David Eichmann at 2026-06-09T18:04:11-04:00

  Hadrian: remove unused wrapper scripts from windows bindist
  
  These wrapper scripts are only installed on non-relocatable builds
  which are not generally supported on windows.
  

• ce01ccb6
  by sheaf at 2026-06-10T05:08:48-04:00

  Don't drop ticks around variables of type `IO ()`
  
  GHC.Core.Utils.mkTick is responsible for placing a tick on a Core
  expression. It contains logic for dropping SCCs (non-counting profiling
  ticks) around non-function variables, as such variables cannot
  meaningfully contribute to profiles. However, the logic for what counts
  as a function was incorrect: it used `isFunTy` which returns 'False' for
  types such as 'IO ()' where the function arrow is hidden under a
  newtype.
  
  We now use 'mightBeFunTy' instead of 'isFunTy'. This ensures we don't
  drop ticks in cases we aren't sure.
  
  On the way, we improve the documentation of 'isFunTy', 'isPiTy' and
  'mightBeFunTy', and update the latter's implementation to consistently
  handle unary classes.
  
  Fixes #27225
  
  -------------------------
  Metric Decrease:
      T5642
  -------------------------
  

• d311c4f1
  by Simon Jakobi at 2026-06-10T05:09:32-04:00

  testsuite: Add regression test for #4081
  
  Check that a strict constructor field is unboxed once outside an
  enclosing loop, not re-inspected each iteration (the float-out
  case-floating from 9cb20b488). Uses simonpj's `data T a = T !a` example
  from the ticket; T4081.stderr captures the expected Core.
  
  Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
  

• 333df444
  by sheaf at 2026-06-10T05:10:25-04:00

  Check for cabal-install >= 3.12 upfront
  
  Starting with commit 8cb99552f607f6bc4000e45ab32532d50c8bb996, Hadrian
  requires cabal-install >= 3.12 in order to use the 'cabal path' command
  that was introduced in version 3.12, as per
    https://github.com/haskell/cabal/blob/a51c4ee1556d816ad86e90db7e6330dd51b0b6e7/release-notes/cabal-install-3.12.1.0.md?plain=1#L45
  
  This was not reflected in the Hadrian build script, causing a delayed
  build failure instead of enforcing the version requirement upfront,
  which this patch does.
  
  Fixes #27317
  

• 98c20394
  by sheaf at 2026-06-10T05:11:09-04:00

  Fix crash in Data.Data instance for HsCtxt
  
  The Data.Data instance for HsCtxt contained an error for the 'toConstr'
  method, which could trigger for example when looking at -ddump-tc-ast
  traces. Replace it with the 'abstractConstr' pattern used in the rest of
  the codebase.
  

• 5ac9ce7d
  by Zubin Duggal at 2026-06-10T21:26:32+05:30

  hadrian: Remove old package.conf files when generating new ones
  
  Old package.conf files might exists with different hashes, causing issues like #26661
  
  Fixes #26661
  

• c9015f09
  by sheaf at 2026-06-11T12:40:28-04:00

  Fix AArch64 clobbering bug for MUL2
  
  On AArch64, the code generator could clobber one of the input operands
  when computing the lower bits of a MUL2 operation. This rendered invalid
  the subsequent computation of the high bits.
  This commit fixes that by using a temporary register. The register
  allocator can remove the redundant move in the common case when the
  registers do not conflict.
  
  Fixes #27046
  

• 7ab90288
  by Rodrigo Mesquita at 2026-06-11T12:41:11-04:00

  fix: make T27131 less flaky
  
  It seems that T27131 fails flakily in a race where we check the flag
  before the capability had the chance to process the mailbox which sets
  the flag. This seemingly should only happen if the capability ends up
  being the same for setting and checking the flag.
  

• 8965cb76
  by Marc Scholten at 2026-06-12T04:53:22-04:00

  haddock: render modules concurrently
  

• 8cc0b64a
  by Duncan Coutts at 2026-06-12T04:54:06-04:00

  Promote HAVE_PREEMPTION from Timer.c to OSThreads.h
  
  We will want to know about HAVE_PREEMPTION in more places.
  
  HAVE_PREEMPTION tells us that we do have OS threads available,
  irrespective of whether THREADED is defined. In particular,
  HAVE_PREEMPTION is defined on all proper OSs, but not on WASM (and
  hyopthetically may not be true on some other platforms like
  micro-controllers, RTOSs, VM hypervisors etc).
  

• cce574ed
  by Duncan Coutts at 2026-06-12T04:54:06-04:00

  Define ACQUIRE_LOCK_ALWAYS and friends
  
  Fix issue #27335
  
  Like the atomic _ALWAYS variants, these lock actions are always defined,
  rather than being dependent on whether we are in the THREADED case. All
  the "normal" LOCK macros are defined to be no-ops when !THREADED.
  
  The use case for the _ALWAYS variants is where we are using OS threads
  even in the non-threaded RTS. This includes everything to do with the
  timer/ticker thread, which is used in the non-threaded RTS too.
  
  In particular, we will want to use this for eventlog things, because the
  timer thread performs eventlogging concurrently with the main
  capability, even in the non-threaded RTS.
  

• 1f28d1f6
  by Duncan Coutts at 2026-06-12T04:54:06-04:00

  Use ACQUIRE/RELEASE_LOCK_ALWAYS with eventBufMutex
  
  Even in the non-threaded RTS the eventBufMutex is needed by both the
  main capability and the timer/ticker thread, so always use the mutex.
  
  This should fix #25165 which is about the main capability and the timer
  thread posting events to the eventlog buffer concurrently and thereby
  corrupting the buffer data.
  

• 0ff29782
  by Duncan Coutts at 2026-06-12T04:54:06-04:00

  Expose eventBufMutex in the EventLog interface/header
  
  We will need it in forkProcess to ensure we don't write to the global
  eventlog buffer concurrently with trying to flush eventlog buffers and
  do the fork().
  

• 7a688395
  by Duncan Coutts at 2026-06-12T04:54:07-04:00

  Split flushAllCapsEventsBufs into safe and unlocked version
  
  Following the convention that unlocked versions have a trailing _
  underscore in their name. This one requires the caller to hold the
  eventlog global buffer mutex. We will need this in forkProcess.
  

• 341ed474
  by Duncan Coutts at 2026-06-12T04:54:07-04:00

  Remove redundant use of stopTimer in setNumCapabilities
  
  Historically, the comment here was:
  
    We must stop the interval timer while we are changing the
    capabilities array lest handle_tick may try to context switch
    an old capability. See #17289.
  
  and
  
    We must disable the timer while we do this since the tick handler may
    call contextSwitchAllCapabilities, which may see the capabilities array
    as we free it.
  
  What this refers to is that historically, when changing the number of
  capabilities, the array of capabilities was reallocated to a new size,
  allocating new ones and freeing the old ones, thus invalidating all
  existing capbility pointers.
  
  Strangely, for good measure the code used to call stopTimer twice (hence
  the two similar comments above).
  
  However, since commit a3eccf06292dd666b24606251a52da2b466a9612, the
  capabilities array is no longer reallocated. Instead the array is
  allcoated once on RTS startup to the maximum size it could ever be
  allowed to be, and then capabilities get enabled/disabled at runtime. So
  the capability pointers never become invalid anymore. At worst, they may
  point to capabilities that are disabled.
  
  Thus we no longer need to stop the timer (twice) while we change the
  number of enabled capabilities. This also partially solves issue #27105,
  which notes that stopTimer is being used as if it were synchronous, when
  it is not. At least for this case, the solution is that stopTimer is not
  needed at all!
  

• 674858e3
  by Duncan Coutts at 2026-06-12T04:54:07-04:00

  Remove redundant use of stopTimer in forkProcess
  
  but replace it with taking the eventlog buffer lock during the fork.
  
  Fixes issue #27105
  
  The original reason to block the timer during a fork was that
  historically the timer was implemented using a periodic timer signal,
  and the signal itself would interrupt the fork system call (returning
  EINTR). For large processes (where fork() takes a while) this could
  permanently livelock: the timer always would go off before the fork
  could complete, which got retried in a loop forever.
  
  The timer is no longer implemented as a unix signal, but uses threads.
  Thus the original problem no longer exists. The only remaining reason to
  block the timer tick is to prevent actions taken by the tick from
  interfering with the delicate process involved in fork (taking a load of
  locks and pausing everything).
  
  The only thing we need to do is to prevent the eventlog from being
  written to or flushed while the fork is taking place. To achieve this
  all we need to do is hold the mutex for the global eventlog buffer.
  
  This removes the last use of stopTimer that expects stopTimer to work
  synchronously (which it was not) and thus solves issue #27105. To be
  clear, we solve issue #27105 not by making stopTimer synchronous, but by
  eliminating the use sites that expected it to be synchronous.
  

• 40764930
  by sheaf at 2026-06-12T14:54:43-04:00

  Add type family performance test for #26426
  
  Some GHC versions produced large numbers of coercions after typechecking
  and desugaring when compiling the program in #26426:
  
  Version | Typechecker time | Typechecker allocations | Coercions
  -------:|-----------------:|------------------------:|---------:
  9.6     |   47 ms          |  48 MB                  |    110k
  9.8     | 1000 ms          | 486 MB                  | 10,437k
  9.10    |  922 ms          | 489 MB                  | 10,436k
  9.12    |  906 ms          | 482 MB                  | 10,437k
  9.14    |   63 ms          |  55 MB                  |    333k
  10.0    |   47 ms          |  64 MB                  |     35k
  
  The improvement 9.12 -> 9.14 was due to commit 22d11fa818fae2c95c494fc0fac1f8cb4c6e7cb6,
  while the improvement 9.14 -> 10.0 was due to commit 0b7df6db9e46df40e86fbff1a66dc10440b99db5.
  
  As the behaviour of GHC seems better than it's ever been on this program,
  we declare victory, adding this performance test to ensure we don't
  regress on this program.
  
  On the way, we update Note [Combining equalities] in GHC.Tc.SolveR.Equality
  with the explanation of the 9.12 -> 9.14 improvement (getting rid of an
  exponential blowup in coercion sizes), and we update
  Note [Exploiting closed type families] in GHC.Tc.Solver.FunDeps with
  the explanation of the 9.14 -> 10.0 improvement (bringing down coercion
  size growth from cubic to quadratic).
  

• 0f3d0a71
  by Zubin Duggal at 2026-06-12T14:55:30-04:00

  compiler: mark tool messages as errors/warnings depending on the exit code
  
  Fixes #27370
  

• d9ea2d76
  by mangoiv at 2026-06-13T04:41:51-04:00

  libraries/process: bump submodule to v1.6.30.0
  
  - bump the submodule to the appropriate tag
  - suppress benign warning resulting from the change
  

• 6ebaaba3
  by David Eichmann at 2026-06-13T04:42:37-04:00

  ghc-toolchain: don't throw when candidate executables are not found
  
  Fixes #27369
  

• 6c65e1e1
  by David Eichmann at 2026-06-13T04:43:23-04:00

  CI: lint-changelog checks for no-changelog label in script instead of rules
  

• bab37cc6
  by konsumlamm at 2026-06-13T19:10:21+02:00

  Implement CLC proposal #378
  
  Add `Data.Double` and `Data.Float` modules
  Document that GHC uses IEEE 754
  

• fb5246ad
  by fendor at 2026-06-15T18:07:23-04:00

  Drop `preloadClosure` from `UnitState`
  
  It is always hard-coded to the same value.
  
  Backpack Unit instantiation isn't using it any more.
  Allows us to simplify the API and get rid of `improveUnit`.
  

• 291ce3aa
  by ARATA Mizuki at 2026-06-15T18:08:26-04:00

  RISC-V NCG: Zero-extend the result of castFloatToWord32
  
  According to the ISA manual, FMV.X.W sign-extends the result.
  We need to truncate the result to avoid creating an exotic Word32 value.
  
  Fixes #27300
  

• 011be91f
  by ARATA Mizuki at 2026-06-15T18:08:26-04:00

  RISC-V NCG: Treat d28-d31 (ft8-ft11) as caller-saved
  
  According to the calling convention, the registers d28-d31 (ft8-ft11) are caller-saved.
  
  Fixes #27306
  

• e8a54713
  by ARATA Mizuki at 2026-06-15T18:08:26-04:00

  RISC-V NCG: Set rounding mode when emitting `truncate`
  
  If we omit the rounding mode for `fcvt`, `dyn` will be used.
  We do not want that for `truncate`, so we set `rtz`.
  In other places, we set `rne` because we do not use the dynamic rounding mode.
  
  Fixes #27303
  

• 9438bec7
  by Zubin Duggal at 2026-06-15T18:09:11-04:00

  rts: fix validate build with gcc 16. `__attribute__((regparm(1)))` is ignored on x86_64 and now
  gcc warns that it is ignored:
  
  rts/sm/Evac.h:35:1: error:
       error: ‘regparm’ attribute ignored [-Werror=attributes]
  
  See https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=ccead81bbc39668376eb5cf47066acb446cc43f3
  
  Fixes #27366
  

• 893e6133
  by Andrew Lelechenko at 2026-06-15T23:55:36+01:00

  base: more NonEmpty zips
  
  CLC proposal: https://github.com/haskell/core-libraries-committee/issues/409
  

• 1314f2fd
  by David Eichmann at 2026-06-16T05:46:52-04:00

  Hadrian: fix ghc-internal .def file name
  

• 7f72bcb3
  by mangoiv at 2026-06-16T05:47:39-04:00

  compiler: ignore camelCase and Eta reduce hlint hints
  
  These do not cohere with the style used in GHC. After disabling them,
  hlint lints are much less noisy again.
  

• 842bef9f
  by Alan Zimmerman at 2026-06-16T05:48:25-04:00

  EPA: Use standard type family declaration for Anno
  

• f6d30767
  by Wolfgang Jeltsch at 2026-06-16T15:32:34-04:00

  Fix two issues in the documentation of pipeline interruption
  
  One issue is a typo (“interreuptible”), the other one the lack of an end
  of a sentence, which has been reconstructed from the message of
  633bbc1fd4762a2bb73ba1c5b9e0c279f1dd3c40, the commit that introduced
  said documentation.
  

• a3fa10e0
  by Christian Georgii at 2026-06-16T15:33:26-04:00

  Find plugins in sibling home units in multiple-home-unit sessions
  
  In a multiple-home-unit session (e.g. `cabal repl --enable-multi-repl` or HLS), enabling a plugin with -fplugin that is defined in (or reexported by) another home unit failed with a "hidden package" error. The plugin module finder only searched the current home unit and the registered external packages, never the sibling home units.
  
  findPluginModuleNoHsc now searches the home units that the current home unit depends on, following module reexports and respecting hidden modules, exactly as ordinary import resolution does in findImportedModuleNoHsc. To avoid two divergent copies of this logic, the shared home-unit search (the current home unit first, then its dependencies in priority order, with the accompanying ordering invariant) is extracted into findHomeModuleAmongDeps, which both findImportedModuleNoHsc and findPluginModuleNoHsc now call.
  
  Add testsuite/tests/driver/multipleHomeUnits/plugin01, which loads a plugin as byte-code from a sibling home unit, and plugin02, in which the consumer enables a plugin reexported by a sibling home unit without depending on the plugin's own home unit directly.
  
  Fixes #27349
  

• d216412b
  by Ian-Woo Kim at 2026-06-16T20:25:57-04:00

  Make the order of usages deterministic
  
  It has been observed that the ordering of usages can be non-determinstic
  in parallel builds. Therefore, this contribution introduces sorting of
  usages based on a platform- and race-independent sorting criterion.
  
  Resolves #26877.
  
  Co-authored-by: Wolfgang Jeltsch <wolfgang@well-typed.com>
  

• 8e1cc105
  by Wolfgang Jeltsch at 2026-06-16T20:25:57-04:00

  Change the descriptions of two existing changelog entries
  
  The descriptions now describe the changes in a user-friendly manner, as
  opposed to describing the contributions that led to these changes in a
  developer-friendly manner.
  

• 636c1c7a
  by Ian Duncan at 2026-06-16T20:26:50-04:00

  AArch64: use SXTH, not SXTW, for W32 signExtendReg
  
  signExtendReg was using SXTH (sign-extend halfword, 16-bit) for
  W32-to-W64 sign extension. This should be SXTW (sign-extend word,
  32-bit). SXTH only sign-extends the lower 16 bits, producing wrong
  results for 32-bit values whose bit 15 differs from bit 31.
  
  Other fixes:
  
    - At sub-W64, code gen for MO_S_Mul2 should use W32 registers for
      SMULL source operands as per the ARM spec (SMULL Xd, Wn, Wm),
      and not W64.
  
    - Ensure signExtendReg uses the source width for the source operand
      in SXTW/SXTH/SXTB instructions. GNU as requires sxtw Xd,Wn (not
      sxtw Xd,Xn), while LLVM's integrated assembler on macOS is lenient.
  
    - Fix overflow flag computation for `MO_S_Mul2`. The overflow bit
      was exactly inverted for sub-W64 operands.
  
  Fixes #26978 and #27047
  

• b734c75d
  by Igor Ranieri at 2026-06-16T20:27:32-04:00

  haddock: Update CONTRIBUTING with missing step, add missing test
  dependency
  

• 7fe4f2ec
  by Luite Stegeman at 2026-06-17T05:35:09-04:00

  tag inference: don't confuse functions with their return values
  
  inferTagRhs was mixing up taggedness for closures and return values
  for function closures. We really shouldn't assign TagTuple to a
  properly tagged function returning a tuple.
  
  We fix this by keeping track of functions (TagFun) separately from
  values (TagVal) and keeping track of their return value. TagFun is
  also used for join points.
  
  fixes #27005
  

• 4671c126
  by Sebastian Graf at 2026-06-17T05:35:55-04:00

  Seed the simplifier's in-scope set for open expressions
  
  simplifyExpr simplifies expressions typed at the GHCi prompt and the
  results of Template Haskell splices. Such an expression may be open: at a
  GHCi debugger breakpoint its free variables include RuntimeUnk skolems
  standing for as-yet-unknown types.
  
  The simplifier began with an in-scope set holding only the wildcard
  binder, so when it instantiated the unsafeCoerce# wrapper that GHCi
  builds around a result, it formed a substitution whose range mentioned a
  free skolem that was not in scope. That breaks the substitution invariant
  and, in a compiler built with assertions, trips substTy's sanity check.
  
  Seed the initial in-scope set with the free variables of the expression.
  For a closed expression this adds nothing.
  
  See Note [Seed the in-scope set for open expressions].
  
  Fixes #17833 and its duplicate #21118.
  

• 67d41299
  by Sebastian Graf at 2026-06-18T05:18:24-04:00

  Desugar a `case` scrutinee only once (#27383, #20251)
  
  In `dsExpr` for `HsCase` we desugared the scrutinee /twice/: once to
  build the Core `case` itself, and again inside `matchWrapper`, which
  re-desugared the source scrutinee (via `addHsScrutTmCs`) purely to
  record long-distance information for the pattern-match checker.
  
  For a single `case` that is merely wasteful.  But for nested cases it
  is catastrophic.  Consider
  
      case (case (case e of ... ) of ... ) of ...
  
  Desugaring the outer scrutinee desugars the middle `case` twice, each
  of which desugars the inner `case` twice, and so on.  The work doubles
  at every level, so desugaring takes O(2^n) time in the nesting depth.
  That is the blowup reported in #27383; it is also what makes the
  machine-generated program in #20251 take an age to compile.
  
  The fix is simple.  `matchWrapper` is handed the scrutinee anyway, so
  we give it the Core expression we have /already/ desugared, and record
  the long-distance term constraint with `addCoreScrutTmCs` instead of
  re-desugaring from source.  This is just what `matchSinglePatVar`
  already does for single-pattern matches.
  
  So:
  
  * `matchWrapper` now takes `Maybe [CoreExpr]` rather than
    `Maybe [LHsExpr GhcTc]`.
  
  * The `HsCase` equation of `dsExpr` passes the already-desugared
    `core_discrim`; the arrow desugarer passes its match variables.
  
  * `addHsScrutTmCs` had no other use, so it is gone.
  
  Desugaring is now linear in the nesting depth.  (The coverage checker
  still runs `simpleOptExpr` over each scrutinee, which leaves the total
  at O(n^2); that is ample.)  The long-distance information itself is
  unchanged: the checker sees precisely the Core that backs the
  generated code.
  
  Test: deSugar/should_compile/T27383
  

• fa5defde
  by Rodrigo Mesquita at 2026-06-18T05:19:11-04:00

  fix: Save FastStrings in the PMC
  
  There is no point in adding the unique to the occurrence FastString we
  create, since it is part of the Id anyway.
  
  Adding it to the FastString, meant each FastString was unique
  unnecessarily!
  
  In a separate branch, running the compiler on test `InstanceMatching`
  observed 30000 `FastString`s created by this code path.
  
  Plus, `fsLit "pm"` follows the existing pattern in `mkPmId`.
  

• 4efb4a66
  by Alan Zimmerman at 2026-06-18T14:41:14-04:00

  TTG: Add extension points to HsConDetails
  
  Extend HsConDetails as
  
      data HsConDetails p arg rec
        = PrefixCon !(XPrefixCon p) [arg]    -- C @t1 @t2 p1 p2 p3
        | RecCon    !(XRecCon p)    rec      -- C { x = p1, y = p2 }
        | InfixCon  !(XInfixCon p)  arg arg  -- p1 `C` p2
        | XHsConDetails !(XXHsConDetails p)
  
      type family XPrefixCon      p
      type family XRecCon         p
      type family XInfixCon       p
      type family XXHsConDetails  p
  

• c8d27dd4
  by Simon Jakobi at 2026-06-18T14:41:59-04:00

  CI: quiet submodule clean output in after_script and setup
  
  The clean and cleanup_submodules functions ran 'git submodule foreach
  git clean -xdf', flooding the job log with 'Entering ...' and
  'Removing ...' lines. Pass --quiet to 'git submodule' and -q to 'git
  clean' to drop the success output; errors are still reported.
  
  Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
  

• 09326ca6
  by Matthew Pickering at 2026-06-20T23:41:12+02:00

  Add missing req_interp modifier to T18441fail3 and T18441fail19
  
  These tests require the interpreter but they were failing in a different
  way with the javascript backend because the interpreter was disabled and
  stderr is ignored by the test.
  

• 521e55bf
  by Matthew Pickering at 2026-06-20T23:41:13+02:00

  hadrian: Fill in more of the default.host toolchain file
  
  When you are building a cross compiler this file will be used to build
  stage1 and it's libraries, so we need enough information here to work
  accurately. There is still more work to be done (see for example, word
  size is still fixed).
  

• 23c9b6c3
  by Matthew Pickering at 2026-06-20T23:42:52+02:00

  hadrian: Build stage 2 cross compilers
  
  * Most of hadrian is abstracted over the stage in order to remove the
    assumption that the target of all stages is the same platform. This
    allows the RTS to be built for two different targets for example.
  * Abstracts the bindist creation logic to allow building either normal
    or cross bindists. Normal bindists use stage 1 libraries and a stage 2
    compiler. Cross bindists use stage 2 libararies and a stage 2
    compiler.
  * hadrian: Make binary-dist-dir the default build target. This allows us
    to have the logic in one place about which libraries/stages to build
    with cross compilers. Fixes #24192
  
  New hadrian target:
  
  * `binary-dist-dir-cross`: Build a cross compiler bindist (compiler =
    stage 1, libraries = stage 2)
  
  This commit also contains various changes to make stage2 compilers
  feasible.
  
  -------------------------
  Metric Decrease:
      LinkableUsage02
      ManyAlternatives
      ManyConstructors
      MultiComponentModulesRecomp
      MultiLayerModulesRecomp
      RecordUpdPerf
      T10421
      T12150
      T12227
      T12425
      T12707
      T13035
      T13379
      T13820
      T15703
      T16577
      T18140
      T18282
      T18698a
      T18698b
      T18923
      T1969
      T20049
      T21839c
      T3294
      T4801
      T5030
      T5321FD
      T5321Fun
      T5631
      T5642
      T6048
      T783
      T9020
      T9198
      T9233
      T9630
      T9872d
      T9961
      parsing001
      T3064
  
  Metric Increase:
      T26989
      hard_hole_fits
  -------------------------
  
  Co-authored-by: Sven Tennie <sven.tennie@gmail.com>
  

• 26fed8ab
  by Matthew Pickering at 2026-06-20T23:42:52+02:00

  ci: Test cross bindists
  
  We remove the special logic for testing in-tree cross
  compilers and instead test cross compiler bindists, like we do for all
  other platforms.
  

• 80c8910e
  by Matthew Pickering at 2026-06-20T23:42:52+02:00

  ci: Introduce CROSS_STAGE variable
  
  In preparation for building and testing stage3 bindists we introduce the
  CROSS_STAGE variable which is used by a CI job to determine what kind of
  bindist the CI job should produce.
  
  At the moment we are only using CROSS_STAGE=2 but in the future we will
  have some jobs which set CROSS_STAGE=3 to produce native bindists for a
  target, but produced by a cross compiler, which can be tested on by
  another CI job on the native platform.
  
  CROSS_STAGE=2: Build a normal cross compiler bindist
  CROSS_STAGE=3: Build a stage 3 bindist, one which is a native compiler and library for the target
  

• 8215573d
  by Sven Tennie at 2026-06-20T23:42:52+02:00

  ci: Increase timeout for emulators
  
  Test runs with emulators naturally take longer than on native machines.
  
  Generate jobs.yml
  

• 5acb7dbc
  by Matthew Pickering at 2026-06-20T23:42:52+02:00

  ci: Javascript don't set CROSS_EMULATOR
  
  There is no CROSS_EMULATOR needed to run javascript binaries, so we
  don't set the CROSS_EMULATOR to some dummy value.
  

• 48345343
  by Sven Tennie at 2026-06-20T23:42:52+02:00

  Javascript skip T23697
  
  See #22355 about how HSC2HS and the Javascript target don't play well
  together.
  

• 5e44fd05
  by Sven Tennie at 2026-06-20T23:42:52+02:00

  Mark T24602 as fragile
  
  It was skipped before (due to CROSS_EMULATOR being set, which changed
  for JS), so we don't make things worse by marking it as fragile.
  

• ab349ec2
  by Sven Tennie at 2026-06-20T23:42:52+02:00

  Fix T22744 for GHCJS
  
  In fact, this test needs Template Haskell, not necessarily an
  interpreter.
  

• c73352d8
  by Sven Tennie at 2026-06-20T23:42:52+02:00

  haddock-test: fix GHCJS haddock test failures
  
  Add --ghc-pkg-path flag support so haddock test runner can find
  cross-prefixed ghc-pkg (e.g. javascript-unknown-ghcjs-ghc-pkg) which
  is not on $PATH in cross install directories.
  
  Skip haddockHtmlTest on GHCJS: Threaded.hs uses forkOS in a TH splice,
  which GHCJS RTS doesn't support. Mark with js_skip in all.T.
  

• 5e814e76
  by Andreas Klebinger at 2026-06-22T23:00:24-04:00

  compiler: Deduplicate hscTidy
  
  This function was accidentally duplicated during a refactor.
  
  Fixes #27351
  

• 473b97eb
  by sheaf at 2026-06-22T23:01:22-04:00

  Avoid mkTick in Core Prep breaking ANF (part II)
  
  Hotfix for 2f9579765f55b3920ceb2e04995ff41a9d0e2d4e fixing a small
  oversight in the call to tickTickedExpr from mkTick, in which we
  improperly recursively called mkTick without passing on the preserve_anf
  flag.
  
  Fixes #27386
  

• 9284a1f7
  by Simon Hengel at 2026-06-23T05:55:33-04:00

  Don't use global variables to address concurrency bugs! (fixes #27234)
  
  This was originally introduce with
  88f38b03025386f0f1e8f5861eed67d80495168a to address #17922.
  
  In this specific case a better fix would have been to synchronize on
  stderr:
  
      withHandle_ "stderrSupportsAnsiColors" stderr $ \ _ -> do
        ...
  
  But apparently the dependency on `terminfo` was removed in
  32ab07bf3d6ce45e8ea5b55e8095174a6b42a7f0, preventing #17922 in the first
  place.
  

• 44309cd3
  by Alan Zimmerman at 2026-06-23T05:56:20-04:00

  EPA: remove LocatedL / SrcSpanAnnL and  LocatedLI / SrcSpanAnnLI
  
  This is part of a refactor towards only having LocatedA / SrcSpanAnnA
  
  It removes the stated items, but has to add back one for BooleanFormula,
  LocatedBF / SrcSpanAnnBF
  
  This commit also use the HsConDetails RecCon extension point to
  capture the braces in a record constructor
  

• 2f6a5534
  by Simon Jakobi at 2026-06-23T15:46:20+02:00

  Add -dstable-core-dump-order for stable Core dump ordering (#27296)
  
  The order of top-level bindings in Core dumps (-ddump-simpl etc.) is the
  compiler's Unique-sensitive internal processing order, so an unrelated
  upstream change can reorder them and defeat a textual diff of two dumps.
  
  This adds an opt-in flag -dstable-core-dump-order that reorders the
  top-level bindings of dumps routed through dumpPassResult into a stable,
  Unique-independent order, so two dumps line up across rebuilds. See
  Note [Stable Core dump order] in GHC.Core.Ppr for the sort key and its
  rationale.
  
  Adds tests T27296 (binders GHC emits in non-source order by default,
  asserted to come out stably ordered under the flag) and T27296b (an
  untidied -ddump-float-out dump pinning the ordering of the anonymous lvl
  floats by literal value).
  
  Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
  

• 141986e3
  by mangoiv at 2026-06-24T15:51:14-04:00

  compiler: refactor error reporting code for ExplicitLevelImports
  
  Refactors error reporting code for ExplicitLevelImports to pass in a
  RdrName and a GlobalReaderElt to be able to report errors that are
  faithful to the source and to more precisely distinguish between names
  that are in scope from different qualifications.
  
  Fixes #27385 and #26616
  

• aa7df6b6
  by Simon Hengel at 2026-06-24T15:52:18-04:00

  Set GHC_VERSION when calling custom pre-processors (see #25952)
  
  (so that pre-processors can emit backwards compatible code)
  

• a9e494f2
  by Simon Hengel at 2026-06-24T15:54:08-04:00

  Add a flag to control GHCi specific error hints (close #27409)
  

• a805b2a2
  by Simon Hengel at 2026-06-24T15:55:20-04:00

  Reference correct package in error messages for reexported modules
  
  (fixes #27417)
  

• f235d183
  by Simon Jakobi at 2026-06-25T05:51:18-04:00

  Add explicit setBit/clearBit/complementBit for instance Bits Integer (#21176)
  
  The default setBit, clearBit, and complementBit methods allocate
  intermediate Integers per call. Define them explicitly via the new
  integerSetBit[#], integerClearBit[#] and integerComplementBit[#], built
  on the BigNat# primitives, which avoid those allocations. Allocation is not
  eliminated entirely -- the negative (IN) cases would need in-place mutation,
  which is left as future work.
  
  The default methods constant-folded on literal arguments via the
  integerOr/integerAnd/integerXor rules, which fold literal Integers of any
  size. The explicit functions have no such rule, so they (their Word-argument
  wrappers, and the Bits Integer methods) are marked INLINE to expose the
  underlying primops to the simplifier; see Note [INLINE for constant folding
  of bit operations]. This restores folding only on the small-int (IS) path --
  large literal Integers (IP/IN) are no longer constant-folded, a minor
  regression for that case. T8832 covers the IS-path folding.
  
  The new golden-output test T21176 checks all three operations against the
  default implementations across the sign/size boundaries, recording each
  result plus its integerCheck validity. The base and ghc-bignum interface-
  stability export goldens gain the new functions.
  
  The main changelog entry lives in changelog.d under a new ghc-internal
  section (renamed from ghc-prim).
  
  CLC proposal: https://github.com/haskell/core-libraries-committee/issues/423
  
  Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
  

• 202ed264
  by Marc Scholten at 2026-06-25T05:52:21-04:00

  haddock: use Text in documentation pipeline
  
  This patch moves Haddock's documentation pipeline from String to Text
  where the data is already textual. It avoids repeated conversions while
  keeping the existing decoding behavior for invalid UTF-8 docstring
  chunks.
  
  The main changes are:
  
  * Render and carry docstrings as Text in Haddock-facing paths.
  * Use the Binary Text instance from GHC.Utils.Binary for Haddock
    interface files, and bump the Haddock binary interface version.
  * Add a FastString HTML instance so XHTML rendering avoids
    intermediate String allocation.
  * Keep HsDocStringChunk decoding lenient, matching the previous
    unpackHDSC behavior on invalid UTF-8 input.
  * Update the xhtml submodule to 3000.4.1.0, which contains the
    apostrophe escaping fix used by the Haddock test output.
  
  Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
  Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
  Assisted-by: Codex <codex@openai.com>
  

• a72ff58f
  by mangoiv at 2026-06-25T05:53:07-04:00

  compiler: rename ZonkAny to UnusedType and add pretty printing logic
  
  ZonkAny is a hard to understand name for users who do not know how the
  compiler works internally. Additionally, it is confusing that ZonkAny,
  while being a concrete type *represents* a meta variable, espeically in
  the compiler output.
  This patch changes the name of ZonkAny to UnusedType which is closer to
  its intended semantics and adds special pretty printing logic to display
  this type in the same fashion the compiler displays meta variables in
  other places, whenever they leak from the implementation to the user.
  It also exports the type from ghc-internal:GHC.Internal.Types in order
  to expose documentation.
  
  Fixes #27390
  
  Co-Authored-By: Sam Derbyshire <sam.derbyshire@gmail.com>
  

• 6813f002
  by Simon Jakobi at 2026-06-26T04:51:47-04:00

  Reg.Linear: drop Platform argument from most FR (FreeRegs) methods
  
  The FR class has one instance per CPU architecture, so any
  architecture-constant information its methods derived from the Platform
  argument can instead be baked into the instance. This removes the now
  needless Platform argument from frAllocateReg, frGetFreeRegs and
  frReleaseReg.
  
  frInitFreeRegs keeps its Platform argument: the initial allocatable set is
  genuinely platform-dependent, see Note [Aarch64 Register x18 at Darwin and
  Windows].
  
  Fixes #26665
  
  Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
  

• 3b2a9409
  by Zubin Duggal at 2026-06-26T04:52:39-04:00

  testsuite: Report fragile failures as skipped in JUnit output
  

• 27463426
  by Rodrigo Mesquita at 2026-06-26T20:54:58-04:00

  perf: Share Module in Iface Symbol Table
  
  This commit modifies the structure of the serialized `SymbolTable Name`
  to then re-use and share the `Module` (both on disk and in memory) across
  all `Name`s from the same module.
  
  The new structure looks like:
  
    <total name count>
    $modules.size
    for (mod, names) in $modules:
      $mod
      $names.size
      for table_ix, occ in $names
        $table_ix
        $occ
  
  i.e. we put the module just once, followed by all names in that module.
  When deserializing, we deserialize the module just once, and all the
  following `Name`s are constructed with a pointer to that same decoded
  `Module`.
  
  In `hoogle-test`, we must use `DNameEnv` rather than `Map Name`,
  otherwise the output fixities order was susceptible to changes in the
  uniques assigned to each Names, which is not stable.
  
  Fixes #27401
  
  -------------------------
  Metric Decrease:
      InstanceMatching
      LinkableUsage01
      LinkableUsage02
      hard_hole_fits
  -------------------------
  

• 412f1675
  by Simon Hengel at 2026-06-26T20:55:41-04:00

  Rename `MCDiagnostic` to `InternalMCDiagnostic`
  
  `MCDiagnostic` is meant to be used for compiler diagnostics.
  
  Any code that creates `MCDiagnostic` directly, without going through
  `GHC.Driver.Errors.printMessage`, sidesteps `-fdiagnostics-as-json` (see
  e.g. !14616, !14475, !14492 !14548).
  
  To avoid this in the future, this change more narrowly controls who
  creates `MCDiagnostic` (see #24113).
  

• 6f212121
  by Facundo Domínguez at 2026-06-26T20:56:27-04:00

  Encapsulate options of occurAnalysePgm in a record
  

• adfbb179
  by Facundo Domínguez at 2026-06-26T20:56:27-04:00

  Allow to configure the occurrence analyser to retain some dead bindings
  
  This is needed by plugins that are the only consumers of a binding which
  is otherwise unused in the program.
  
  See Note [Controlling elimination of dead bindings in occurrence analysis]
  added in this commit, or
  https://gitlab.haskell.org/ghc/ghc/-/issues/27240 for more discussion.
  

• c745b11f
  by Copilot at 2026-06-26T20:56:27-04:00

  Address documentation feedback
  

• 2c2a4a2a
  by Copilot at 2026-06-26T20:56:27-04:00

  Keep the imp_rules parameter of occurPgmAnalysePgm and add occ_opts to OccEnv
  

• e2262b0e
  by Copilot at 2026-06-26T20:56:27-04:00

  Strengthen T27240.hs with a binding that should be removed
  

• 5f9d9268
  by Copilot at 2026-06-26T20:56:27-04:00

  Move the reference #27240 to a related paragraph
  

• d86d2644
  by Simon Hengel at 2026-06-26T20:57:10-04:00

  Remove deprecated flag `-ddump-json` (see #24113)
  
  This was first deprecated in 9.10.1.
  

• 3b15ff03
  by Simon Jakobi at 2026-06-27T18:48:34+02:00

  Tweak mk_mod_usage_info
  
  * Use O(log n) `elemModuleEnv` instead of O(n) `elem` to filter the
    direct imports.
  * Use `nonDetModuleEnvKeys` to avoid sorting the ent_map keys twice.
  * Prepend the presumably shorter list when creating all_mods with
    `(++)`. Actually this eliminates the `(++)` entirely, as it seems to
    fuse with the `filter` expression.
  
  As a result there is a tiny speed-up when generating the .hi-files for
  modules with many imports.
  
  None of the changes affect compilation determinism as the module list
  is explicitly sorted to ensure a canonical order.
  

• 2d0fd154
  by Alan Zimmerman at 2026-06-29T11:44:00-04:00

  EPA: Remove LocatedC / SrcSpanAnnC
  
  This is part of a cleanup of the zoo of
  SrcSpanAnnXXX types for exact print annotations.
  
  This one removes SrcSpanAnnC used for storing exact print annotations
  for contexts. It replaces it with an explicit `HsContext` data type
  that carries the annotations and the context.
  
  So, replace
  
    type HsContext pass = [LHsType pass]
  
  with
  
    type HsContext pass = HsContextDetails pass (LHsType pass)
  
    data HsContextDetails pass arg
      = HsContext
        { hsc_ext  :: !(XHsContext pass)
        , hsc_ctxt :: [arg]
        }
      | XHsContextDetails !(XXHsContextDetails pass)
  
  We need the parameterised HsContextDetails because it is used both for
  HsQual carrying 'LHsExpr p' and "normal" contexts carrying 'LHsType p'.
  

• cca0d589
  by Luite Stegeman at 2026-06-30T13:33:40-04:00

  rts: handle large AP closures in compacting GC
  
  The function update_fwd_large in the compacting GC could run into
  an unexpected object with the following error:
  
    internal error: update_fwd_large: unknown/strange object  24
  
  Closure type 24 is the AP closure, which was not handled in
  upd_fwd_large. This patch adds handling them.
  
  fixes #27434
  

• 42935858
  by Luite Stegeman at 2026-06-30T13:33:40-04:00

  testsuite: use compacting_gc way instead of hardcoding +RTS -c
  

• bf7b5ce6
  by Alan Zimmerman at 2026-06-30T13:34:23-04:00

  EPA: Remove LocatedLW from LStmtLR
  
  HsDo already had its XDo extension point for an
  AnnList, which also appeared in LocatedLW.
  So we remove the redundant one and use the one inside HsDo
  as originally intended.
  
  Also delete LocatedLC/LocatedLS as they were unused
  

• d7cfea49
  by Recursion Ninja at 2026-06-30T21:37:12-04:00

  Decoupling 'L.H.S' from 'GHC.Types.SourceText'
  
    * Migrated 'IntegralLit'   to 'L.H.S.Lit'.
    * Migrated 'FractionalLit' to 'L.H.S.Lit'.
    * Migrated 'StringLiteral' to 'L.H.S.Lit'.
    * Added TTG extension points to the types above.
    * Added nice export list to 'GHC.Hs.Lit'.
    * Added 'rnOverLitVal' and 'tcOverLitVal' functions to 'GHC.Hs.Lit'.
    * Added instance 'Anno (StringLiteral (GhcPass p)) = SrcSpanAnnN'
    * Moved [Notes] about 'SourceText' from 'L.H.S.*' to 'GHC.*'.
    * Removed all references to 'SourceText' from 'L.H.S'.
    * Removed the trailing comma record field from  'StringLiteral'
    * Renamed exported functions for nomenclature consistency.
    * Deprecated the renamed functions
  
  Fixes #26953
  

• a1f2558b
  by Recursion Ninja at 2026-06-30T21:37:12-04:00

  Monomorphising GHC pass parameters where appropriate
  

• 7bf9e3c5
  by Teo Camarasu at 2026-06-30T21:38:03-04:00

  Make Q abstract
  
  This patch aims to clearly demarcate the internal and external interfaces
  of Q.
  In the past the `Quasi` typeclass was both part of the external,
  public-facing interface, and was used to give the implementation of `Q`.
  
  Now we separate out these two distinct roles. `Quasi` continues to exist
  in the public interface, but we introduce a new `MetaHandlers` type,
  which is equivalent to `Dict Quasi`.
  
  `Q a` is now defined to be `MetaHandlers -> IO a`, and, crucially,
  the constructor and the new `MetaHandlers` type are not exposed from the
  public interface.
  
  This gives us the ability to vary the interface on the GHC side without
  forcing a breaking change on the `template-haskell` side.
  Similarly `template-haskell` has more freedom to change the `Quasi`
  typeclass without needing any changes in `lib:ghc`.
  
  Implements https://github.com/ghc-proposals/ghc-proposals/pull/700
  
  Resolves #27341
  

• 4262af36
  by L0neGamer at 2026-06-30T21:38:56-04:00

  generically defines mconcat in terms of internal type's Semigroup instance
  
  add changelog entry
  
  use simpler definition for mconcat
  
  `nonEmpty` isn't available yet; inline branches in case
  
  add test case
  
  fixup generically defines mconcat in terms of internal type's Semigroup instance
  
  add comment on Generically and deriving mishaps
  
  swap mconcat to foldr version
  
  add some strictness testing for mconcat
  
  add to `base` changelog entry
  

• e22ad997
  by Cheng Shao at 2026-06-30T21:39:43-04:00

  hadrian/rts: fix unregisterised build for gcc 15+
  
  This patch fixes unregisterised build for gcc 15+:
  
  - Pass -optc-Wno-error in hadrian when +werror enables -optc-Werror,
    see added comment for details.
  - For RTS functions that the codegen would emit calls, ensure their
    real prototype is hidden when the header is included in .hc fies
    (IN_STG_CODE), and the dummy prototype is provided to match the EFF_
    convention.
  
  In the future we should get rid of EFF_ (#14647) and remove these
  hacks, but for now this patch makes unregisterised work again on newer
  toolchains. Fixes #27404.
  
  Co-authored-by: Codex <codex@openai.com>
  

• 3f00f234
  by Cheng Shao at 2026-06-30T21:40:32-04:00

  compiler: fix missing handling of CmmUnsafeForeignCall node in LayoutStack
  
  This patch fixes missing handling of `CmmUnsafeForeignCall` middle
  node in the `LayoutStack` pass.
  
  Before proc-points splitting, this pass computes liveliness of local
  registers, and spills those alive across a Cmm native call onto the
  stack. It need to traverse all middle nodes in each block and check
  whether a local register is an assignee, if so then the previous
  mapping in `sm_regs` is invalidated and needs to be dropped. However,
  it didn't handle `CmmUnsafeForeignCall` node which may also assign to
  a local register. When proc-points splitting is enabled, this can
  produce an invalid basic block that doesn't properly backup the
  updated local register to the stack before doing a Cmm call, resulting
  in completely invalid runtime behavior.
  
  The patch also adds a `T27447` regression test. With no-TNTC or with
  LLVM backend, without the fix the test case would output a stale
  0x1111111111111111 value, instead of the expected 0x2222222222222222
  output.
  
  Fixes #27447.
  
  Co-authored-by: Codex <codex@openai.com>
  

• 701088db
  by Ben Gamari at 2026-07-01T10:34:03-04:00

  gitlab-ci: Drop vestigial references to make build system
  

• 62d54a53
  by Ben Gamari at 2026-07-01T10:34:03-04:00

  gitlab-ci: Add support for running specifying a job's testsuite ways
  

• 7f97ac2c
  by Ben Gamari at 2026-07-01T10:34:03-04:00

  gitlab-ci: Run llvm testsuite ways in llvm jobs
  
  Addresses #25762.
  

• 7ea75116
  by ARATA Mizuki at 2026-07-01T10:34:03-04:00

  testsuite: Add normalise_ddump_deriv setup function
  
  Some tests check the result of -ddump-deriv, which may contain INLINE pragmas depending on optimization flags.
  With normalise_ddump_deriv setup function, INLINE pragmas are stripped off.
  

• c7a8199f
  by ARATA Mizuki at 2026-07-01T10:34:03-04:00

  testsuite: Use -dsuppress-idinfo to make tests more robust
  
  Previously, T18052a and T21755 were failing on 'optasm' and 'optllvm' ways because of visibility of unfoldings.
  

• a12122e5
  by ARATA Mizuki at 2026-07-01T10:34:03-04:00

  testsuite: Use a trick to keep large objects alive
  
  Previously, T17574 and T19381 were failing on 'optasm' and 'optllvm' ways because of compiler optimizations.
  Change them to use NOINLINE to prevent unwanted optimizations.
  

• 1a95b327
  by ARATA Mizuki at 2026-07-01T10:34:03-04:00

  testsuite: Only run T24224 in 'normal' way
  
  This test is a frontend-only one and breaks if optimizations are enabled.
  

• 8abea737
  by ARATA Mizuki at 2026-07-01T10:34:03-04:00

  testsuite: Ignore T18118's stderr
  
  When optimizations are enabled, the compiler emits a warning (You cannot SPECIALISE ...).
  The message is not important, so ignore it.
  

• 9453a722
  by ARATA Mizuki at 2026-07-01T10:34:03-04:00

  testsuite: Mark T816 and tc216 broken with optimizations
  
  These tests are about type checking, so we should not care too much if they are broken with optimizations.
  
  See #26952
  

• 0aef9ec0
  by Ben Gamari at 2026-07-01T10:34:03-04:00

  testsuite: ds014 is not longer broken
  
  It now appears to pass in the ways it was marked as broken in.
  
  Closes #14901.
  

• 4692d1e4
  by Ben Gamari at 2026-07-01T10:34:03-04:00

  testsuite: Only run stack cloning tests in the normal way
  
  These are too dependent upon code generation specifics to pass in most
  other ways.
  

• c154df26
  by ARATA Mizuki at 2026-07-01T10:34:03-04:00

  testsuite: Update options_ghc_fbyte-code
  
  The `-fbyte-code` option used to be overriden by `-fllvm` but it is no longer true since !14872 was merged.
  
  I updated the test to accept the new behavior.
  
  Closes #27049
  

• 5d8bb7b5
  by ARATA Mizuki at 2026-07-01T10:34:03-04:00

  testsuite: Only run T22744 in 'normal' way
  
  This test takes a long time on optimized ways.
  

• d1e74c8e
  by ARATA Mizuki at 2026-07-01T10:34:03-04:00

  testsuite: Disable tests that use -finfo-table-map on llvm ways
  
  Currently, -finfo-table-map does not work with -fllvm. See #26435
  

• 3bf38c84
  by ARATA Mizuki at 2026-07-01T10:34:03-04:00

  testsuite: Don't run T24726 on optimized ways
  
  If optimizations are enabled, the rewrite rule just fires and -drule-check will report nothing.
  

• e4eef116
  by ARATA Mizuki at 2026-07-01T10:34:03-04:00

  testsuite: Use -fno-unoptimized-core-for-interpreter when running LinkableUsage01/02
  
  Optimizations for the bytecode interpreter are considered experimental, and need a flag to be enabled.
  

• 234a9872
  by ARATA Mizuki at 2026-07-01T10:34:03-04:00

  testsuite: Suppress unwanted optimizations on T25284
  

• 99a2af2f
  by ARATA Mizuki at 2026-07-01T10:34:03-04:00

  testsuite: Don't run stack_big_ret with optimizations
  
  Stack layout may change with optimizations enabled.
  

• 04c836df
  by ARATA Mizuki at 2026-07-01T10:34:04-04:00

  testsuite: Mark memo001 broken on optimized ways
  
  See #27396
  

• 1a8a24f4
  by ARATA Mizuki at 2026-07-01T10:34:04-04:00

  testsuite: Mark syn-perf broken on optimized ways
  
  See #27398
  

• 40412093
  by Duncan Coutts at 2026-07-01T10:34:50-04:00

  Add a test for thread scheduler fairness
  
  It also tests that the interval timer and context switching works.
  We also test that fairness is lost when the context switching interval
  is too coarse for the duration of the test.
  
  We add this test before doing surgery on the interval timer, so we have
  decent coverage.
  

• 3f34d557
  by Duncan Coutts at 2026-07-01T10:34:50-04:00

  Make exported stop/startTimer no-ops, and rename internal functions
  
  Specifically, internally rename:
  stop/startTimer to pause/unpauseTimer
  stop/startTicker to pause/unpauseTicker
  
  and keep stop/startTimer as exported functions, but now as no-ops.
  
  In the past the stop/startTicker actions were used incorrectly as if
  they were synchronous, which they are not. See issue #27105. We now
  document pause/unpackTicker as being async and not to be used for the
  purpose of concurrency safety.
  
  The existing stop/startTimer (note Timer not Ticker, the Timer calls the
  Ticker!) are also exported from the RTS as a public API. This was
  historically because the ticker used signals and it was important to
  suspend the timer signel over a process fork. So these functions were
  exported to be used by the process and unix libraries.
  
  We cannot just remove the RTS exports, but we now make them no-ops, and
  they can be removed from the process and unix library later. This
  was already documented in a changelog.d entry no-more-timer-signal but
  due to changes during the MR process the change to make stop/startTicker
  into no-ops didn't make it into the earlier MR.
  

• 02e84e5f
  by Duncan Coutts at 2026-07-01T10:34:51-04:00

  Make exitTicker/exitTimer unconditionally synchronous
  
  We never use them asynchronously, and we should never need to do so.
  
  And update some related comments.
  

• 13db6a72
  by Duncan Coutts at 2026-07-01T10:34:51-04:00

  posix ticker: update and improve comments on (un)pause and exit
  
  Clarify what is async vs sync.
  

• 43d9a07d
  by Duncan Coutts at 2026-07-01T10:34:51-04:00

  posix ticker: split out ppoll/select helper functions
  
  Move the #ifdefs out of the main code body by introducing local helper
  functions and types, which themselves have two implementations (with a
  common API) based on ppoll or select.
  
  This helps improve clarity/readability.
  

• a5491baa
  by Duncan Coutts at 2026-07-01T10:34:51-04:00

  posix ticker: improve the implementation
  
  The existing implementation supported pausing and exiting, with the
  implementation of pausing reling on a mutex and condition variable.
  It needed to check the pause and stop shared variables on every
  iteration. It relies on ppoll or select, to wait on the timeout and also
  wait on an interrupt fd. The interrupt fd was only used for prompt
  exit/shutdown, and not for pausing or other notification. The pause only
  needed a lock and a memory operation, but the pause was not prompt. The
  resume used a lock, and signaling a cond var.
  
  The new implementation uses a somewhat more regular design: every
  notification is done by setting a shared variable and
  interrupting/notifying the ticker via the fd. The ticker thread does not
  need to check any shared variables on normal timer expiry, only when it
  recevies notification. This may be a micro-optimisation, but the tick
  occurs 100 times a second by default so any improvements in the hot path
  are amplified. When the ticker thread does receive notification it can
  check the various shared variables and update its local state. The
  blocking relies on using ppoll/select but without a timeout. This avoids
  the condition var and also allows further notifications when paused
  (also used for unpausing).
  
  This design can be extended with further notification types if needed by
  using and checking further shared vars (or making existing shared vars
  an enum or counter). This may be used in future for additional
  notifications to the ticker thread. This will likely be used to proxy
  wakeUpRts from a single handler context for example. And this approach,
  avoiding mutexes, is compatible with use from signal handlers.
  
  So overall, it's:
   * slightly simpler / more regular;
   * easier to extend with additional notifications;
   * probably slightly more efficient (but a micro-optimisation);
   * and supports calling notification from signal handlers
  

• 5b20821e
  by Duncan Coutts at 2026-07-01T10:34:51-04:00

  posix ticker: further minor local renaming for code clarity
  
  Improve the clarity with better choice of names for several local vars
  and function.
  

• 1f3ec5e0
  by Duncan Coutts at 2026-07-01T10:34:51-04:00

  win32 ticker: split out local helper functions
  

• 596e7307
  by Duncan Coutts at 2026-07-01T10:34:51-04:00

  win32 ticker: provide guarantee about concurrency and idempotency
  
  Use a lock to ensure pause/unpause can be used concurrently. Use a
  paused variable, protected by the lock, to ensure that pause and unpause
  are both idempotent. This is what the portable API expects.
  

• 1870edd7
  by Duncan Coutts at 2026-07-01T10:34:51-04:00

  win32 ticker: make the initial tick be after one wait interval
  
  There is no need to tick immediately. This is consistent with the
  posix implementation.
  

• 7c15ab5b
  by Duncan Coutts at 2026-07-01T10:34:51-04:00

  ticker: remove now-unnecessary layer of enable/disable
  
  There was an atomic variable used to block *part* of the actions of the
  tick handler. This still did not make stopTimer synchronous, even for
  the part of the the handle_tick actions it covered. It also added a more
  expensive (sequentuially consistent) atomic operation in the hot path
  for the handle_tick action, whereas our new design requires no atomic
  ops at all.
  
  Now that we have eliminate the need for synchronous stop/startTicker,
  we don't need this not-quite-working-anyway atomic protocol. The new
  pause/unpauseTicker is explicitly asynchronous and idempotent.
  

• 8585f8cb
  by Duncan Coutts at 2026-07-01T10:34:51-04:00

  ticker: add TODOs about issue #27250: too much being done from handle_tick
  
  The handle_tick should not perform I/O, block, perform long-running
  operations or call arbitrary user code. Unfortunately, everything to
  do with the eventlog (at the moment) falls into all those categories.
  

• 6e381626
  by Duncan Coutts at 2026-07-01T22:29:55+01:00

  Adjust releaseCapability_ precondition to allow cap->running_task == NULL
  
  There are two use cases for releaseCapability_:
  
  1. The current Task (cap->running_task) releases the Capability.
     The Capability is marked free, and if there is any work to do,
     an appropriate Task is woken up.
  
  2. There is no current task (cap->task == NULL), and thus the
     Capability is idle, and we want to wake up an idle Task to animate
     the Capability. This case uses always_wakeup.
  
  Currently, the precondition for releaseCapability_ is
    cap->running_task != NULL
  and so the 2nd use cases have to set cap->running_task (which is then
  immediately overwritten) just to satisfy the precondition. See the
  use cases in sendMessage and prodCapability.
  
  So we can relax the precondition to be:
    cap->running_task != NULL || always_wakeup
  so that in the always_wakeup case, we say it is ok for the
  cap->running_task to be NULL.
  
  This lets us simplify sendMessage and prodCapability. In particular it
  will allow prodCapability to not need a Task parameter.
  
  The ulterior motive for all this is that I want to be able to call
  prodCapability from an OS thread that is not itself a Task, in persuit
  of issue #27086: disentangle I/O managers from wakeUpRts. The most
  straightforward way to wake the RTS is using prodCapability, but the
  context in which we will need to do that are threads that are not Tasks.
  

• 89404ebc
  by Duncan Coutts at 2026-07-01T22:29:55+01:00

  prodCapability no longer needs to take a Task param
  
  Now that releaseCapability_ can accept cap->running_task == NULL then it
  is no longer necessary for prodCapability to require a Task.
  

• 4e60c5f6
  by Duncan Coutts at 2026-07-01T22:29:56+01:00

  Define prodOneCapability
  
  There was an existing declaration for this in the header file, but no
  definition.
  
  Similarly, there is a declaration for prodAllCapabilities but no
  definition, and we don't need it, so remove the declaration.
  

• 2527026f
  by Duncan Coutts at 2026-07-01T22:29:56+01:00

  Add a wakeUpRtsViaTicker feature to the posix ticker
  
  It proxies a call to wakeUpRts, but crucially, this can be called from
  a signal handler context. It will be used for ctl-c handling.
  

• aa5a03a5
  by Duncan Coutts at 2026-07-01T22:29:56+01:00

  Change how wakeUpRts works
  
  Previously it would call wakeupIOManager to get a capability to wake up
  and run. This works but it entangles the I/O managers with unrelated
  features: ctl-c handling and idle gc (the two features that use wakeUpRts).
  
  The reason it used wakeupIOManager is that this action is safe to use
  from a posix signal handler, since it just posts bytes to a pipe.
  Otherwise the more direct approach (used e.g. by sendMessage when the
  target capability is idle) is to use releaseCapability. But that uses
  condition variables and mutexes, which are not safe to use from within a
  signal handler.
  
  So instead of entangling the (multiple) I/O managers with this, we make
  wakeUpRts use the direct approach (using prodOneCapability). On win32
  the ctl-c console handler can call wakeUpRts directly, since it is
  called in a proper thread. On posix, to deal with the signal handler
  problem, we make the signal handler ask the ticker thread to proxy the
  call to wakeUpRts, since the ticker thread is also a proper thread.
  
  This will allow the I/O managers to no longer be concerned with this.
  This is good because there are many I/O managers (and they're
  complicated), but there is (on posix) only one ticker implementation. So
  this is an overall reduction in coupling and complexity.
  
  Fixes issue #27086
  

• c6d53c16
  by sheaf at 2026-07-02T21:35:44-04:00

  Test driver: normalise line numbers into libraries
  
  When comparing the stdout of tests that print out callstacks, we can't
  rely on the stability of exact line:column spans pointing into libraries
  (e.g. ghc-internal), as any change (such as adding a comment) can change
  them.
  
  This commit addresses this by normalising away line:column in callstacks,
  but only when those point into internal libraries. We don't do this in
  general, as the exact span might be important to the test (e.g. for a
  span within the test module itself).
  
  Fixes #27387
  

• 81ee62e0
  by Alan Zimmerman at 2026-07-02T21:36:33-04:00

  EPA: Remove LocatedLW from MatchGroup
  
  This is the last usage of LocatedLW / SrcSpanAnnLW
  

• 925959db
  by Recursion Ninja at 2026-07-04T04:14:12-04:00

  Decoupling 'L.H.S' from 'GHC.Hs.Doc'
  
    * Migrated 'GHC.Hs.Doc' and 'GHC.Hs.DocString' AST defintions from 'GHC.*' namespace,
      to new 'Language.Haskell.Syntax.Doc' module in the 'L.H.S' "namespace."
    * Updated 'HsDocString to be TTG-parameterised as 'HsDocString pass'.
    * Added 'GHC.Hs.Extension.Pass': splits 'GhcPass'/'Pass' and all 'HsDocString'
      TTG instances out of 'GHC.Hs.Extension', which re-exports it unchanged
      (this is backwards compatible and prevents the introduction of a boot file).
    * Deleted 'GHC.Hs.Doc.hs-boot'; removed all 'L.H.S.*' imports of 'GHC.Hs.Doc'.
    * Updated 'GHC.Hs.DocString' to be TTG pass-parameterised throughout; moved
      'mkHsDocStringChunk'/'unpackHDSC' here (require 'GHC.Utils.Encoding').
    * Split 'GHC.Rename.Doc.rnHsDoc' from 'rnHsDocIdentifiersOnly'.
    * Updated parser, renamer, typechecker, HIE, and exact-print for new types.
    * Added 'HsDocString' TTG instances for 'DocNameI' to 'Haddock.Types'.
    * Killed the last module loop between GHC.* and LHS.*.
          - Only edges from LHS.* to GHC.Data.FastString now!
  
  Resolves #26971
  

• b7e24044
  by mangoiv at 2026-07-04T04:14:56-04:00

  ci: retry fetching test metrics
  
  Retry fetching test metrics to make the CI not fail if the services is
  temporarily unavailable
  

• 4180af3f
  by Zubin Duggal at 2026-07-04T04:15:38-04:00

  Bump semaphore-compat submodule to 2.0.1
  
  This versions includes some cruicial fixes for darwin
  

• 242d4317
  by sheaf at 2026-07-04T04:16:19-04:00

  Remove outdated comment in GHC.Data.ShortText
  
  There was a long comment in GHC.Data.ShortText about a workaround that
  was necessary when bootstrapping with GHC 9.2 and below. The actual
  logic has since been dropped, but the comment remained. This commit
  removes the vestigial comment.
  

• 9b714c4c
  by Zubin Duggal at 2026-07-05T09:40:36+05:30

  CorePrep: Don't speculatively evaluate bindings that we have already discovered to be absent
  
  In #25924, we segfault because speculation forces a projection out of a RUBBISH dictionary
  (which we generated because it absent).
  
  Solution: Don't speculate on bindings we already know are absent.
  
  Fixes 25924
  

• 4a59b3ee
  by Zubin Duggal at 2026-07-05T09:40:36+05:30

  Don't make absent fillers for terminating types
  
  In #25924 we discovered that we could speculatively evaluate an absent filler
  for a dictionary, and project a field (a superclass selector) out of it,
  resulting in segfaults.
  
  Solution: Never make an absent filler or rubbish literal for a terminating type
  like a dictionary. mkAbsentFiller returns Nothing for isTerminatingType, so
  worker/wrapper and the specialiser keep the real argument instead.
  
  Some small metric decreases because we do a little less work in the
  simplifier now.
  
  Metric Decrease:
      T9872a
      T9872b
      T9872c
      TcPlugin_RewritePerf
  

• 383ddcd4
  by Alan Zimmerman at 2026-07-06T07:08:16-04:00

  EPA: Move the 'where' annotation for PatSynBind
  
  This allows us to move it out of the MatchGroup exact print annotation
  too
  

• 66d1a5d5
  by fendor at 2026-07-07T16:57:56-04:00

  Add 'backendInfoTableMapValidity' backend predicate
  
  Check whether the backend supports the `-finfo-table-map` flag and
  ignore it otherwise.
  
  Improve by-design documentation of `backendCodeOutput`.
  
  `Backend` is **abstract by design**. Make this clearer in
  `backendCodeOutput` which is incorrectly being used as a proxy for
  `Backend`.
  
  Instead, define the desired property predicates in GHC.Driver.Backend
  In the process, make `backendCodeOutput` total.
  

• 74f1071d
  by fendor at 2026-07-07T16:57:56-04:00

  Add failing test for `-finfo-table-map` and bytecode backend
  
  If you compile a module using the bytecode backend, with
  -finfo-table-map, then the info table map doesn't get populated for the
  module.
  
  This is because the -finfo-table-map code path is implemented mostly in
  the StgToCmm phase which isn't run when creating bytecode.
  
  Ticket #27039
  

• 28d63bca
  by mangoiv at 2026-07-07T16:59:16-04:00

  ci: don't fail nightly if there have been no changes that night
  
  Fixes #27127
  

• 4ebfc478
  by Rodrigo Mesquita at 2026-07-08T04:47:53-04:00

  ttg: Using ShortText over FastString in the AST
  
  To make the AST independent of GHC, this commit replaces usages of
  `FastString` with `HText` in the AST, killing the last edge from
  Language.Haskell.* to GHC.* modules.
  
  Even though we /do/ want to use FastStrings in general -- critically in
  Names or Ids -- there is no particular reason for the FastStrings that
  occur in the AST proper to be FastStrings. Strings in the AST are
  typically unique and don't benefit particularly from being interned
  FastStrings with Uniques for fast comparison.
  
  `HText` is a type synonym for `ShortText` which uses GHC's Modified
  UTF-8 encoding exclusively.
  
  Modified UTF-8 must be used to represent the Haskell AST because the
  Haskell Report allows surrogate code points. `Data.Text.Text` functions
  use Standard UTF-8 which replace surrogates with a placeholder value,
  thus `Data.Text.Text` is unsuitable for AST strings. See the
  `Language.Haskell.Syntax.Text` module header for more details.
  
  Final progress towards #21592
  
  Closes #21628
  

• d910b353
  by Simon Peyton Jones at 2026-07-08T04:48:36-04:00

  Update equality-type documenation in GHC.Builtin.Types.Prim
  
  Fix #27466
  

• b2530542
  by Simon Peyton Jones at 2026-07-08T04:48:36-04:00

  Honour -dsuppress-coercions in GHC.Core.TyCo.pprCo
  
  Fixes #27467
  

• 9a73179a
  by Facundo Domínguez at 2026-07-08T04:49:26-04:00

  Add item to MR checklist asking to squash fixup commits after approval
  
  The checklist has an item that reads
  
      All commits are either individually buildable or squashed.
  
  This item could be checked immediately after sending the merge request
  though. If reviewers ask for amends later on, and the author amends
  the merge request, there was no item that would remind the contributors
  to squash the fixup commits before landing.
  
  This commit adds a new item
  
      After all approvals and before landing: all fixup commits are squashed with their originating commits.
  
  which should be harder to mark as done before approvals have been given.
  

• ed09895d
  by Andreas Klebinger at 2026-07-08T16:53:27-04:00

  Fix a profiling race condition resulting in segfaults.
  
  StgToCmm: Don't assume tagged FUN closures in closureCodeBody.
  When entering a closure the self/node pointer might not be tagged in
  some situations when a thunk is evaluated by multiple threads.
  So we most AND away the tag bits rather than subtracting an expected tag.
  
  Apply.cmm: Fix a race condition occuring when a thunk is mutated during GC.
  
  In stg_ap_0_fast when might need to run GC before entering a thunk. If this happens
  another thread or the GC itself might mutate the closure making entering it no longer
  valid. We now check for this.
  
  Add test and changelog for #27123 fixes.
  

• 67c03eb2
  by Cheng Shao at 2026-07-08T16:54:09-04:00

  ghc-heap: fix invalid srtlen returned by peekItbl when no-TNTC
  
  This patch fixes the no-TNTC code path of `peekItbl` so that it looks
  at the right memory address when reading the `srt` field from the
  `StgInfoTable_` struct. Also adds a `T27465` regression test that
  reproduces the bug on no-TNTC builds before the fix. Fixes #27465.
  
  Co-authored-by: Codex <codex@openai.com>
  

• 2ecabb4f
  by Zubin Duggal at 2026-07-09T09:23:25-04:00

  hadrian: binary-dist-dir should not be the default target
  
  Revert behaviour to pre 23c9b6c392f52ec9d7a8618b204ff6b885f5fba2
  
  In 23c9b6c392f52ec9d7a8618b204ff6b885f5fba2, we applied the following behaviour change:
  
  ```
  hadrian: Build stage 2 cross compilers
  ...
  * hadrian: Make binary-dist-dir the default build target. This allows us
    to have the logic in one place about which libraries/stages to build
    with cross compilers. Fixes #24192
  ```
  
  This is a major regression to development experience, a plain hadrian/build
  --freeze1 now takes ages because we rebuild all docs (which need to go in the
  binary dist dir).
  
  `binary-dist-dir` is the wrong default target for regular GHC development work
  
  Fixes #27445
  

• e16388e3
  by Zubin Duggal at 2026-07-09T09:23:25-04:00

  .gitignore: Add the hadrian system.config introduced by commit 23c9b6c392f52ec9d7a8618b204ff6b885f5fba2
  
  Since
  
  commit 23c9b6c392f52ec9d7a8618b204ff6b885f5fba2
  Author: Matthew Pickering <matthewtpickering@gmail.com>
  Date:   Thu Dec 21 16:17:41 2023 +0000
  
      hadrian: Build stage 2 cross compilers
  
  ./configure produces /hadrian/cfg/system.config.{host,target}
  
  Add these to .gitignore
  

• 7e8abf41
  by Alan Zimmerman at 2026-07-09T09:24:12-04:00

  EPA: Replace AnnListItem with simply [TrailingAnn]
  
  Remove the unnecessary wrapper around a single field.
  

• 29032f17
  by Zubin Duggal at 2026-07-09T09:24:58-04:00

  testsuite: Keep real reason for fragile test failures
  

• c34e03a7
  by Zubin Duggal at 2026-07-09T09:24:58-04:00

  testsuite: Fall back to the failure reason for empty JUnit bodies
  

• 409d40f0
  by Zubin Duggal at 2026-07-09T09:24:58-04:00

  testsuite: Show output diffs in JUnit output
  
  Also refactor compare_outputs to return essentially a `Maybe Diff`
  (`CompareOutput`) instead of a bool, but more pythonic. This
  allows us to pass the diff through nice.
  

• 06fee1ab
  by Zubin Duggal at 2026-07-09T09:24:58-04:00

  perf notes: include stat deviation and acceptance window in notes so they show up in gitlab
  

• 57c0f32c
  by mangoiv at 2026-07-10T11:08:38-04:00

  driver: enable -finter-module-far-jumps by default
  
  this fixes a compatibility bug with certain binutils/gcc versions where
  we were seeing jump offset overflow errors.
  This commit can probably reverted if we stop supporting the problematic
  binutils/gcc verions (2.44 and 14.2, respectively)
  
  Reolves #26994
  

• 4396a6f2
  by Andrea Vezzosi at 2026-07-10T11:09:25-04:00

  [Fix #27287] preserve ModBreaks in ModIface
  

• ed261a7e
  by Cheng Shao at 2026-07-14T17:59:38-04:00

  hadrian: fix HLS support
  
  This patch fixes hadrian's HLS support so one can rely on HLS when
  working on the hadrian codebase. Fixes #27480.
  
  Not building/linking shared libraries for hadrian is a severely
  premature optimization; this top-level setting in `cabal.project` only
  affects home packages while the dependencies in the cabal store are
  built with vanilla/dynamic anyway, and even adding dynamic builds to
  home packages would not be costly due to cabal's usage of
  `-dynamic-too`.
  

• eee8ec5b
  by Cheng Shao at 2026-07-14T18:00:20-04:00

  compiler: fix miscompiled %load_relaxed, add missing %store_relaxed
  
  This patch fixes the %load_relaxed cmm primop compilation logic to
  correctly use relaxed memory ordering, and adds the missing
  %store_relaxed primop. Parsing logic of %load/%store with explicit
  ordering is covered in the AtomicFetch test case. Fixes #27483.
  
  Co-authored-by: Codex <codex@openai.com>
  

• 1718230f
  by Alan Zimmerman at 2026-07-14T18:01:06-04:00

  EPA: Keep binds and sigs together in HsValBindsLR
  
  We combine them into a single list for GhcPs, wrapped in the
  ValBind data type, which is the bind equivalent of ValD, having
  constructors for binds and sigs.
  
  This simplifies exact print processing, especially when using it to
  update the contents of local binds, as we no longer need AnnSortKey
  BindTag
  

• 6bd1ad2a
  by Andreas Klebinger at 2026-07-14T18:01:49-04:00

  Bump nofib submodule to account for MonoLocalBinds.
  
  New versions of GHC enable MonoLocalBinds by default.
  This breaks some of the benchmarks. I've fixed this and
  this bump pulls in that fix.
  

• 7eb0f1c9
  by Cheng Shao at 2026-07-14T18:02:31-04:00

  testsuite: fix bytecodeIPE test under +ipe flavours
  
  This patch fixes the bytecodeIPE test under +ipe flavours. It used to
  fail under +ipe because the RTS is built with IPE info, then
  stg_AP_info in RTS carries IPE info, so whereFrom wouldn't return
  Nothing. Now the test checks IPE info of a datacon in the ghci-loaded
  module which is not affected by whether the RTS is built with IPE info
  or not. Fixes #27498.
  
  Co-authored-by: Codex <codex@openai.com>
  

• ef038aae
  by cydparser at 2026-07-15T04:35:41-04:00

  Reduce bytes allocated for `capabilities` in RTS (fixes #27487)
  
  In rts/Capability.c, `capabilities` is an array of pointers, but it was allocated as if it were an
  array of Capability's.
  

• d377e83e
  by Cheng Shao at 2026-07-15T04:36:27-04:00

  rts: fix missing UNTAG in stg_readTVarIOzh
  
  This patch fixes missing UNTAG on the current value closure read from
  StgTVar. UNTAG is a no-op when it's stg_TREC_HEADER_info which is word
  aligned; it may be a tagged closure, and reading info table from the
  tagged address is an unaligned load which may cause issues on
  platforms with strict alignment requirements.
  
  Co-authored-by: Codex <codex@openai.com>
  

• 8ed03842
  by Cheng Shao at 2026-07-15T04:36:27-04:00

  rts: fix missing UNTAG in stg_control0zh_ll
  
  This patch fixes missing UNTAG on the cont closure returned by
  captureContinuationAndAbort. In case it's not NULL,
  captureContinuationAndAbort returns a tagged StgContinuation closure,
  in which case it must be untagged before accessing the
  apply_mask_frame field.
  
  In the past it worked out of luck: when apply_mask_frame was NULL then
  mask_frame_offset is also 0 so the control flow didn't diverge to a
  wrong path. Still, this is horribly wrong and will crash once
  StgContinuation struct is refactored and fields are shuffled around.
  
  Co-authored-by: Codex <codex@openai.com>
  

• 5aa7000a
  by Cheng Shao at 2026-07-15T04:37:08-04:00

  compiler: fix redundant AP thunk codegen when not using -ticky-ap-thunk
  
  This patch fixes a double negation confusion in !7525 that results in
  some redundant AP thunk code generation when not using
  -ticky-ap-thunk. Now, we use `stgToCmmUseStdApThunk` to indicate
  whether precomputed AP thunks in the RTS should be used, which
  defaults to `True`, unless `-ticky-ap-thunk` is passed.
  `-finfo-table-map` now also implies `-ticky-ap-thunk`, since when
  doing IPE profiling we want the generated AP thunks to be unique.
  Fixes #27502.
  
  -------------------------
  Metric Decrease:
      T3064
  -------------------------
  
  Co-authored-by: Codex <codex@openai.com>
  

• d43a7b7a
  by Brian McKenna at 2026-07-15T20:10:04+02:00

  Strip ticks when desugaring bool guards
  
  The special `considerAccessible` pattern was broken when compiling
  with debug info. Compiling with debug info wraps expressions with
  `SourceNote` ticks, which broke the internals of the
  `desugarBoolGuard` function. Ticks are now ignored within this
  function.
  
  Fixes #27360
  

• ede4b17b
  by Ben Gamari at 2026-07-15T22:59:53-04:00

  base: Display ExceptionContext in WhileHandling's textual description
  
  As originally-implemented the implementation for
  `WhileHandling(displayExceptionAnnotation)` would display the
  `ExceptionContext` of the exception which it carries (as this was the
  behavior of `displayException`, in terms of which
  `displayExceptionAnnotation` was implemented).
  
  However, in 284ffab3 the definition of `SomeException(displayException)`
  was changed to exclude the `ExceptionContext`. This means that
  `WhileHandling(displayExceptionAnnotation)` fails to describe the
  provenance of the exception which it captures, greatly limiting its
  utility.
  
  Return the implementation to its originally-specified behavior by
  implementing `WhileHandling(displayExceptionAnnotation)` in terms of
  `displayExceptionWithInfo`.
  
  Fixes #27456.
  

• 0f64f348
  by Cheng Shao at 2026-07-16T15:41:08+00:00

  ci: add missing docker permission workaround in abi-test job
  

• 660cb239
  by Cheng Shao at 2026-07-16T19:37:48+00:00

  bindist: Fix make install -j race condition on macos/freebsd
  
  This patch fixes make install -j race condition on macos/freebsd. BSD
  install fails with EEXIST when multiple install processes concurrently
  create the same prefix directory. So we add an `install_dirs`
  prerequisite job that sequentially creates the directories for
  subsequent jobs to work with. Fixes #27499.
  
  Co-authored-by: Codex <codex@openai.com>
  

• 08130257
  by Cheng Shao at 2026-07-16T19:37:48+00:00

  ci: run bindist make install with -j
  
  This patch makes the ci scripts run `make install` with `-j` to reduce
  wall clock time when installing the bindist, see related issue for
  benchmark numbers. This only affects ghc ci logic, the user-facing
  default is up to distributors and is still `-j1`. Closes #27029.
  

• d5ae6906
  by Adam Gundry at 2026-07-17T04:57:43-04:00

  Mark various language extension flags as deprecated (see #27329)
  
  The following language extensions are now deprecated:
  
   - AlternativeLayoutRule
   - AlternativeLayoutRuleTransitional
   - ParallelArrays
   - PolymorphicComponents
   - Rank2Types
  
  In addition, the warning `-Walternative-layout-rule-transitional`
  has been marked as deprecated, as it is emitted only under the
  deprecated extension `XAlternativeLayoutRuleTransitional`.
  

• fe3b059c
  by Andrew Lelechenko at 2026-07-17T04:58:26-04:00

  base: re-export GHC.Environment.getFullArgs from System.Environment
  
  CLC proposal https://github.com/haskell/core-libraries-committee/issues/431
  

• 722236dd
  by sheaf at 2026-07-18T08:48:31-04:00

  Coercion optimisation: avoid double-Sym for InstCo
  
  Ticket #27374 pointed out an issue with GHC.Core.Coercion.Opt.optCoercion's
  handling of InstCo: it contravened (LC2) in Note [The LiftingContext in optCoercion]
  because it applied the ambient 'sym' to a coercion that was then added
  to the lifting context substitution.
  
  Fixes #27374
  
  Co-authored-by: Simon Jakobi <simon.jakobi@gmail.com>
  

• ff70fc75
  by sheaf at 2026-07-18T08:48:31-04:00

  Coercion optimisation: avoid exponential behaviour
  
  The change to coercion optimisation of 'InstCo' in the previous commit
  introduces exponential behaviour to the coercion optimiser. To avoid
  this, this commit provides a way to push in 'Sym' of an already-optimised
  coercion: GHC.Core.Coercion.Opt.mkDeepSymCo.
  
  See Note [Pushing Sym without re-optimising] in GHC.Core.Coercion.Opt.
  

• dfef27f0
  by Duncan Coutts at 2026-07-18T08:49:12-04:00

  Move THREADED_RTS-conditional struct members to end of Capability
  
  Accessing members of the Capability struct from CMM code rely on
  accessor macros. (The macros are generated by deriveConstants).
  
  These macros have a single definition. This means that the offsets of
  all struct members must *not* vary based on THREADED_RTS vs
  !THREADED_RTS. This requires that any struct members that are
  conditional on THREADED_RTS must occur after the unconditional struct
  members. Hence we move all the ones that are conditional on
  THREADED_RTS to the end.
  
  Add a deriveConstants entry for the iomgr member of the Capability
  struct, which was the motivation for this change.
  
  Add warning messages to help our future selves. Debugging this took me
  a couple hours in gdb!
  

• c254e022
  by Duncan Coutts at 2026-07-18T08:49:12-04:00

  Make the IOManager API use CapIOManager rather than Capability
  
  This makes the API somewhat more self-contained and more consistent.
  Now the IOManager API and each of the backends takes just the I/O
  manager structure. Previously we had a bit of a mixture, depending on
  whether the function needed access to the Capability or just the
  CapIOManager.
  
  We still need access to the cap, so we introduce a back reference to
  reach the capability, via iomgr->cap.
  
  Convert all uses in select and poll backends, but not win32 ones.
  Convert callers in the scheduler and elsewhere.
  
  Also convert the three CMM primops that call IOManager APIs. They just
  need to use Capability_iomgr(MyCapability()).
  

• 4f3d8f31
  by Duncan Coutts at 2026-07-18T08:49:12-04:00

  Split posix/MIO.c out of posix/Signals.c
  
  The MIO I/O manager was secretly living inside the Signals file.
  
  Now it gets its own file, like any other self-respecting I/O manager.
  

• 52ce04a9
  by Duncan Coutts at 2026-07-18T08:49:12-04:00

  Rationalise some scheduler run queue utilities
  
  Move them all to the same place in the file.
  
  Make some static that were used only internally.
  
  Also remove a redundant assignment after calling truncateRunQueue that
  is already done within truncateRunQueue.
  

• 75bbdebc
  by Duncan Coutts at 2026-07-18T08:49:12-04:00

  Rename initIOManager{AfterFork} to {re}startIOManager
  
  These are more accurate names, since these actions happen after
  initialisation and are really about starting (or restarting) background
  threads.
  

• 724c0517
  by Duncan Coutts at 2026-07-18T08:49:12-04:00

  Free per-cap I/O managers during shutdown and forkProcess
  
  Historically this was not strictly necessary. The select and win32
  legacy I/O managers did not maintain any dynamically allocated
  resources. The new poll one does (an auxillary table), and so this
  should be freed.
  
  After forkProcess, all threads get deleted. This includes threads
  waiting on I/O or timers. So as of this patch, resetting the I/O
  manager is just about tidying things up. For example, for the poll
  I/O manager this will reset the size of the AIOP table (which
  otherwise grows but never shrinks).
  
  In future however the re-initialising will become neeecessary for
  functionality, since some I/O managers will need to re-initialise
  wakeup fds that are set CLOEXEC.
  

• c007d122
  by Duncan Coutts at 2026-07-18T08:49:12-04:00

  Add a TODO to the MIO I/O manager
  
  The direction of travel is to make I/O managers per-capability and have
  all their state live in the struct CapIOManager. The MIO I/O manager
  however still has a number of global variables.
  
  It's not obvious how handle these globals however.
  

• b65ab7b3
  by Duncan Coutts at 2026-07-18T08:49:12-04:00

  Add a FIXME note in the Poll I/O manager
  

• daf2bd6f
  by Duncan Coutts at 2026-07-18T08:49:12-04:00

  Add missing updateRemembSetPushClosure in poll I/O manager
  
  For the non-moving GC.
  

• e33ca830
  by Duncan Coutts at 2026-07-18T08:49:12-04:00

  Minor doc improvement to struct StgAsyncIOOp member outcome
  
  Mention the enumeration names, as well as their numeric values. The rest
  of the code uses the enum names.
  

• 4edd2579
  by Duncan Coutts at 2026-07-18T08:49:12-04:00

  Minor doc improvements for StgTSOBlockInfo
  
  Clarify that certain union members are used only by certain legacy
  I/O managers. Hopefully we will be able to remove these at some point.
  

• 536bedbb
  by Duncan Coutts at 2026-07-18T08:49:12-04:00

  Avoid exporting various win32-specific rts symbols
  
  The BeginPrivate.h / EndPrivate.h scheme works perfectly well on
  Windows, but all of the rts/win32/*.h files were not using it.
  

• 8139b5ac
  by Duncan Coutts at 2026-07-18T08:49:12-04:00

  Remove wakeupIOManager, ioManagerWakeup and setIOManagerWakeupFd
  
  We no longer need wakeupIOManager for the threaded RTS case, so we can
  remove it and the bits only needed to support it. This includes the
  pipe/eventfd fd shared between the RTS and the in-library I/O manager
  used for waking up the I/O manager thread. The pipe/eventfd still
  exists, but it no longer has to be communicated to the RTS, since the
  RTS no longer needs to use it.
  
  So we remove the RTS API export setIOManagerWakeupFd, and remove uses of
  it within the I/O managers in ghc-internal.
  

• 74fe7c66
  by Duncan Coutts at 2026-07-18T08:49:12-04:00

  Add a new interruptIOManager API for the I/O managers
  
  It will be used to interrupt awaitCompletedTimeoutsOrIO. Also update the
  return type and docs for awaitCompletedTimeoutsOrIO to have it return
  false when it gets interrupted, and have no useful post condition in
  that case.
  

• 38792843
  by Duncan Coutts at 2026-07-18T08:49:13-04:00

  Add interruptIOManager support for select I/O manager
  
  Uses the FdWakup mechanism.
  

• 2f3b00aa
  by Duncan Coutts at 2026-07-18T08:49:13-04:00

  Add interruptIOManager support for poll I/O manager
  
  Uses the FdWakup mechanism.
  
  A quirk we have to cope with is that we now need to poll one more fd --
  the wakeup_fd_r -- but this fd has no corresponding entry in the
  aiop_table. This is awkward since we have set up our aiop_poll_table to
  be an auxilliary table with matching indicies.
  
  The solution this patch uses (and described in the comments) is to have
  two tables: struct pollfd *aiop_poll_table, *full_poll_table;
  and to have the aiop_poll_table alias the tail of the full_poll_table.
  The head entry in the full_poll_table is the extra fd. So we poll the
  full_poll_table, while the aiop_poll_table still has matching indicies
  with the aiop_table.
  
  Hurrah for C aliasing rules.
  

• cee50131
  by Duncan Coutts at 2026-07-18T08:49:13-04:00

  Add interruptIOManager support for win32 legacy I/O manager
  
  And remove unused related helper resetAbandonRequestWait. It is not
  called because the event is created in auto-reset mode, so never needs
  to be reset manually.
  

• cf453143
  by Duncan Coutts at 2026-07-18T08:49:13-04:00

  Note lack of interruptIOManager support for WinIO I/O manager
  
  Though there's a plausible design, we can't sanely test it at the moment
  due to related WinIO bugs. Filed as issue #27403.
  

• 1b74a0ad
  by Duncan Coutts at 2026-07-18T08:49:13-04:00

  Be more explicit about enum IOReadOrWrite values, and type within cmm
  
  Belt and braces.
  

• b388d093
  by Brian McKenna at 2026-07-18T17:51:50-04:00

  Ignore ticks in the pattern-match term oracle
  
  The term-oracle in the pattern-match checker is keyed by a canonical
  form of the scrutinee, computed by `makeDictsCoherent`. That canonical
  form was tick-sensitive: two occurrences of an otherwise identical
  expression that happened to carry different ticks were treated as
  distinct values, breaking long-distance information.
  
  This shows up in practice under `-finfo-table-map`, because the
  desugarer wraps every record-selector use site in a `SourceNote`
  carrying that site's span. For example:
  
       data Box = Box { unBox :: Maybe Int }
       f b = case unBox b of
         Nothing -> 0
         Just _  -> let Just x = unBox b in x
  
  The two `unBox b` expressionss carry different SourceNote spans, the
  pattern-match checker sees them as different, the long-distance
  information from the outer `Just _` branch never reaches the
  let-pattern, and `Just x = unBox b` is wrongly reported as
  non-exhaustive.
  
  We now strip all ticks in `makeDictsCoherent`.  This is documented as
  Wrinkle (UD1) of Note [Unique dictionaries in the TmOracle CoreMap].
  
  Fixes #27314
  

• c23e1acb
  by Mrjtjmn at 2026-07-18T17:52:45-04:00

  Add explanations for unsolved Typeable constraints
  
  This commit adds explanations for unsolved 'Typeable' constraints.
  
  GHC will now provide additional explanations for an unsolved constraint
  of the form 'Typeable ty', explain why GHC did not solve Typeable constraint.
  e.g.:
   - 'ty' is a polymorphic type (e.g. forall a. a -> a)
   - 'ty' is a qualified type (e.g. Eq Int => Int)
   - 'ty' is an unboxed sum type
   - 'ty' is an unreduced type family application
   - 'ty' whose kind is not typeable
  
  Fixes #26532
  

• cbef021e
  by Artem Pelenitsyn at 2026-07-19T07:49:55-04:00

  ghc-internal: Lock.hs: fix typo and indentation

• 42918646
  by Duncan Coutts at 2026-07-19T07:50:36-04:00

  Fix failing test GcStaticPointers for non-moving GC
  
  Minor mistake in asserting something before checking for that same
  thing.
  
  Specifically, Bdescr asserts HEAP_ALLOCED_GC, but Bdescr was being used
  prior to a guard that checks HEAP_ALLOCED_GC. The solution is just to
  move the use of Bdescr after the guard.
  
  Thanks to Simon Jakobi for identifying the problem.
  

• c2f6dcd4
  by Sasha Bogicevic at 2026-07-20T10:31:56+02:00

  Improve error messages for invalid record wildcards
  
  Record wildcard hints are now shown in more contexts and include
  constructor arity; matching with `..` on a fieldless constructor
  now produces a dedicated error message.
  
  Fixes #21101
  

• 4c02e76b
  by Duncan Coutts at 2026-07-21T10:37:21-04:00

  Mark test T27105 as fragile, citing issue #27522
  
  Scheduler fairness is fine, except when it isn't. And it isn't on CI
  machines surprisingly often! See the issue for details.
  

• 43dd2b15
  by Recursion Ninja at 2026-07-21T17:09:53-04:00

  Resolving many TTG related orphan type-class instances
  
  This is part a technical debt removal effort made possible now
  that separating out the AST via TTG has come to a close.
  
  As the AST in 'L.H.S' has been incrementally separated from the GHC internals,
  there are many accumulated orphan instance of 'Binary', 'NFData', 'Outputable',
  and 'Uniquable'. The orphan instance of data-types from within 'L.H.S' have had
  their orphan instances moved to either:
    1. The module which defines the data-type
    2. The module which defines the type-class;
       i.e. moving an orphan 'Binary' instance to 'GHC.Utils.Binary'
  
  Orphan instances resolved (37):
  
    | Data-type            | Resolved instance(s)       | Former orphan module(s)   |
    | -------------------- | -------------------------- | ------------------------- |
    | Role                 | Binary, NFData, Outputable | GHC.Core.Coercion.Axiom   |
    | SrcStrictness        | Binary, NFData, Outputable | GHC.Core.DataCon          |
    | SrcUnpackedness      | Binary, NFData, Outputable | GHC.Core.DataCon          |
    | Fixity               | Binary, Outputable         | GHC.Hs.Basic              |
    | FixityDirection      | Binary, Outputable         | GHC.Hs.Basic              |
    | LexicalFixity        | Outputable                 | GHC.Hs.Basic              |
    | CCallTarget          | NFData                     | GHC.Hs.Decls.Foreign      |
    | CType                | NFData                     | GHC.Hs.Decls.Foreign      |
    | Header               | NFData                     | GHC.Hs.Decls.Foreign      |
    | OverlapMode          | Binary, NFData             | GHC.Hs.Decls.Overlap      |
    | WithHsDocIdentifiers | NFData, Outputable         | GHC.Hs.Doc                |
    | HsDocString          | NFData                     | GHC.Hs.DocString          |
    | HsDocStringChunk     | Binary, Outputable         | GHC.Hs.DocString          |
    | HsDocStringDecorator | Binary, Outputable         | GHC.Hs.DocString          |
    | NamespaceSpecifier   | Outputable                 | GHC.Hs.ImpExp             |
    | ForAllTyFlag         | Binary, NFData, Outputable | GHC.Hs.Specificity        |
    | Specificity          | Binary, NFData             | GHC.Hs.Specificity        |
    | PromotionFlag        | Binary, Outputable         | GHC.Types.Basic           |
    | FieldLabelString     | Outputable, Uniquable      | GHC.Types.FieldLabel      |
    | InlinePragma         | Binary                     | GHC.Types.InlinePragma    |
  
  -------------------------
  Metric Decrease:
      hard_hole_fits
  -------------------------
  
  Closes #21262, #27469
  

• ab9ab895
  by Cheng Shao at 2026-07-21T17:10:53-04:00

  rts: always use StgInt to represent cost center id
  
  Currently cost center id is modeled as `Int` and it should be `StgInt`
  uniformly in the RTS, hence this patch. Fixes #27524.
  

• 94d8f83b
  by Cheng Shao at 2026-07-22T11:30:40-04:00

  hadrian: clean up stale cabal package flags in the tree
  
  This patch cleans up stale cabal package flags in the tree and related
  hadrian/autoconf logic. Closes #27474.
  
  Co-authored-by: Codex <codex@openai.com>
  

• 0bf1d8c9
  by Sasha Bogicevic at 2026-07-22T11:31:21-04:00

  parser: don't suggest ImportQualifiedPost when it is already enabled
  
  -Wprepositive-qualified-module unconditionally attached a hint to
  enable ImportQualifiedPost, even when the extension was already on
  (as it is by default under GHC2021). Record the extension's state in
  the PsWarnImportPreQualified diagnostic and drop the hint when it is
  already enabled.
  
  Fixes #27380
  

• 700a1dd1
  by Simon Jakobi at 2026-07-23T11:21:20-04:00

  ci: Reduce lint job setup costs
  
  Avoid fetching unnecessary history and submodules for lightweight lint
  jobs. Run changelog validation without Hadrian.
  
  Because the lint-author job is now based on the .lint template directly,
  we enhance it to allow Git to read from the runner-owned checkouts,
  In the previously used .lint-params template, this permissions issue was
  addressed via `chown`.
  
  Closes #27521.
  
  Assisted-by: gpt-5.6-sol via Codex CLI
  

• 26a44fb0
  by ARATA Mizuki at 2026-07-23T11:22:10-04:00

  testsuite: Fix memory issues of doublex2_* and simd010
  
  doublex2_* had reads from uninitialized memory.
  
  simd010 had out-of-bounds array access.
  
  Fixes #27544
  

• 4d798b17
  by Duncan Coutts at 2026-07-23T17:26:18-04:00

  Eliminate STM_AWOKEN
  
  It was used as nullary closure for the block_info.closure in the case of
  a thread being awoken after an STM transaction.
  
  However, while it was written, it was never read, so contributed nothing
  to the behaviour. Furthermore, in the only place it was set (in
  tryWakeupThread) the why_blocked was immediately overwritten by the
  NotBlocked status, and the block_info was updated accordingly (by
  appendToRunQueue).
  
  So it didn't even serve a purpose of clarifying an intermediate state,
  there really was no such intermediate state.
  
  Cleaning this up will allow the BlockedOnSTM case to follow the same
  pattern as the other why_blocked cases that do not use the block_info,
  and in turn this reduces the number of different categories.
  

• e1cece79
  by Duncan Coutts at 2026-07-23T17:26:18-04:00

  Document that eventlog thread stop code ThreadBlocked is no longer used
  
  It has not been used since GHC 7.0.x (2011). In 7.2 all the BlockedOn*
  codes were added, and these were and are used instead of ThreadBlocked.
  

• 795db115
  by Duncan Coutts at 2026-07-23T17:26:18-04:00

  Add a proper mapping to eventlog external thread stop status
  
  That is the mapping from rts-internal codes, to the coes used in the
  status field in the eventlog EVENT_STOP_THREAD event.
  
  See issue #9003 for what goes wrong when we mess this up. In that
  ticket, people note that we should really not require the internal
  tso->why_blocked codes to leak into the external eventlog thread stop
  codes. The same principle applies to the StgThreadReturnCode.
  
  This change properly separates them, and explicitly maps between them
  using a pair of (compact, constant) tables. These tables are pretty
  small (with no alignment constraints) and will soon shrink so it seems
  a sensible tradeoff.
  
  We also introduce and use proper EVENT_STOP_THREAD constants in the
  event log format header. Previously there was not specification in the
  code for these (only in the docs): the values were encoded into the
  conversion code.
  
  This will allow us to renumber the internal why_blockd codes without
  breaking the eventlog output.
  

• 6f1c8efa
  by Duncan Coutts at 2026-07-23T17:26:18-04:00

  Remove unused tso->block_info.wakeup member
  
  Presumably it was used once, but not now.
  

• 740b88a9
  by Duncan Coutts at 2026-07-23T17:26:18-04:00

  Document StgTSOBlockInfo to say what cases use what members
  
  In principle, tso->why_blocked is the tag for the StgTSOBlockInfo union,
  so we should be able to say for each union member the why_blocked cases
  that use that member.
  

• 5b92eae2
  by Duncan Coutts at 2026-07-23T17:26:18-04:00

  Add a tso->block_info.mvar member and use it
  
  in preference to the generic block_info.closure union member, with
  casts.
  
  The plan is that when we know what case we're in (via tso->why_blocked)
  then we can always access the correct union member, and so we will only
  need to access block_info.closure for generic cases where we don't know
  or don't care.
  

• d931715f
  by Duncan Coutts at 2026-07-23T17:26:18-04:00

  Add a tso->block_info.unused member and use it
  
  in preference to the generic block_info.closure union member, with
  casts.
  
  The plan is that when we know what case we're in (via tso->why_blocked)
  then we can always access the correct union member, and so we will only
  need to access block_info.closure for generic cases where we don't know
  or don't care.
  

• 47e28ebb
  by Duncan Coutts at 2026-07-23T17:26:18-04:00

  Avoid storing to tso->block_info.closure
  
  In one case we can use a specific union member (.prev) instead. In
  several cases the stores were in fact redundant because of subsequent
  overwrites.
  
  In scavengeTSO we replace setting tso->block_info.closure to a valid
  closure, with an assertion that the block_info.unused is already set to
  END_TSO_QUEUE which is a valid (static) closure.
  

• 96e4749d
  by Duncan Coutts at 2026-07-23T17:26:18-04:00

  Renumber the tso->why_blocked constants
  
  We can do this now because we have separated the internal values from
  the external ones used in the eventlog.
  
  This lets us put them back into a deliberate order and consolodate some
  gaps.
  
  More importantly, it is a prepation for a slightly more sophisticated
  encoding.
  

• 8f62661c
  by Duncan Coutts at 2026-07-23T17:26:18-04:00

  Define constants for the existing stg_threadStatuszh return codes
  
  The stg_threadStatuszh reuses the internal tso->why_blocked codes but
  also extends them with a couple previously magic values. This is awkward
  since we need to know what those magic values are so we don't
  accidentally use those values to mean something else. By pulling a
  definition up to where the why_blocked codes are defined we will be able
  to avoid mistakenly assining those codes some meaning (or just changing
  the BlockedThreadComplete, BlockedThreadKilled code if necessary).
  

• 42c69ae2
  by Duncan Coutts at 2026-07-23T17:26:18-04:00

  Extend the tso->why_blocked encoding to indicate block_info closures
  
  We use some bit tricks to cheaply and generically test if a
  tso->why_blocked tag implies that the corresponding tso->block_info will
  contain a non-trivial valid closure (i.e. not just block_info.unused set
  to END_TSO_QUEUE).
  
  In particular we arrange for most why_blocked values to naturally have a
  distinguishing bit, but for the BlockedOn{Read,Write,Delay} cases, they
  can come in either non-closure or closure forms. We allow an additional
  bit to distinguish these cases. The non-closure forms are only from
  legacy I/O managers: select and win32-legacy. So this extra bit
  mechanism will be able to be retired once the legacy I/O managers are
  themselves retired.
  
  This means in a few places we need to untag the why_blocked value before
  inspecting it, but in most places we do not.
  

• 7c64632b
  by Duncan Coutts at 2026-07-23T17:26:18-04:00

  Use BlockInfoForceNonClosure in the select I/O manager
  

• 8fd7104a
  by Duncan Coutts at 2026-07-23T17:26:18-04:00

  Use BlockInfoForceNonClosure in the win32-legacy I/O manager
  
  for the BlockedOn{Read,Write} since these use the non-heap allocated
  StgAsyncIOResult.
  

• e0da603b
  by Duncan Coutts at 2026-07-23T17:26:18-04:00

  Enforce the why_blocked and block_info rules in checkTSO
  
  We now check the cases wher IsBlockInfoClosure should hold, the cases
  that are supposed to use block_info.unused == END_TSO_QUEUE, and which
  cases are allowed to use BlockInfoForceNonClosure.
  
  This partially enforces the use of why_blocked as a tag for the
  block_info union. We could be stricter and check for the correct
  expected info table for the closure cases.
  

• 1dd0f381
  by Duncan Coutts at 2026-07-23T17:26:18-04:00

  Use IsBlockInfoClosure to simplify several tests
  
  In GC and generic traversal we need to know if we should look at the
  block_info.closure or not. Now we can do just that using a cheap bit
  test on the why_blocked tag.
  
  This fixes issue 26717, where the problem was that some GC modes did not
  know when to look at block_info.closure, because the poll I/O manager
  uses a closure for BlockedOn{Read,Write} while the select I/O manager
  uses a non-closure. Now this information is in the why_blocked tag
  itself.
  

• 7a00ffbc
  by Duncan Coutts at 2026-07-23T17:26:18-04:00

  Remove the now-unused scavengeTSOIOManager
  
  The GC no longer has to delegate to the I/O manager, since it can use
  IsBlockInfoClosure to decide things itself.
  

• 522a481f
  by Duncan Coutts at 2026-07-23T17:26:18-04:00

  Remove duplicate assertion
  

• 0874d965
  by Duncan Coutts at 2026-07-23T17:26:18-04:00

  Follow atomic access rules more consistently for tso->why_blocked
  
  The rule is this:
  
  store block_info *before* why_blocked
  store why_blocked using store release
  
  load why_blocked using load acquire
  load block_info *after* why_blocked
  
  This is a an atomic store release / load acquire pair and (if the reads
  are in a separate thread to the writes, and the read receives the value
  stored) then this guarantees a full "happens before" relationship of
  these stores and loads.
  
  In some cases, we do not need a full load acquire, because we don't read
  the block_info at all and so do not need any ordering. In this case we
  just need an atomic relaxed load.
  
  This was being followed in most places, but not all. If there's good
  reason in any case that we don't need atomic access, then we should
  document that in a comment. In the absence of that I think it's easier
  to follow the rule everywhere.
  

• 8f0bdbe1
  by Duncan Coutts at 2026-07-23T17:26:19-04:00

  Add a changelog entry
  

• 4fdfe757
  by Alan Zimmerman at 2026-07-23T17:27:06-04:00

  EPA: Keep decls together in ClassDecl
  
  Similar to 1718230f4d3d19d8c49c0e5d496cb0fb6f399528 for HsValBindsLR,
  this commit updates ClassDecl so that it no longer splits out the
  assorted `LHsDecl GhcPs` until the renamer.
  
  It does this by inserting a type family (separate from the classic TTG one) for this.
  
  So
  
  data TyClDecl
    ...
    | ClassDecl {
      ...
         tcdDecls   :: XClassDecls pass
  
  with
  
  type instance XClassDecls GhcPs = [LHsDecl GhcPs]
  type instance XClassDecls GhcRn = ClassDeclX GhcRn
  type instance XClassDecls GhcTc = ClassDeclX GhcTc
  
  data ClassDeclX pass
    = ClassDeclX { tcdSigs    :: [LSig pass],              -- ^ Methods' signatures
                   tcdMeths   :: LHsBinds pass,            -- ^ Default methods
                   tcdATs     :: [LFamilyDecl pass],       -- ^ Associated types;
                   tcdATDefs  :: [LTyFamDefltDecl pass],   -- ^ Associated type defaults
                   tcdDocs    :: [LDocDecl pass]           -- ^ Haddock docs
      }
  

• f586c885
  by Simon Jakobi at 2026-07-24T18:05:00-04:00

  ci: Use shallow submodule clones by default
  
  Limit submodule clones to depth one to reduce CI checkout costs. Keep
  fetching full submodule history for the submodule lint jobs, which
  inspect commits across a range.
  
  Assisted-by: gpt-5.6-sol via Codex CLI
  

• 306120d2
  by Duncan Coutts at 2026-07-24T18:05:43-04:00

  Fix flaky test T3994 on FreeBSD
  
  On current FreeBSD versions, calling getpgid on a zombie process fails.
  In T3994, if we're really unlucky with delays and scheduling then we can
  end up in exactly that situation.
  
  Just catch that specific exception and ignore it. It's rare, and not our
  fault.
  

• 7b116a0b
  by Cheng Shao at 2026-07-24T18:06:24-04:00

  ci: add missing workaround for docker permissions in lint jobs
  
  Some lint jobs use ci-images with default user `ghc`, and the gitlab
  ci docker executor requires the `sudo chown` workaround to fix
  workspace directory permission issue. This patch adds the missing
  workarounds for the lint jobs. Fixes #27554.
  
  Co-authored-by: Codex <codex@openai.com>
  

• 815149f3
  by Andrzej Rybczak at 2026-07-25T15:06:43+00:00

  Add -Wdefaulted-callstack
  
  Adds a new warning, -Wdefaulted-callstack, which warns when an implicit
  CallStack parameter is defaulted to the empty stack. In particular, this
  includes call sites where a function with a HasCallStack constraint is called
  from a definition that does *not* provide one. At such call sites the call stack
  is cut off and does not include the enclosing definition's callers, which can be
  a source of surprise if the user wants complete call stacks.
  
  Closes #27077.
  

• f6f2343f
  by Zubin Duggal at 2026-07-25T17:40:51-04:00

  UniqueDFM: alter should preserve insertion order
  
  Before it always inserting new elements at the end.
  This is problematic because instances get inserted into the map with
  `alterF`, which can change ordering of how instances are printed
  with `:info` depending on the order in which we consult interfaces
  
  I expect `alter id k = id` and `alter (fmap f) k = adjust f k`. Moving keys to
  the end breaks that (`adjust` already preserves position).
  
  Fixes #27532
  

• 5d0ab71a
  by fendor at 2026-07-27T17:31:05-04:00

  Introduce global unit database cache
  
  As a first step for better sharing of `UnitInfo` across `UnitEnv`,
  we introduce a new datatype called `ExternalUnitDatabases`.
  
  It primarily serves as an in-memory representation of *all*
  `UnitDatabase`s across `UnitEnv`. This means, if multiple `HomeUnitEnv`s
  depend on the same database, one way or another, we make sure that we
  don't parse from disk every time.
  Instead, we store the in-memory representation in `ExternalUnitDatabases`.
  
  `ExternalUnitDatabaseCache` is the equivalent of `ExternalUnitState` in
  the `UnitEnv`. It is a mutable variable wrapping `ExternalUnitDatabases`.
  
  The mutable `ExternalUnitDatabaseCache` is used in `initUnits` to make
  sure we don't parse the same unit database multiple times.
  
  Almost by accident, we change the semantics of `initUnits` to honour
  modifications to `packageDBFlags`.
  The inability to change `packageDBFlags` while also reusing the already
  parsed `UnitDatabase`s was reported in #26423 as a bug.
  Hence, we think this behaviour change is warranted and acceptable,
  especially since it comes with a breaking change to the `initUnits` API.
  
  Add regression test for #26423
  Closes #26423
  

• 6cce494a
  by fendor at 2026-07-27T17:31:05-04:00

  Introduce UnitIndex for global external unit caching
  
  `UnitInfo`s have been observed to cause a lot of memory usage in #27500.
  Especially with multiple home units, as the same (external) units are
  processed from scratch, even though most of the time we end up with
  exactly the same `UnitInfo`.
  
  We introduce a `UnitEnv` global cache that allows us to store external
  unit information that is used across all `HomeUnitEnv`s.
  
  The most important change in this commit is the introduction of the `UnitIndex`.
  It stores a global mapping of `UnitId` -> `UnitInfo`, and `initUnits`
  always uses the cached `UnitInfo` entry to populate each
  `HomeUnitEnv`'s `UnitState`.
  This allows us to ensure the following property:
  
  > Each `UnitInfo` should be alive exactly once in GHC.
  
  All `UnitState`s should reference 'UnitInfo's stored in the 'UnitIndex'.
  This ensured by calling 'initUnits' with the 'UnitIndex'.
  
  In addition, the `ExternalUnitDatabases` may also hold a reference
  to each on-disk representation of `UnitInfo`.
  
  This means, we impose an hard upper bound on the number of `UnitInfo`s
  alive in the GHC session:
  
  > The number of alive `UnitInfo`s closure objects must be the
  > sum of all loaded unit database times two.
  
  We add performance regression tests that make sure the number of live
  `UnitInfo` cannot exceed this threshold.
  
  Closes #27500
  
  -------------------------
  Metric Decrease:
      MultiComponentModules
      MultiComponentModulesRecomp
      MultiComponentModulesRecomp100
      mhu-perf
      LinkableUsage02
  -------------------------
  
  These metrics increases are especially notable, as we are not even
  sharing anything big but merely the global package database with 50
  entries.
  It shows how careful sharing of `UnitInfo` can improve memory usage.
  We expect this to be much more notable when the whole cabal package
  database is shared across multiple home units.
  
  `LinkableUsage02` metric decreases on unreg and i386 platform, only.
  
  ---
  
  Technical details
  
  To share the `UnitInfo`s correctly, it is important that we extract
  the `WireMap` into the `UnitIndex`. At the moment of writing, `WireMap`
  must be globally the same for all `HomeUnitEnv`s.
  This is important, as we could otherwise not cache the "fully-resolved"
  `UnitInfo`, as we don't change the `UnitId` or `unitAbiHash` when
  resolving wired-in units. Thus, there could be ambiguities, when the
  `WireMap` is not the same for all `UnitState`s across the `UnitEnv`.
  
  We consider a `UnitInfo` fully-resolved, if wired-in units have been
  updated, the `UnitInfo` has been validated and variables in the unit
  config, such as `${pkgroot}` have been resolved.
  
  Updating the wired-in units requires the `WireMap` to be globally the
  same.
  

• f8e3bee9
  by Zubin Duggal at 2026-07-27T17:31:49-04:00

  testsuite: skip runtime stats tests on debugged compilers
  
  Debugged flavours build the boot libraries without optimisation, so the
  runtime numbers do not match the baselines.
  

• 1e326770
  by Zubin Duggal at 2026-07-27T17:31:50-04:00

  testsuite: mark #20706 tests fragile rather than broken
  
  Whether the static linux linker issues manifest depends on the host
  toolchain.
  

• c0b13cbe
  by Zubin Duggal at 2026-07-27T17:31:50-04:00

  testsuite: exclude libnuma from mostly-static
  
  It needs static system libraries (libnuma.a) that many platforms do not
  ship.
  
  Fixes #26914
  

• bee1913d
  by Alan Zimmerman at 2026-07-28T16:42:29-04:00

  EPA: ClsInstDecl with decls as [LHsDecl GhcPs] in GhcPs
  
  Similar to 4fdfe75731e01dad7d7fa474c2703d0d3965afb1, this commit
  changes the as-parsed representation of class instance declarations to
  [LHsDecl GhcPs], and only separates them by type from the renamer onward.
  
  This also allows us to remove all the AnnSortKey machinery for exact
  printing, as it is now no longer needed.
  

• 72c55eee
  by Cheng Shao at 2026-07-28T16:43:11-04:00

  hadrian: implement and use writeFileAtomic to fix race condition
  
  This patch implements `writeFileAtomic` in hadrian and change all
  invocations of shake non-atomic `writeFile'` to use `writeFileAtomic`,
  to avoid multiple hadrian concurrent invocations overwriting the same
  in-tree generated file not in the build root directory. Fixes #27536.
  Additional notes:
  
  - `writeFileChanged`/`writeFileChangedBS` cannot be made atomic since
    it involves reading the file's older version, so their uses are left
    alone. It doesn't affect #27536 given their outputs are contained in
    the build root directory.
  - It's possible to shrink this patch by only making writes outside the
    build root directory atomic. But I think it's not worth the effort
    for fine grained distinction here, and atomic writes within the
    build root directory should also improve robustness of a hadrian
    build.
  - In the longer term we do want to make a ghc build only generate
    files within the build root directory, though that's a lot of work
    and outside the scope of this particular bugfix.
  
  Co-authored-by: Codex <codex@openai.com>
  

• 46d4f963
  by Sylvain Henry at 2026-07-29T06:38:40-04:00

  RTS: correctly mark slop bytes when shrinking large arrays (#19048)
  
  Correctly mark slop bytes even when profiling is off so that heap census
  doesn't traverse garbage-collected closures.
  

• 4762a8bf
  by Simon Jakobi at 2026-07-29T06:39:23-04:00

  Add -XLazyFieldAnnotations (GHC proposal 752)
  
  Unbundle the prefix `~` lazy field annotation syntax from StrictData. The
  new LazyFieldAnnotations extension controls whether `~` is accepted on
  constructor fields. StrictData (and Strict, transitively) imply the new
  extension.
  
  See https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0752-lazy-field-annotations.rst.
  
  Closes #24455.
  
  Assisted-by: Claude Opus 4.8
  

• 0b6dcc84
  by Simon Jakobi at 2026-07-29T06:40:04-04:00

  testsuite: Relax T24471 residency tolerance
  
  T24471 peak residency fluctuates enough on i386 to cause spurious
  failures. Use the standard residency tolerance while retaining the
  existing allocation threshold.
  
  See https://gitlab.haskell.org/ghc/ghc/-/work_items/24471#note_682303.
  
  Assisted-by: gpt-5.6-sol via Codex CLI
  

• 90e95b34
  by Cheng Shao at 2026-07-29T06:40:45-04:00

  compiler: fix missing top-level procedure labels in cmm dumps
  
  This patch fixes missing top-level procedure labels in some
  intermediate Cmm pass dumps. Fixes #27553.
  
  Co-authored-by: Codex <codex@openai.com>
  

• 360a5946
  by sheaf at 2026-07-29T06:41:35-04:00

  Add some type-family-heavy performance tests
  
  FamAppCachePerf stress-tests the performance of lookups in the
  type family application cache.
  
  T27336 is a minimisation extracted from the reported reproducer.
  
  SimplCastPerf is a measure of coercion growth due to the simplifier
  calling mkTransCo without re-optimising the result.
  

• 3ec9e2b9
  by Mike Pilgrem at 2026-07-31T08:21:33-04:00

  GHC Guide: Improve docs on response files
  

• e5b2a1f7
  by sheaf at 2026-07-31T08:22:23-04:00

  Disable Core Lint for TcPlugin_RewritePerf
  
  This is a compiler performance test, but the test source hard-coded
  -dcore-lint, defeating the measurement.
  
  -------------------------
  Metric Decrease:
      TcPlugin_RewritePerf
  -------------------------
  

• 85b10c00
  by Alan Zimmerman at 2026-07-31T22:09:47+01:00

  EPA: Remove LocatedP from OverlapMode
  
  We have
  
    type LocatedP = GenLocated SrcSpanAnnP
    type SrcSpanAnnP = EpAnn AnnPragma
  
  As the first step in removing this in favour of LocatedA which only
  captures location, comments and trailing annotations, we remove it
  from OverlapMode
  
  We do this by moving the AnnPragma into the TTG extension point
  instead.
  

• c9a34a00
  by Viktor Dukhovni at 2026-08-02T04:34:17-04:00

  Fix note typo
  

• 4f2a21f7
  by Andreas Klebinger at 2026-08-02T22:46:46-04:00

  Apply oneShot Monad trick to STG LintM
  

• 21e4b89d
  by Andreas Klebinger at 2026-08-02T22:46:46-04:00

  stgLint: Use a single reader env for read only arguments.
  

• d415f38a
  by Alan Zimmerman at 2026-08-02T22:47:27-04:00

  EPA: Remove LocatedP from CType
  
  The next step of removing use of LocatedP by moving
  the AnnPragma for CType into its TTG extension point
  instead.
  

• 5379e154
  by Zubin Duggal at 2026-08-04T11:37:40+02:00

  hie files: Also dump the type table when dumping with -ddump-hie
  

• 5d626640
  by Zubin Duggal at 2026-08-04T11:40:25+02:00

  hie files: Take evidence for quantified constraints into account when saving evidence terms to the hie ast
  
  Fixes #25709
  

• 3415f4ef
  by fendor at 2026-08-04T11:43:27+02:00

  fixup! hie files: Also dump the type table when dumping with -ddump-hie
  

• c420ccbc
  by fendor at 2026-08-04T16:57:03+02:00

  WIP: test case for quantified constraints
  

4431 changed files:

• .gitattributes
• .gitignore
• .gitlab-ci.yml
• .gitlab/ci.sh
• .gitlab/common.sh
• .gitlab/darwin/nix/sources.json
• .gitlab/darwin/toolchain.nix
• + .gitlab/generate-ci/cabal.project
• .gitlab/generate-ci/flake.lock
• .gitlab/generate-ci/gen_ci.hs
• .gitlab/issue_templates/default.md
• + .gitlab/issue_templates/get-verified.md
• + .gitlab/issue_templates/release_tracking.md
• .gitlab/jobs.yaml
• .gitlab/merge_request_templates/Default.md
• .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
• .gitlab/test-metrics.sh
• .gitmodules
• .mailmap
• CODEOWNERS
• README.md
• boot
• cabal.project-reinstall
• + changelog.d/21101
• + changelog.d/26616
• + changelog.d/27380
• + changelog.d/27532
• + changelog.d/AbstractQ
• + changelog.d/T15973
• + changelog.d/T17833
• + changelog.d/T19174.md
• + changelog.d/T21176
• + changelog.d/T21628
• + changelog.d/T25636
• + changelog.d/T26423
• + changelog.d/T26532
• + changelog.d/T26716
• + changelog.d/T26978
• + changelog.d/T26979
• + changelog.d/T27022
• + changelog.d/T27046
• + changelog.d/T27047
• + changelog.d/T27121.md
• + changelog.d/T27123.md
• + changelog.d/T27124.md
• + changelog.d/T27131
• + changelog.d/T27182.md
• + changelog.d/T27202
• + changelog.d/T27225
• + changelog.d/T27261
• + changelog.d/T27308
• + changelog.d/T27314.md
• + changelog.d/T27317
• + changelog.d/T27329
• + changelog.d/T27359
• + changelog.d/T27360
• + changelog.d/T27374
• + changelog.d/T27386
• + changelog.d/T27456
• + changelog.d/add_can_drop_to_occurence_analyser
• + changelog.d/binary-array-no-list
• + changelog.d/bump-process
• + changelog.d/bytecode-interpreter-hpc-support
• + changelog.d/changelog-entries
• + changelog.d/cmm-import-syntax-changes
• + changelog.d/config
• + changelog.d/deterministic-usage-order
• + changelog.d/dynamic-trace-flags
• + changelog.d/elem-via-foldr-27096
• + changelog.d/fix-absent-dict-projection
• + changelog.d/fix-blackhole-handling
• + changelog.d/fix-cmm-atomic-load-store
• + changelog.d/fix-cmm-dump-labels
• + changelog.d/fix-compacting-gc-ap-27434
• + changelog.d/fix-duplicate-pmc-warnings
• + changelog.d/fix-exponential-case-desugar-27383
• + changelog.d/fix-finalizers-27072
• + changelog.d/fix-ghci-duplicate-warnings-26233
• + changelog.d/fix-heap-census-large-arrays-19048
• + changelog.d/fix-layout-stack-fcall
• + changelog.d/fix-make-install-j
• + changelog.d/fix-peekitbl-no-tntc
• + changelog.d/fix-plugin-finder-multi-home-unit.md
• + changelog.d/fix-unreg
• + changelog.d/fix-use-std-ap-thunk
• + changelog.d/generically-mconcat
• + changelog.d/ghc-api-epa-parens
• + changelog.d/ghc-api-holes-ast-27111
• + changelog.d/ghc-api-namespace-specifier-26678
• + changelog.d/ghc-pkg-faster-closure
• + changelog.d/ghc-pkg-long-path-support
• + changelog.d/hadrian-response-files.md
• + changelog.d/hadrian-stale-package-confs-26661
• + changelog.d/hadrian-system-cxx-std-lib-25303
• + changelog.d/hadrian-warn-missing-package-index-16484
• + changelog.d/inter-module-far-jumps-aarch64-default
• + changelog.d/interactive-error-hints
• + changelog.d/ipe-event-class
• + changelog.d/jobserver-leak-fix
• + changelog.d/lazy-field-annotations
• + changelog.d/lib-add-tuple-tyfam-27179
• + changelog.d/libdir-setting
• + changelog.d/llvm-22
• + changelog.d/module-graph-reuse-in-downsweep
• + changelog.d/more-efficient-home-unit-imports-finding
• + changelog.d/no-more-timer-signal
• + changelog.d/pp-set-ghc-version
• + changelog.d/reexported-module-errors
• + changelog.d/remove-bignum-check-backend
• + changelog.d/remove-bignum-ffi-backend
• + changelog.d/remove-ddump-json-flag
• + changelog.d/rts_symlinks.md
• + changelog.d/semaphore-v2
• + changelog.d/simd_constant_folding
• + changelog.d/skip-test
• + changelog.d/so_inline_is_a_predicate
• + changelog.d/stable-core-dump-order-27296
• + changelog.d/stage2-cross-compilers
• + changelog.d/tag-inference-27005
• + changelog.d/tcplugin_init.md
• + changelog.d/tcplugins-pmc.md
• + changelog.d/tool-messages-27370
• + changelog.d/typecheckModule-API.md
• + changelog.d/unit-index
• + changelog.d/unused-type
• + changelog.d/warn-defaulted-callstack
• + changelog.d/wasm-fix-serviceworker
• + changelog.d/windows-rethrow-overlapped-exception
• + changelog.d/withTcPlugins.md
• compile_flags.txt
• compiler/.hlint.yaml
• 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/Utils.hs
• compiler/GHC/Builtin/primops.txt.pp
• compiler/GHC/ByteCode/Asm.hs
• + compiler/GHC/ByteCode/Binary.hs
• + compiler/GHC/ByteCode/Breakpoints.hs
• compiler/GHC/ByteCode/InfoTable.hs
• compiler/GHC/ByteCode/Instr.hs
• compiler/GHC/ByteCode/Linker.hs
• + compiler/GHC/ByteCode/Recomp/Binary.hs
• + compiler/GHC/ByteCode/Serialize.hs
• compiler/GHC/ByteCode/Types.hs
• compiler/GHC/Cmm.hs
• compiler/GHC/Cmm/BlockId.hs
• compiler/GHC/Cmm/CLabel.hs
• compiler/GHC/Cmm/CommonBlockElim.hs
• compiler/GHC/Cmm/Config.hs
• compiler/GHC/Cmm/ContFlowOpt.hs
• compiler/GHC/Cmm/Dataflow.hs
• compiler/GHC/Cmm/Dataflow/Block.hs
• compiler/GHC/Cmm/Dataflow/Graph.hs
• compiler/GHC/Cmm/Dataflow/Label.hs
• compiler/GHC/Cmm/DebugBlock.hs
• compiler/GHC/Cmm/Dominators.hs
• compiler/GHC/Cmm/Expr.hs
• compiler/GHC/Cmm/Graph.hs
• compiler/GHC/Cmm/Info.hs
• compiler/GHC/Cmm/Info/Build.hs
• compiler/GHC/Cmm/InitFini.hs
• compiler/GHC/Cmm/LRegSet.hs
• compiler/GHC/Cmm/LayoutStack.hs
• compiler/GHC/Cmm/Lexer.x
• compiler/GHC/Cmm/Lint.hs
• compiler/GHC/Cmm/Liveness.hs
• compiler/GHC/Cmm/MachOp.hs
• compiler/GHC/Cmm/Node.hs
• compiler/GHC/Cmm/Opt.hs
• compiler/GHC/Cmm/Parser.y
• compiler/GHC/Cmm/Pipeline.hs
• compiler/GHC/Cmm/ProcPoint.hs
• compiler/GHC/Cmm/Reducibility.hs
• compiler/GHC/Cmm/Reg.hs
• compiler/GHC/Cmm/Sink.hs
• compiler/GHC/Cmm/Switch.hs
• compiler/GHC/Cmm/Switch/Implement.hs
• compiler/GHC/Cmm/ThreadSanitizer.hs
• compiler/GHC/Cmm/Type.hs
• compiler/GHC/Cmm/UniqueRenamer.hs
• compiler/GHC/Cmm/Utils.hs
• compiler/GHC/CmmToAsm/AArch64/CodeGen.hs
• compiler/GHC/CmmToAsm/AArch64/Instr.hs
• compiler/GHC/CmmToAsm/AArch64/Ppr.hs
• compiler/GHC/CmmToAsm/AArch64/RegInfo.hs
• compiler/GHC/CmmToAsm/AArch64/Regs.hs
• compiler/GHC/CmmToAsm/BlockLayout.hs
• compiler/GHC/CmmToAsm/CFG.hs
• compiler/GHC/CmmToAsm/CPrim.hs
• compiler/GHC/CmmToAsm/Config.hs
• compiler/GHC/CmmToAsm/Dwarf/Types.hs
• compiler/GHC/CmmToAsm/Format.hs
• compiler/GHC/CmmToAsm/LA64/CodeGen.hs
• compiler/GHC/CmmToAsm/LA64/Instr.hs
• compiler/GHC/CmmToAsm/LA64/Ppr.hs
• compiler/GHC/CmmToAsm/LA64/Regs.hs
• compiler/GHC/CmmToAsm/Monad.hs
• compiler/GHC/CmmToAsm/PPC/CodeGen.hs
• compiler/GHC/CmmToAsm/PPC/Ppr.hs
• compiler/GHC/CmmToAsm/PPC/RegInfo.hs
• compiler/GHC/CmmToAsm/PPC/Regs.hs
• compiler/GHC/CmmToAsm/Ppr.hs
• compiler/GHC/CmmToAsm/RV64/CodeGen.hs
• compiler/GHC/CmmToAsm/RV64/Instr.hs
• compiler/GHC/CmmToAsm/RV64/Ppr.hs
• compiler/GHC/CmmToAsm/RV64/Regs.hs
• compiler/GHC/CmmToAsm/Reg/Graph.hs
• compiler/GHC/CmmToAsm/Reg/Graph/Coalesce.hs
• compiler/GHC/CmmToAsm/Reg/Graph/Spill.hs
• compiler/GHC/CmmToAsm/Reg/Graph/SpillClean.hs
• compiler/GHC/CmmToAsm/Reg/Graph/SpillCost.hs
• compiler/GHC/CmmToAsm/Reg/Graph/TrivColorable.hs
• compiler/GHC/CmmToAsm/Reg/Linear.hs
• compiler/GHC/CmmToAsm/Reg/Linear/Base.hs
• compiler/GHC/CmmToAsm/Reg/Linear/FreeRegs.hs
• compiler/GHC/CmmToAsm/Reg/Linear/JoinToTargets.hs
• compiler/GHC/CmmToAsm/Reg/Linear/StackMap.hs
• compiler/GHC/CmmToAsm/Reg/Linear/State.hs
• compiler/GHC/CmmToAsm/Reg/Linear/X86.hs
• compiler/GHC/CmmToAsm/Reg/Linear/X86_64.hs
• compiler/GHC/CmmToAsm/Reg/Liveness.hs
• + compiler/GHC/CmmToAsm/Reg/Regs.hs
• compiler/GHC/CmmToAsm/Reg/Target.hs
• compiler/GHC/CmmToAsm/Wasm.hs
• compiler/GHC/CmmToAsm/Wasm/Asm.hs
• compiler/GHC/CmmToAsm/Wasm/FromCmm.hs
• compiler/GHC/CmmToAsm/Wasm/Types.hs
• compiler/GHC/CmmToAsm/X86/CodeGen.hs
• compiler/GHC/CmmToAsm/X86/Instr.hs
• compiler/GHC/CmmToAsm/X86/Ppr.hs
• compiler/GHC/CmmToAsm/X86/RegInfo.hs
• compiler/GHC/CmmToAsm/X86/Regs.hs
• compiler/GHC/CmmToC.hs
• compiler/GHC/CmmToLlvm.hs
• compiler/GHC/CmmToLlvm/Base.hs
• compiler/GHC/CmmToLlvm/CodeGen.hs
• compiler/GHC/CmmToLlvm/Config.hs
• compiler/GHC/CmmToLlvm/Data.hs
• compiler/GHC/CmmToLlvm/Mangler.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/Axiom.hs
• 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/InstEnv.hs
• compiler/GHC/Core/LateCC/OverloadedCalls.hs
• compiler/GHC/Core/LateCC/TopLevelBinds.hs
• compiler/GHC/Core/Lint.hs
• compiler/GHC/Core/Lint/Interactive.hs
• + compiler/GHC/Core/Lint/SubstTypeLets.hs
• compiler/GHC/Core/Make.hs
• compiler/GHC/Core/Map/Expr.hs
• compiler/GHC/Core/Map/Type.hs
• compiler/GHC/Core/Multiplicity.hs
• compiler/GHC/Core/Opt/Arity.hs
• compiler/GHC/Core/Opt/CSE.hs
• compiler/GHC/Core/Opt/CallArity.hs
• compiler/GHC/Core/Opt/CallerCC.hs
• compiler/GHC/Core/Opt/ConstantFold.hs
• compiler/GHC/Core/Opt/CprAnal.hs
• compiler/GHC/Core/Opt/DmdAnal.hs
• compiler/GHC/Core/Opt/FloatIn.hs
• compiler/GHC/Core/Opt/FloatOut.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/Range.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/TyCon/Env.hs
• compiler/GHC/Core/TyCon/RecWalk.hs
• compiler/GHC/Core/Type.hs
• compiler/GHC/Core/Type.hs-boot
• 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/Bag.hs
• compiler/GHC/Data/BooleanFormula.hs
• compiler/GHC/Data/FastString.hs
• compiler/GHC/Data/FastString/Env.hs
• compiler/GHC/Data/FlatBag.hs
• compiler/GHC/Data/Graph/Collapse.hs
• compiler/GHC/Data/Graph/Color.hs
• compiler/GHC/Data/Graph/Directed.hs
• compiler/GHC/Data/IOEnv.hs
• compiler/GHC/Data/List/Infinite.hs
• compiler/GHC/Data/List/NonEmpty.hs
• compiler/GHC/Data/List/SetOps.hs
• compiler/GHC/Data/Maybe.hs
• compiler/GHC/Data/OsPath.hs
• compiler/GHC/Data/Pair.hs
• compiler/GHC/Data/Stream.hs
• compiler/GHC/Data/Strict.hs
• compiler/GHC/Data/StringBuffer.hs
• compiler/GHC/Data/TrieMap.hs
• compiler/GHC/Data/Word64Map.hs
• compiler/GHC/Data/Word64Map/Internal.hs
• compiler/GHC/Data/Word64Map/Lazy.hs
• compiler/GHC/Data/Word64Map/Strict.hs
• compiler/GHC/Data/Word64Map/Strict/Internal.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/CmmToLlvm.hs
• compiler/GHC/Driver/Config/Core/Lint.hs
• compiler/GHC/Driver/Config/Core/Lint/Interactive.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/Config/StgToCmm.hs
• compiler/GHC/Driver/Config/Tidy.hs
• compiler/GHC/Driver/Downsweep.hs
• compiler/GHC/Driver/DynFlags.hs
• compiler/GHC/Driver/Env.hs
• compiler/GHC/Driver/Env/KnotVars.hs
• compiler/GHC/Driver/Env/Types.hs
• compiler/GHC/Driver/Errors.hs
• compiler/GHC/Driver/Errors/Ppr.hs
• compiler/GHC/Driver/Errors/Types.hs
• compiler/GHC/Driver/Flags.hs
• compiler/GHC/Driver/GenerateCgIPEStub.hs
• compiler/GHC/Driver/Hooks.hs
• compiler/GHC/Driver/LlvmConfigCache.hs
• compiler/GHC/Driver/Main.hs
• + compiler/GHC/Driver/Main/Compile.hs
• compiler/GHC/Driver/Main.hs-boot → compiler/GHC/Driver/Main/Compile.hs-boot
• + compiler/GHC/Driver/Main/Hsc.hs
• + compiler/GHC/Driver/Main/Interactive.hs
• + compiler/GHC/Driver/Main/Passes.hs
• + compiler/GHC/Driver/Main/Passes.hs-boot
• compiler/GHC/Driver/Make.hs
• compiler/GHC/Driver/MakeAction.hs
• compiler/GHC/Driver/MakeFile.hs
• compiler/GHC/Driver/MakeSem.hs
• compiler/GHC/Driver/Messager.hs
• compiler/GHC/Driver/Monad.hs
• compiler/GHC/Driver/Phases.hs
• compiler/GHC/Driver/Pipeline.hs
• compiler/GHC/Driver/Pipeline/Execute.hs
• compiler/GHC/Driver/Pipeline/LogQueue.hs
• compiler/GHC/Driver/Pipeline/Monad.hs
• compiler/GHC/Driver/Pipeline/Phases.hs
• compiler/GHC/Driver/Plugins.hs
• compiler/GHC/Driver/Session.hs
• + compiler/GHC/Driver/Session/Inspect.hs
• compiler/GHC/Driver/Session/Units.hs
• compiler/GHC/Hs.hs
• compiler/GHC/Hs/Basic.hs
• compiler/GHC/Hs/Binds.hs
• compiler/GHC/Hs/Decls.hs
• + compiler/GHC/Hs/Decls/Overlap.hs
• compiler/GHC/Hs/Doc.hs
• − compiler/GHC/Hs/Doc.hs-boot
• compiler/GHC/Hs/DocString.hs
• compiler/GHC/Hs/Dump.hs
• compiler/GHC/Hs/Expr.hs
• compiler/GHC/Hs/Expr.hs-boot
• compiler/GHC/Hs/Extension.hs
• + compiler/GHC/Hs/Extension/Pass.hs
• compiler/GHC/Hs/ImpExp.hs
• compiler/GHC/Hs/Instances.hs
• compiler/GHC/Hs/Lit.hs
• compiler/GHC/Hs/Pat.hs
• compiler/GHC/Hs/Pat.hs-boot
• − compiler/GHC/Hs/Specificity.hs
• compiler/GHC/Hs/Stats.hs
• compiler/GHC/Hs/Syn/Type.hs
• compiler/GHC/Hs/Type.hs
• compiler/GHC/Hs/Utils.hs
• compiler/GHC/HsToCore.hs
• compiler/GHC/HsToCore/Arrows.hs
• compiler/GHC/HsToCore/Binds.hs
• compiler/GHC/HsToCore/Breakpoints.hs
• + compiler/GHC/HsToCore/Breakpoints/Types.hs
• compiler/GHC/HsToCore/Coverage.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/Decl.hs
• compiler/GHC/HsToCore/Foreign/JavaScript.hs
• compiler/GHC/HsToCore/Foreign/Utils.hs
• compiler/GHC/HsToCore/Foreign/Wasm.hs
• compiler/GHC/HsToCore/GuardedRHSs.hs
• compiler/GHC/HsToCore/ListComp.hs
• compiler/GHC/HsToCore/Match.hs
• compiler/GHC/HsToCore/Match.hs-boot
• compiler/GHC/HsToCore/Match/Constructor.hs
• compiler/GHC/HsToCore/Match/Literal.hs
• compiler/GHC/HsToCore/Monad.hs
• compiler/GHC/HsToCore/Pmc.hs
• compiler/GHC/HsToCore/Pmc/Check.hs
• compiler/GHC/HsToCore/Pmc/Desugar.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/Types.hs
• compiler/GHC/HsToCore/Usage.hs
• compiler/GHC/HsToCore/Utils.hs
• compiler/GHC/Iface/Binary.hs
• compiler/GHC/Iface/Decl.hs
• compiler/GHC/Iface/Env.hs
• compiler/GHC/Iface/Errors.hs
• compiler/GHC/Iface/Errors/Ppr.hs
• compiler/GHC/Iface/Errors/Types.hs
• compiler/GHC/Iface/Ext/Ast.hs
• compiler/GHC/Iface/Ext/Binary.hs
• compiler/GHC/Iface/Ext/Debug.hs
• compiler/GHC/Iface/Ext/Types.hs
• compiler/GHC/Iface/Ext/Utils.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/Iface/Warnings.hs
• compiler/GHC/IfaceToCore.hs
• compiler/GHC/JS/Ident.hs
• compiler/GHC/JS/JStg/Monad.hs
• compiler/GHC/JS/JStg/Syntax.hs
• compiler/GHC/JS/Make.hs
• compiler/GHC/JS/Optimizer.hs
• compiler/GHC/JS/Ppr.hs
• compiler/GHC/JS/Syntax.hs
• compiler/GHC/JS/Transform.hs
• + compiler/GHC/Linker/ByteCode.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/Unit.hs
• compiler/GHC/Linker/Windows.hs
• compiler/GHC/Llvm/MetaData.hs
• compiler/GHC/Llvm/Ppr.hs
• compiler/GHC/Llvm/Types.hs
• compiler/GHC/Parser.y
• compiler/GHC/Parser/Annotation.hs
• compiler/GHC/Parser/Errors/Basic.hs
• compiler/GHC/Parser/Errors/Ppr.hs
• compiler/GHC/Parser/Errors/Types.hs
• compiler/GHC/Parser/HaddockLex.x
• 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/String.hs
• compiler/GHC/Parser/Types.hs
• compiler/GHC/Platform.hs
• compiler/GHC/Platform/Reg.hs
• compiler/GHC/Platform/Reg/Class.hs
• compiler/GHC/Platform/Reg/Class/NoVectors.hs
• compiler/GHC/Platform/Reg/Class/Separate.hs
• compiler/GHC/Platform/Reg/Class/Unified.hs
• + compiler/GHC/Platform/Tag.hs
• compiler/GHC/Platform/Ways.hs
• compiler/GHC/Plugins.hs
• compiler/GHC/Prelude/Basic.hs
• compiler/GHC/Rename/Bind.hs
• compiler/GHC/Rename/Doc.hs
• compiler/GHC/Rename/Env.hs
• compiler/GHC/Rename/Expr.hs
• compiler/GHC/Rename/Expr.hs-boot
• compiler/GHC/Rename/Fixity.hs
• compiler/GHC/Rename/HsType.hs
• + compiler/GHC/Rename/Lit.hs
• compiler/GHC/Rename/Module.hs
• compiler/GHC/Rename/Names.hs
• compiler/GHC/Rename/Pat.hs
• compiler/GHC/Rename/Splice.hs
• compiler/GHC/Rename/Splice.hs-boot
• compiler/GHC/Rename/Unbound.hs
• compiler/GHC/Rename/Utils.hs
• compiler/GHC/Runtime/Debugger.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/Heap/Layout.hs
• compiler/GHC/Runtime/Interpreter.hs
• + compiler/GHC/Runtime/Interpreter/C.hs
• + compiler/GHC/Runtime/Interpreter/Init.hs
• compiler/GHC/Runtime/Interpreter/JS.hs
• compiler/GHC/Runtime/Interpreter/Process.hs
• compiler/GHC/Runtime/Interpreter/Types.hs
• compiler/GHC/Runtime/Interpreter/Types/SymbolCache.hs
• compiler/GHC/Runtime/Interpreter/Wasm.hs
• compiler/GHC/Runtime/Loader.hs
• compiler/GHC/Settings.hs
• compiler/GHC/Settings/Constants.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/Rewrite.hs
• compiler/GHC/Stg/EnforceEpt/TagSig.hs
• compiler/GHC/Stg/EnforceEpt/Types.hs
• compiler/GHC/Stg/FVs.hs
• compiler/GHC/Stg/Lift/Analysis.hs
• compiler/GHC/Stg/Lift/Monad.hs
• compiler/GHC/Stg/Lift/Types.hs
• compiler/GHC/Stg/Lint.hs
• compiler/GHC/Stg/Pipeline.hs
• compiler/GHC/Stg/Syntax.hs
• compiler/GHC/Stg/Unarise.hs
• compiler/GHC/Stg/Utils.hs
• compiler/GHC/StgToByteCode.hs
• compiler/GHC/StgToCmm.hs
• compiler/GHC/StgToCmm/ArgRep.hs
• compiler/GHC/StgToCmm/Bind.hs
• compiler/GHC/StgToCmm/CgUtils.hs
• compiler/GHC/StgToCmm/Closure.hs
• compiler/GHC/StgToCmm/Config.hs
• compiler/GHC/StgToCmm/DataCon.hs
• compiler/GHC/StgToCmm/Env.hs
• compiler/GHC/StgToCmm/Expr.hs
• compiler/GHC/StgToCmm/ExtCode.hs
• compiler/GHC/StgToCmm/Foreign.hs
• compiler/GHC/StgToCmm/Heap.hs
• compiler/GHC/StgToCmm/InfoTableProv.hs
• compiler/GHC/StgToCmm/Layout.hs
• compiler/GHC/StgToCmm/Lit.hs
• compiler/GHC/StgToCmm/Monad.hs
• compiler/GHC/StgToCmm/Prim.hs
• compiler/GHC/StgToCmm/Prof.hs
• compiler/GHC/StgToCmm/Ticky.hs
• compiler/GHC/StgToCmm/Utils.hs
• compiler/GHC/StgToJS/Apply.hs
• compiler/GHC/StgToJS/Arg.hs
• compiler/GHC/StgToJS/CodeGen.hs
• compiler/GHC/StgToJS/DataCon.hs
• compiler/GHC/StgToJS/Deps.hs
• compiler/GHC/StgToJS/Expr.hs
• compiler/GHC/StgToJS/ExprCtx.hs
• compiler/GHC/StgToJS/FFI.hs
• compiler/GHC/StgToJS/Heap.hs
• compiler/GHC/StgToJS/Ids.hs
• compiler/GHC/StgToJS/Linker/Linker.hs
• compiler/GHC/StgToJS/Linker/Opt.hs
• compiler/GHC/StgToJS/Linker/Types.hs
• compiler/GHC/StgToJS/Linker/Utils.hs
• compiler/GHC/StgToJS/Literal.hs
• compiler/GHC/StgToJS/Monad.hs
• compiler/GHC/StgToJS/Object.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/Sinker/Collect.hs
• compiler/GHC/StgToJS/Sinker/Sinker.hs
• compiler/GHC/StgToJS/Sinker/StringsUnfloat.hs
• compiler/GHC/StgToJS/StaticPtr.hs
• compiler/GHC/StgToJS/Types.hs
• compiler/GHC/StgToJS/Utils.hs
• compiler/GHC/SysTools.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/SysTools/Terminal.hs
• compiler/GHC/Tc/Deriv.hs
• compiler/GHC/Tc/Deriv/Functor.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/Hole/FitTypes.hs
• compiler/GHC/Tc/Errors/Hole/Plugin.hs
• compiler/GHC/Tc/Errors/Ppr.hs
• compiler/GHC/Tc/Errors/Types.hs
• compiler/GHC/Tc/Errors/Types/PromotionErr.hs
• compiler/GHC/Tc/Gen/Annotation.hs
• compiler/GHC/Tc/Gen/App.hs
• compiler/GHC/Tc/Gen/Arrow.hs
• compiler/GHC/Tc/Gen/Bind.hs
• compiler/GHC/Tc/Gen/Default.hs
• compiler/GHC/Tc/Gen/Do.hs
• + compiler/GHC/Tc/Gen/Expand.hs
• compiler/GHC/Tc/Gen/Export.hs
• compiler/GHC/Tc/Gen/Expr.hs
• compiler/GHC/Tc/Gen/Expr.hs-boot
• compiler/GHC/Tc/Gen/Foreign.hs
• compiler/GHC/Tc/Gen/Head.hs
• compiler/GHC/Tc/Gen/HsType.hs
• compiler/GHC/Tc/Gen/Match.hs
• compiler/GHC/Tc/Gen/Match.hs-boot
• 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/Instance/Typeable.hs
• compiler/GHC/Tc/Module.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/Class.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/BasicTypes.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/LclEnv.hs
• compiler/GHC/Tc/Types/Origin.hs
• compiler/GHC/Tc/Types/Origin.hs-boot
• compiler/GHC/Tc/Types/Rank.hs
• compiler/GHC/Tc/Types/TH.hs
• compiler/GHC/Tc/Utils/Backpack.hs
• compiler/GHC/Tc/Utils/Concrete.hs
• compiler/GHC/Tc/Utils/Env.hs
• compiler/GHC/Tc/Utils/Instantiate.hs
• compiler/GHC/Tc/Utils/Monad.hs
• compiler/GHC/Tc/Utils/TcMType.hs
• − compiler/GHC/Tc/Utils/TcMType.hs-boot
• compiler/GHC/Tc/Utils/TcType.hs
• compiler/GHC/Tc/Utils/TcType.hs-boot
• compiler/GHC/Tc/Utils/Unify.hs
• compiler/GHC/Tc/Utils/Unify.hs-boot
• compiler/GHC/Tc/Validity.hs
• compiler/GHC/Tc/Zonk/Monad.hs
• compiler/GHC/Tc/Zonk/TcType.hs
• compiler/GHC/Tc/Zonk/Type.hs
• compiler/GHC/ThToHs.hs
• compiler/GHC/Types/Annotations.hs
• + compiler/GHC/Types/Arity.hs
• compiler/GHC/Types/Avail.hs
• compiler/GHC/Types/Basic.hs
• − compiler/GHC/Types/Breakpoint.hs
• compiler/GHC/Types/CompleteMatch.hs
• compiler/GHC/Types/CostCentre.hs
• compiler/GHC/Types/CostCentre/State.hs
• compiler/GHC/Types/DefaultEnv.hs
• compiler/GHC/Types/Demand.hs
• compiler/GHC/Types/Error.hs
• compiler/GHC/Types/Error/Codes.hs
• compiler/GHC/Types/FieldLabel.hs
• compiler/GHC/Types/Fixity.hs
• compiler/GHC/Types/ForeignCall.hs
• compiler/GHC/Types/ForeignStubs.hs
• compiler/GHC/Types/GREInfo.hs
• compiler/GHC/Types/Hint.hs
• compiler/GHC/Types/Hint/Ppr.hs
• compiler/GHC/Types/HpcInfo.hs
• compiler/GHC/Types/Id.hs
• compiler/GHC/Types/Id/Info.hs
• compiler/GHC/Types/Id/Make.hs
• + compiler/GHC/Types/InlinePragma.hs
• compiler/GHC/Types/Literal.hs
• + compiler/GHC/Types/Literal/Floating.hs
• compiler/GHC/Types/Name.hs
• compiler/GHC/Types/Name/Cache.hs
• compiler/GHC/Types/Name/Env.hs
• compiler/GHC/Types/Name/Occurrence.hs
• compiler/GHC/Types/Name/Reader.hs
• compiler/GHC/Types/Name/Set.hs
• compiler/GHC/Types/PkgQual.hs
• compiler/GHC/Types/RepType.hs
• compiler/GHC/Types/SaneDouble.hs
• compiler/GHC/Types/SourceError.hs
• compiler/GHC/Types/SourceText.hs
• compiler/GHC/Types/SptEntry.hs
• compiler/GHC/Types/SrcLoc.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/DSet.hs
• compiler/GHC/Types/Unique/FM.hs
• compiler/GHC/Types/Unique/Map.hs
• compiler/GHC/Types/Unique/SDFM.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/Types/Var/FV.hs
• compiler/GHC/Types/Var/Set.hs
• compiler/GHC/Unit.hs
• compiler/GHC/Unit/Env.hs
• + compiler/GHC/Unit/External/Database.hs
• + compiler/GHC/Unit/External/Index.hs
• + compiler/GHC/Unit/External/ModuleOrigin.hs
• + compiler/GHC/Unit/External/Providers.hs
• + compiler/GHC/Unit/External/Query.hs
• + compiler/GHC/Unit/External/Substitution.hs
• + compiler/GHC/Unit/External/Validate.hs
• + compiler/GHC/Unit/External/Visibility.hs
• + compiler/GHC/Unit/External/Wired.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/Home/PackageTable.hs
• compiler/GHC/Unit/Info.hs
• compiler/GHC/Unit/Module.hs
• compiler/GHC/Unit/Module/Deps.hs
• compiler/GHC/Unit/Module/Env.hs
• compiler/GHC/Unit/Module/Graph.hs
• compiler/GHC/Unit/Module/Location.hs
• compiler/GHC/Unit/Module/ModGuts.hs
• compiler/GHC/Unit/Module/ModIface.hs
• compiler/GHC/Unit/Module/ModSummary.hs
• compiler/GHC/Unit/Module/Status.hs
• compiler/GHC/Unit/Module/Warnings.hs
• compiler/GHC/Unit/Module/WholeCoreBindings.hs
• compiler/GHC/Unit/State.hs
• + compiler/GHC/Unit/State.hs-boot
• compiler/GHC/Unit/Types.hs
• compiler/GHC/Unit/Types.hs-boot
• compiler/GHC/Utils/Binary.hs
• compiler/GHC/Utils/Binary/Typeable.hs
• + compiler/GHC/Utils/EndoOS.hs
• compiler/GHC/Utils/Error.hs
• compiler/GHC/Utils/Exception.hs
• − compiler/GHC/Utils/FV.hs
• compiler/GHC/Utils/Json.hs
• compiler/GHC/Utils/Logger.hs
• compiler/GHC/Utils/Misc.hs
• compiler/GHC/Utils/Monad.hs
• compiler/GHC/Utils/Monad/Codensity.hs
• compiler/GHC/Utils/Outputable.hs
• compiler/GHC/Utils/Panic.hs
• compiler/GHC/Utils/Panic/Plain.hs
• compiler/GHC/Utils/Ppr.hs
• compiler/GHC/Utils/Trace.hs
• compiler/GHC/Wasm/ControlFlow.hs
• compiler/GHC/Wasm/ControlFlow/FromCmm.hs
• compiler/Language/Haskell/Syntax.hs
• compiler/Language/Haskell/Syntax/Basic.hs
• compiler/Language/Haskell/Syntax/Binds.hs
• + compiler/Language/Haskell/Syntax/Binds/InlinePragma.hs
• compiler/Language/Haskell/Syntax/Decls.hs
• + compiler/Language/Haskell/Syntax/Decls/Foreign.hs
• + compiler/Language/Haskell/Syntax/Decls/Overlap.hs
• + compiler/Language/Haskell/Syntax/Doc.hs
• compiler/Language/Haskell/Syntax/Expr.hs
• compiler/Language/Haskell/Syntax/Expr.hs-boot
• compiler/Language/Haskell/Syntax/Extension.hs
• compiler/Language/Haskell/Syntax/ImpExp.hs
• compiler/Language/Haskell/Syntax/Lit.hs
• compiler/Language/Haskell/Syntax/Module/Name.hs
• compiler/Language/Haskell/Syntax/Pat.hs
• compiler/Language/Haskell/Syntax/Pat.hs-boot
• compiler/Language/Haskell/Syntax/Specificity.hs
• + compiler/Language/Haskell/Syntax/Text.hs
• compiler/Language/Haskell/Syntax/Type.hs
• − compiler/Language/Haskell/Syntax/Type.hs-boot
• compiler/Setup.hs
• compiler/cbits/keepCAFsForGHCi.c
• compiler/ghc.cabal.in
• config.guess
• config.sub
• configure.ac
• distrib/configure.ac.in
• − docs/Makefile
• − docs/storage-mgt/Makefile
• + docs/users_guide/10.2.1-notes.rst
• − docs/users_guide/9.14.1-notes.rst
• − docs/users_guide/Makefile
• 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/control.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/modifiers.rst
• docs/users_guide/exts/multiway_if.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/qualified_strings.rst
• docs/users_guide/exts/rank_polymorphism.rst
• docs/users_guide/exts/rebindable_syntax.rst
• docs/users_guide/exts/recursive_do.rst
• + docs/users_guide/exts/relaxed_poly_rec.rst
• docs/users_guide/exts/required_type_arguments.rst
• docs/users_guide/exts/rewrite_rules.rst
• docs/users_guide/exts/roles.rst
• docs/users_guide/exts/scoped_type_variables.rst
• docs/users_guide/exts/standalone_deriving.rst
• docs/users_guide/exts/static_pointers.rst
• docs/users_guide/exts/stolen_syntax.rst
• docs/users_guide/exts/strict.rst
• docs/users_guide/exts/syntax.rst
• docs/users_guide/exts/table.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/ghc_config.py.in
• − docs/users_guide/ghc_packages.py
• docs/users_guide/ghci.rst
• docs/users_guide/gone_wrong.rst
• docs/users_guide/hints.rst
• docs/users_guide/index.rst
• docs/users_guide/javascript.rst
• docs/users_guide/packages.rst
• docs/users_guide/phases.rst
• docs/users_guide/profiling.rst
• docs/users_guide/release-notes.rst
• docs/users_guide/rtd-theme/layout.html
• docs/users_guide/runtime_control.rst
• docs/users_guide/separate_compilation.rst
• docs/users_guide/using-concurrent.rst
• docs/users_guide/using-optimisation.rst
• docs/users_guide/using-warnings.rst
• docs/users_guide/using.rst
• docs/users_guide/utils.py
• docs/users_guide/wasm.rst
• docs/users_guide/win32-dlls.rst
• − driver/Makefile
• − driver/ghc/Makefile
• − driver/ghci/Makefile
• driver/ghci/ghci.c
• − driver/haddock/Makefile
• driver/utils/cwrapper.c
• driver/utils/isMinTTY.c
• − driver/utils/merge_sections.ld
• − driver/utils/merge_sections_pe.ld
• ghc/GHC/Driver/Session/Lint.hs
• ghc/GHC/Driver/Session/Mode.hs
• ghc/GHCi/Leak.hs
• 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/Makefile
• ghc/ghc-bin.cabal.in
• hadrian/README.md
• hadrian/bindist/Makefile
• hadrian/bindist/config.mk.in
• hadrian/bindist/cwrappers/cwrapper.c
• 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_10_3.json
• hadrian/bootstrap/plan-9_6_4.json → hadrian/bootstrap/plan-9_12_1.json
• hadrian/bootstrap/plan-9_6_3.json → hadrian/bootstrap/plan-9_12_2.json
• + hadrian/bootstrap/plan-9_14_1.json
• − hadrian/bootstrap/plan-9_6_1.json
• − hadrian/bootstrap/plan-9_6_2.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_10_3.json
• hadrian/bootstrap/plan-bootstrap-9_8_1.json → hadrian/bootstrap/plan-bootstrap-9_12_1.json
• hadrian/bootstrap/plan-bootstrap-9_6_4.json → hadrian/bootstrap/plan-bootstrap-9_12_2.json
• + hadrian/bootstrap/plan-bootstrap-9_14_1.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_8_2.json
• hadrian/bootstrap/src/Main.hs
• hadrian/build-cabal
• hadrian/build-cabal.bat
• hadrian/cabal.project
• hadrian/cfg/default.host.target.in
• hadrian/cfg/default.target.in
• + hadrian/cfg/system.config.host.in
• hadrian/cfg/system.config.in
• + hadrian/cfg/system.config.target.in
• hadrian/doc/flavours.md
• hadrian/doc/make.md
• hadrian/doc/testsuite.md
• hadrian/doc/user-settings.md
• hadrian/hadrian.cabal
• hadrian/src/Base.hs
• + hadrian/src/BindistConfig.hs
• hadrian/src/Builder.hs
• hadrian/src/CommandLine.hs
• hadrian/src/Context.hs
• hadrian/src/Expression.hs
• hadrian/src/Flavour.hs
• hadrian/src/Flavour/Type.hs
• hadrian/src/Hadrian/Builder.hs
• hadrian/src/Hadrian/Builder/Ar.hs
• hadrian/src/Hadrian/Haskell/Cabal/Parse.hs
• hadrian/src/Hadrian/Haskell/Cabal/Type.hs
• hadrian/src/Hadrian/Haskell/Hash.hs
• hadrian/src/Hadrian/Oracles/ArgsHash.hs
• hadrian/src/Hadrian/Oracles/Cabal/Type.hs
• hadrian/src/Hadrian/Oracles/DirectoryContents.hs
• hadrian/src/Hadrian/Oracles/Path.hs
• hadrian/src/Hadrian/Oracles/TextFile.hs
• hadrian/src/Hadrian/Utilities.hs
• hadrian/src/Main.hs
• hadrian/src/Oracles/Flag.hs
• hadrian/src/Oracles/Flavour.hs
• hadrian/src/Oracles/ModuleFiles.hs
• hadrian/src/Oracles/Setting.hs
• hadrian/src/Oracles/TestSettings.hs
• hadrian/src/Packages.hs
• hadrian/src/Rules.hs
• hadrian/src/Rules/BinaryDist.hs
• hadrian/src/Rules/CabalReinstall.hs
• + hadrian/src/Rules/Changelog.hs
• hadrian/src/Rules/Compile.hs
• hadrian/src/Rules/Docspec.hs
• hadrian/src/Rules/Documentation.hs
• hadrian/src/Rules/Generate.hs
• hadrian/src/Rules/Gmp.hs
• − hadrian/src/Rules/Libffi.hs
• hadrian/src/Rules/Library.hs
• hadrian/src/Rules/Lint.hs
• hadrian/src/Rules/Nofib.hs
• hadrian/src/Rules/Program.hs
• hadrian/src/Rules/Register.hs
• hadrian/src/Rules/Rts.hs
• hadrian/src/Rules/SourceDist.hs
• hadrian/src/Rules/Test.hs
• hadrian/src/Rules/ToolArgs.hs
• hadrian/src/Settings.hs
• hadrian/src/Settings/Builders/Cabal.hs
• hadrian/src/Settings/Builders/Cc.hs
• hadrian/src/Settings/Builders/Common.hs
• hadrian/src/Settings/Builders/Configure.hs
• hadrian/src/Settings/Builders/DeriveConstants.hs
• hadrian/src/Settings/Builders/GenPrimopCode.hs
• hadrian/src/Settings/Builders/Ghc.hs
• hadrian/src/Settings/Builders/Hsc2Hs.hs
• hadrian/src/Settings/Builders/Make.hs
• − hadrian/src/Settings/Builders/MergeObjects.hs
• hadrian/src/Settings/Builders/RunTest.hs
• hadrian/src/Settings/Builders/SplitSections.hs
• hadrian/src/Settings/Default.hs
• − hadrian/src/Settings/Flavours/Benchmark.hs
• hadrian/src/Settings/Flavours/Development.hs
• hadrian/src/Settings/Flavours/GhcInGhci.hs
• hadrian/src/Settings/Flavours/Performance.hs
• hadrian/src/Settings/Flavours/Quick.hs
• hadrian/src/Settings/Flavours/QuickCross.hs
• hadrian/src/Settings/Flavours/Quickest.hs
• hadrian/src/Settings/Flavours/Validate.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/Makefile
• libraries/Win32
• libraries/array
• libraries/base/base.cabal.in
• libraries/base/changelog.md
• libraries/base/src/Control/Applicative.hs
• libraries/base/src/Control/Arrow.hs
• libraries/base/src/Control/Concurrent.hs
• libraries/base/src/Control/Exception.hs
• libraries/base/src/Control/Exception/Backtrace.hs
• libraries/base/src/Control/Monad.hs
• libraries/base/src/Control/Monad/IO/Class.hs
• libraries/base/src/Data/Array/Byte.hs
• libraries/base/src/Data/Bifoldable1.hs
• libraries/base/src/Data/Bifunctor.hs
• libraries/base/src/Data/Bool.hs
• libraries/base/src/Data/Char.hs
• libraries/base/src/Data/Data.hs
• + libraries/base/src/Data/Double.hs
• libraries/base/src/Data/Eq.hs
• libraries/base/src/Data/Fixed.hs
• + libraries/base/src/Data/Float.hs
• libraries/base/src/Data/Functor/Classes.hs
• libraries/base/src/Data/Functor/Compose.hs
• libraries/base/src/Data/Ix.hs
• libraries/base/src/Data/List.hs
• libraries/base/src/Data/List/NonEmpty.hs
• + libraries/base/src/Data/List/NubOrdSet.hs
• libraries/base/src/Data/Semigroup.hs
• libraries/base/src/Data/Version.hs
• libraries/base/src/GHC/Base.hs
• libraries/base/src/GHC/ByteOrder.hs
• libraries/base/src/GHC/Conc.hs
• libraries/base/src/GHC/Conc/Sync.hs
• − libraries/base/src/GHC/Desugar.hs
• libraries/base/src/GHC/Exts.hs
• libraries/base/src/GHC/Fingerprint.hs
• libraries/base/src/GHC/Generics.hs
• libraries/base/src/GHC/IO/Handle.hs
• − libraries/base/src/GHC/IOPort.hs
• − libraries/base/src/GHC/JS/Prim/Internal/Build.hs
• libraries/base/src/GHC/Num.hs
• − libraries/base/src/GHC/Num/BigNat.hs
• − libraries/base/src/GHC/Num/Integer.hs
• − libraries/base/src/GHC/Num/Natural.hs
• libraries/base/src/GHC/RTS/Flags.hs
• libraries/base/src/GHC/ResponseFile.hs
• libraries/base/src/GHC/Stack.hs
• libraries/base/src/GHC/Stack/CloneStack.hs
• libraries/base/src/GHC/Stats.hs
• libraries/base/src/GHC/Unicode.hs
• libraries/base/src/GHC/Weak.hs
• libraries/base/src/GHC/Weak/Finalize.hs
• libraries/base/src/Numeric.hs
• libraries/base/src/Prelude.hs
• libraries/base/src/System/CPUTime/Utils.hs
• libraries/base/src/System/Console/GetOpt.hs
• libraries/base/src/System/Environment.hs
• libraries/base/src/System/Exit.hs
• libraries/base/src/System/IO.hs
• + libraries/base/src/System/IO/OS.hs
• libraries/base/src/System/Info.hs
• libraries/base/src/System/Mem/Weak.hs
• libraries/base/src/System/Timeout.hs
• libraries/base/src/Text/Printf.hs
• libraries/base/src/Text/Read.hs
• libraries/base/tests/IO/T12010/cbits/initWinSock.c
• libraries/base/tests/IO/T17912.hs
• libraries/base/tests/IO/T18832.hs
• libraries/base/tests/IO/all.T
• + libraries/base/tests/IO/osHandles001FileDescriptors.hs
• + libraries/base/tests/IO/osHandles001FileDescriptors.stdout
• + libraries/base/tests/IO/osHandles001WindowsHandles.hs
• + libraries/base/tests/IO/osHandles001WindowsHandles.stdout
• + libraries/base/tests/IO/osHandles002FileDescriptors.hs
• + libraries/base/tests/IO/osHandles002FileDescriptors.stderr
• + libraries/base/tests/IO/osHandles002FileDescriptors.stdin
• + libraries/base/tests/IO/osHandles002FileDescriptors.stdout
• + libraries/base/tests/IO/osHandles002WindowsHandles.hs
• + libraries/base/tests/IO/osHandles002WindowsHandles.stderr
• + libraries/base/tests/IO/osHandles002WindowsHandles.stdin
• + libraries/base/tests/IO/osHandles002WindowsHandles.stdout
• libraries/base/tests/T15349.stderr
• libraries/base/tests/T23454.stderr
• libraries/base/tests/all.T
• libraries/base/tests/enum01.stdout
• libraries/base/tests/enum01.stdout-alpha-dec-osf3
• libraries/base/tests/enum01.stdout-ws-64
• + libraries/base/tests/perf/ElemFusionUnknownList.hs
• + libraries/base/tests/perf/ElemFusionUnknownList_O1.stderr
• + libraries/base/tests/perf/ElemFusionUnknownList_O2.stderr
• + libraries/base/tests/perf/ElemNoFusion.hs
• + libraries/base/tests/perf/ElemNoFusion_O1.stderr
• + libraries/base/tests/perf/ElemNoFusion_O2.stderr
• libraries/base/tests/perf/T17752.hs
• − libraries/base/tests/perf/T17752.stdout
• + libraries/base/tests/perf/T17752_O1.stderr
• + libraries/base/tests/perf/T17752_O2.stderr
• libraries/base/tests/perf/all.T
• libraries/base/tests/unicode002.stdout
• libraries/base/tests/unicode003.stdout
• libraries/binary
• libraries/deepseq
• libraries/directory
• libraries/exceptions
• libraries/file-io
• libraries/filepath
• libraries/ghc-bignum/changelog.md
• libraries/ghc-bignum/ghc-bignum.cabal
• + 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/Quote.hs
• libraries/ghc-boot-th/ghc-boot-th.cabal.in
• + libraries/ghc-boot/GHC/Data/ShortByteString.hs
• libraries/ghc-boot/GHC/Data/ShortText.hs
• libraries/ghc-boot/GHC/Data/SizedSeq.hs
• compiler/GHC/Data/SmallArray.hs → libraries/ghc-boot/GHC/Data/SmallArray.hs
• libraries/ghc-boot/GHC/Settings/Utils.hs
• libraries/ghc-boot/GHC/Unit/Database.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-compact/tests/all.T
• libraries/ghc-experimental/CHANGELOG.md
• libraries/ghc-experimental/ghc-experimental.cabal.in
• libraries/ghc-experimental/src/Data/Sum/Experimental.hs
• libraries/ghc-experimental/src/Data/Tuple/Experimental.hs
• + libraries/ghc-experimental/src/GHC/Exception/Backtrace/Experimental.hs
• libraries/ghc-experimental/src/GHC/PrimOps.hs
• libraries/ghc-experimental/src/GHC/Profiling/Eras.hs
• + libraries/ghc-experimental/src/GHC/Stack/Annotation/Experimental.hs
• + libraries/ghc-experimental/src/GHC/Stack/Decode/Experimental.hs
• libraries/ghc-experimental/src/GHC/TypeNats/Experimental.hs
• + libraries/ghc-experimental/src/System/Mem/Experimental.hs
• + libraries/ghc-experimental/tests/Makefile
• libraries/base/src/GHC/Weak/Finalizehs → libraries/ghc-experimental/tests/all.T
• libraries/base/tests/perf/Makefile → libraries/ghc-experimental/tests/backtraces/Makefile
• + libraries/ghc-experimental/tests/backtraces/T26806a.hs
• + libraries/ghc-experimental/tests/backtraces/T26806a.stderr
• + libraries/ghc-experimental/tests/backtraces/T26806b.hs
• + libraries/ghc-experimental/tests/backtraces/T26806b.stderr
• + libraries/ghc-experimental/tests/backtraces/T26806c.hs
• + libraries/ghc-experimental/tests/backtraces/T26806c.stderr
• + libraries/ghc-experimental/tests/backtraces/all.T
• 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/T27465.hs
• + libraries/ghc-heap/tests/T27465.stdout
• libraries/ghc-heap/tests/all.T
• libraries/ghc-heap/tests/parse_tso_flags.hs
• libraries/ghc-heap/tests/tso_and_stack_closures.hs
• libraries/ghc-internal/CHANGELOG.md
• libraries/ghc-internal/bignum-backend.rst
• 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/cbits/atomic.c
• libraries/ghc-internal/cbits/consUtils.c
• − libraries/ghc-internal/cbits/mulIntMayOflo.c
• libraries/ghc-internal/codepages/MakeTable.hs
• libraries/ghc-internal/codepages/Makefile
• libraries/ghc-internal/configure.ac
• libraries/ghc-internal/ghc-internal.buildinfo.in
• libraries/ghc-internal/ghc-internal.cabal.in
• libraries/ghc-internal/include/CTypes.h
• libraries/ghc-internal/include/HsIntegerGmp.h.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/Arr.hs
• libraries/ghc-internal/src/GHC/Internal/Base.hs
• libraries/ghc-internal/src/GHC/Internal/Bignum/Backend.hs
• − libraries/ghc-internal/src/GHC/Internal/Bignum/Backend/Check.hs
• − libraries/ghc-internal/src/GHC/Internal/Bignum/Backend/FFI.hs
• libraries/ghc-internal/src/GHC/Internal/Bignum/Backend/Native.hs
• − libraries/ghc-internal/src/GHC/Internal/Bignum/Backend/Selected.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/Bits.hs
• libraries/ghc-internal/src/GHC/Internal/ByteOrder.hs
• − libraries/ghc-internal/src/GHC/Internal/ByteOrder.hs-boot
• libraries/ghc-internal/src/GHC/Internal/CString.hs
• libraries/ghc-internal/src/GHC/Internal/Char.hs
• libraries/ghc-internal/src/GHC/Internal/Classes.hs
• + libraries/ghc-internal/src/GHC/Internal/Classes/IP.hs
• libraries/ghc-internal/src/GHC/Internal/Clock.hsc
• libraries/ghc-internal/src/GHC/Internal/ClosureTypes.hs
• libraries/ghc-internal/src/GHC/Internal/Conc/Bound.hs
• libraries/ghc-internal/src/GHC/Internal/Conc/IO.hs
• libraries/ghc-internal/src/GHC/Internal/Conc/POSIX.hs
• libraries/ghc-internal/src/GHC/Internal/Conc/Signal.hs
• libraries/ghc-internal/src/GHC/Internal/Conc/Sync.hs
• − libraries/ghc-internal/src/GHC/Internal/Conc/Sync.hs-boot
• libraries/ghc-internal/src/GHC/Internal/Conc/Windows.hs
• libraries/ghc-internal/src/GHC/Internal/ConsoleHandler.hsc
• libraries/ghc-internal/src/GHC/Internal/Control/Arrow.hs
• libraries/ghc-internal/src/GHC/Internal/Control/Concurrent/MVar.hs
• libraries/ghc-internal/src/GHC/Internal/Control/Exception.hs
• libraries/ghc-internal/src/GHC/Internal/Control/Exception/Base.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/Control/Monad/Fix.hs
• libraries/ghc-internal/src/GHC/Internal/Control/Monad/IO/Class.hs
• libraries/ghc-internal/src/GHC/Internal/Control/Monad/ST/Imp.hs
• libraries/ghc-internal/src/GHC/Internal/Control/Monad/ST/Lazy/Imp.hs
• libraries/ghc-internal/src/GHC/Internal/Data/Bits.hs
• − libraries/ghc-internal/src/GHC/Internal/Data/Bool.hs
• libraries/ghc-internal/src/GHC/Internal/Data/Data.hs
• libraries/ghc-internal/src/GHC/Internal/Data/Dynamic.hs
• libraries/ghc-internal/src/GHC/Internal/Data/Either.hs
• − libraries/ghc-internal/src/GHC/Internal/Data/Eq.hs
• libraries/ghc-internal/src/GHC/Internal/Data/Foldable.hs
• libraries/ghc-internal/src/GHC/Internal/Data/Function.hs
• libraries/ghc-internal/src/GHC/Internal/Data/Functor/Const.hs
• libraries/ghc-internal/src/GHC/Internal/Data/Functor/Identity.hs
• libraries/ghc-internal/src/GHC/Internal/Data/Functor/Utils.hs
• libraries/ghc-internal/src/GHC/Internal/Data/IORef.hs
• − libraries/ghc-internal/src/GHC/Internal/Data/Ix.hs
• libraries/ghc-internal/src/GHC/Internal/Data/List.hs
• libraries/ghc-internal/src/GHC/Internal/Data/Maybe.hs
• libraries/ghc-internal/src/GHC/Internal/Data/Monoid.hs
• libraries/ghc-internal/src/GHC/Internal/Data/OldList.hs
• libraries/ghc-internal/src/GHC/Internal/Data/Ord.hs
• libraries/ghc-internal/src/GHC/Internal/Data/Proxy.hs
• libraries/ghc-internal/src/GHC/Internal/Data/STRef.hs
• libraries/ghc-internal/src/GHC/Internal/Data/Semigroup/Internal.hs
• libraries/ghc-internal/src/GHC/Internal/Data/String.hs
• libraries/ghc-internal/src/GHC/Internal/Data/Traversable.hs
• libraries/ghc-internal/src/GHC/Internal/Data/Type/Bool.hs
• libraries/ghc-internal/src/GHC/Internal/Data/Type/Coercion.hs
• libraries/ghc-internal/src/GHC/Internal/Data/Type/Equality.hs
• libraries/ghc-internal/src/GHC/Internal/Data/Type/Ord.hs
• libraries/ghc-internal/src/GHC/Internal/Data/Typeable.hs
• libraries/ghc-internal/src/GHC/Internal/Data/Typeable/Internal.hs
• libraries/ghc-internal/src/GHC/Internal/Data/Unique.hs
• libraries/ghc-internal/src/GHC/Internal/Data/Version.hs
• − libraries/ghc-internal/src/GHC/Internal/Data/Version.hs-boot
• libraries/ghc-internal/src/GHC/Internal/Debug/Trace.hs
• libraries/ghc-internal/src/GHC/Internal/Debug/Trace.hs-boot
• libraries/ghc-internal/src/GHC/Internal/Encoding/UTF8.hs
• libraries/ghc-internal/src/GHC/Internal/Enum.hs
• libraries/ghc-internal/src/GHC/Internal/Environment.hs
• libraries/ghc-internal/src/GHC/Internal/Err.hs
• libraries/ghc-internal/src/GHC/Internal/Event/Array.hs
• libraries/ghc-internal/src/GHC/Internal/Event/Control.hs
• libraries/ghc-internal/src/GHC/Internal/Event/EPoll.hsc
• libraries/ghc-internal/src/GHC/Internal/Event/IntVar.hs
• libraries/ghc-internal/src/GHC/Internal/Event/Internal.hs
• libraries/ghc-internal/src/GHC/Internal/Event/Internal/Types.hs
• libraries/ghc-internal/src/GHC/Internal/Event/KQueue.hsc
• libraries/ghc-internal/src/GHC/Internal/Event/Manager.hs
• libraries/ghc-internal/src/GHC/Internal/Event/PSQ.hs
• libraries/ghc-internal/src/GHC/Internal/Event/Poll.hsc
• libraries/ghc-internal/src/GHC/Internal/Event/Thread.hs
• libraries/ghc-internal/src/GHC/Internal/Event/TimeOut.hs
• libraries/ghc-internal/src/GHC/Internal/Event/TimerManager.hs
• libraries/ghc-internal/src/GHC/Internal/Event/Unique.hs
• libraries/ghc-internal/src/GHC/Internal/Event/Windows.hsc
• libraries/ghc-internal/src/GHC/Internal/Event/Windows/Clock.hs
• libraries/ghc-internal/src/GHC/Internal/Event/Windows/ConsoleEvent.hsc
• libraries/ghc-internal/src/GHC/Internal/Event/Windows/FFI.hsc
• libraries/ghc-internal/src/GHC/Internal/Event/Windows/ManagedThreadPool.hs
• 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/Context.hs
• libraries/ghc-internal/src/GHC/Internal/Exception/Type.hs
• libraries/ghc-internal/src/GHC/Internal/ExecutionStack.hs
• libraries/ghc-internal/src/GHC/Internal/ExecutionStack/Internal.hsc
• libraries/ghc-internal/src/GHC/Internal/Exts.hs
• libraries/ghc-internal/src/GHC/Internal/Fingerprint.hs
• libraries/ghc-internal/src/GHC/Internal/Fingerprint.hs-boot
• libraries/ghc-internal/src/GHC/Internal/Fingerprint/Type.hs
• libraries/ghc-internal/src/GHC/Internal/Float.hs
• libraries/ghc-internal/src/GHC/Internal/Float/ConversionUtils.hs
• libraries/ghc-internal/src/GHC/Internal/Float/RealFracMethods.hs
• libraries/ghc-internal/src/GHC/Internal/Foreign/C/ConstPtr.hs
• libraries/ghc-internal/src/GHC/Internal/Foreign/C/Error.hs
• libraries/ghc-internal/src/GHC/Internal/Foreign/C/String.hs
• libraries/ghc-internal/src/GHC/Internal/Foreign/C/String/Encoding.hs
• libraries/ghc-internal/src/GHC/Internal/Foreign/C/Types.hs
• libraries/ghc-internal/src/GHC/Internal/Foreign/ForeignPtr/Imp.hs
• libraries/ghc-internal/src/GHC/Internal/Foreign/Marshal/Alloc.hs
• libraries/ghc-internal/src/GHC/Internal/Foreign/Marshal/Array.hs
• libraries/ghc-internal/src/GHC/Internal/Foreign/Marshal/Error.hs
• libraries/ghc-internal/src/GHC/Internal/Foreign/Marshal/Pool.hs
• libraries/ghc-internal/src/GHC/Internal/Foreign/Marshal/Utils.hs
• libraries/ghc-internal/src/GHC/Internal/Foreign/Ptr.hs
• libraries/ghc-internal/src/GHC/Internal/Foreign/Storable.hs
• libraries/ghc-internal/src/GHC/Internal/ForeignPtr.hs
• libraries/ghc-internal/src/GHC/Internal/ForeignSrcLang.hs
• libraries/ghc-internal/src/GHC/Internal/Functor/ZipList.hs
• libraries/ghc-internal/src/GHC/Internal/GHCi.hs
• libraries/ghc-internal/src/GHC/Internal/GHCi/Helpers.hs
• libraries/ghc-internal/src/GHC/Internal/Generics.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
• libraries/ghc-internal/src/GHC/Internal/IO/Buffer.hs
• libraries/ghc-internal/src/GHC/Internal/IO/BufferedIO.hs
• libraries/ghc-internal/src/GHC/Internal/IO/Device.hs
• libraries/ghc-internal/src/GHC/Internal/IO/Encoding.hs
• libraries/ghc-internal/src/GHC/Internal/IO/Encoding/CodePage.hs
• libraries/ghc-internal/src/GHC/Internal/IO/Encoding/CodePage/API.hs
• libraries/ghc-internal/src/GHC/Internal/IO/Encoding/CodePage/Table.hs
• libraries/ghc-internal/src/GHC/Internal/IO/Encoding/Failure.hs
• libraries/ghc-internal/src/GHC/Internal/IO/Encoding/Iconv.hs
• libraries/ghc-internal/src/GHC/Internal/IO/Encoding/Latin1.hs
• libraries/ghc-internal/src/GHC/Internal/IO/Encoding/Types.hs
• libraries/ghc-internal/src/GHC/Internal/IO/Encoding/UTF16.hs
• libraries/ghc-internal/src/GHC/Internal/IO/Encoding/UTF32.hs
• libraries/ghc-internal/src/GHC/Internal/IO/Encoding/UTF8.hs
• libraries/ghc-internal/src/GHC/Internal/IO/Exception.hs
• libraries/ghc-internal/src/GHC/Internal/IO/Exception.hs-boot
• libraries/ghc-internal/src/GHC/Internal/IO/FD.hs
• libraries/ghc-internal/src/GHC/Internal/IO/Handle.hs
• libraries/ghc-internal/src/GHC/Internal/IO/Handle/FD.hs
• libraries/ghc-internal/src/GHC/Internal/IO/Handle/Internals.hs
• libraries/ghc-internal/src/GHC/Internal/IO/Handle/Lock.hs
• libraries/ghc-internal/src/GHC/Internal/IO/Handle/Lock/Flock.hsc
• libraries/ghc-internal/src/GHC/Internal/IO/Handle/Lock/LinuxOFD.hsc
• libraries/ghc-internal/src/GHC/Internal/IO/Handle/Lock/NoOp.hs
• libraries/ghc-internal/src/GHC/Internal/IO/Handle/Lock/Windows.hsc
• libraries/ghc-internal/src/GHC/Internal/IO/Handle/Text.hs
• − libraries/ghc-internal/src/GHC/Internal/IO/Handle/Text.hs-boot
• libraries/ghc-internal/src/GHC/Internal/IO/Handle/Types.hs
• libraries/ghc-internal/src/GHC/Internal/IO/Handle/Windows.hs
• libraries/ghc-internal/src/GHC/Internal/IO/IOMode.hs
• libraries/ghc-internal/src/GHC/Internal/IO/SubSystem.hs
• libraries/ghc-internal/src/GHC/Internal/IO/Unsafe.hs
• libraries/ghc-internal/src/GHC/Internal/IO/Windows/Encoding.hs
• libraries/ghc-internal/src/GHC/Internal/IO/Windows/Handle.hsc
• libraries/ghc-internal/src/GHC/Internal/IOArray.hs
• − libraries/ghc-internal/src/GHC/Internal/IOPort.hs
• libraries/ghc-internal/src/GHC/Internal/IORef.hs
• libraries/ghc-internal/src/GHC/Internal/InfoProv.hs
• libraries/ghc-internal/src/GHC/Internal/InfoProv/Types.hsc
• libraries/ghc-internal/src/GHC/Internal/Int.hs
• libraries/ghc-internal/src/GHC/Internal/IsList.hs
• libraries/ghc-internal/src/GHC/Internal/Ix.hs
• libraries/ghc-internal/src/GHC/Internal/JS/Foreign/Callback.hs
• libraries/ghc-internal/src/GHC/Internal/JS/Prim.hs
• libraries/ghc-internal/src/GHC/Internal/JS/Prim/Internal.hs
• libraries/ghc-internal/src/GHC/Internal/JS/Prim/Internal/Build.hs
• libraries/ghc-internal/src/GHC/Internal/LanguageExtensions.hs
• libraries/ghc-internal/src/GHC/Internal/Lexeme.hs
• libraries/ghc-internal/src/GHC/Internal/List.hs
• libraries/ghc-internal/src/GHC/Internal/MVar.hs
• libraries/ghc-internal/src/GHC/Internal/Magic.hs
• libraries/ghc-internal/src/GHC/Internal/Natural.hs
• libraries/ghc-internal/src/GHC/Internal/Num.hs
• libraries/ghc-internal/src/GHC/Internal/Numeric.hs
• libraries/ghc-internal/src/GHC/Internal/OverloadedLabels.hs
• libraries/ghc-internal/src/GHC/Internal/Pack.hs
• + libraries/ghc-internal/src/GHC/Internal/Prim.hs
• libraries/ghc-internal/src/GHC/Internal/Prim/PtrEq.hs
• libraries/ghc-internal/src/GHC/Internal/Profiling.hs
• libraries/ghc-internal/src/GHC/Internal/Ptr.hs
• libraries/ghc-internal/src/GHC/Internal/RTS/Flags.hsc
• libraries/ghc-internal/src/GHC/Internal/RTS/Flags/Test.hsc
• libraries/ghc-internal/src/GHC/Internal/Read.hs
• libraries/ghc-internal/src/GHC/Internal/Real.hs
• − libraries/ghc-internal/src/GHC/Internal/ResponseFile.hs
• libraries/ghc-internal/src/GHC/Internal/ST.hs
• + libraries/ghc-internal/src/GHC/Internal/STM.hs
• libraries/ghc-internal/src/GHC/Internal/STRef.hs
• libraries/ghc-internal/src/GHC/Internal/Show.hs
• libraries/ghc-internal/src/GHC/Internal/Stable.hs
• libraries/ghc-internal/src/GHC/Internal/StableName.hs
• libraries/ghc-internal/src/GHC/Internal/Stack.hs
• libraries/ghc-internal/src/GHC/Internal/Stack.hs-boot
• + libraries/ghc-internal/src/GHC/Internal/Stack/Annotation.hs
• libraries/ghc-internal/src/GHC/Internal/Stack/CCS.hsc
• 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/StaticPtr.hs
• libraries/ghc-internal/src/GHC/Internal/StaticPtr/Internal.hs
• libraries/ghc-internal/src/GHC/Internal/Stats.hsc
• libraries/ghc-internal/src/GHC/Internal/Storable.hs
• libraries/ghc-internal/src/GHC/Internal/System/Environment.hs
• libraries/ghc-internal/src/GHC/Internal/System/Environment/Blank.hsc
• libraries/ghc-internal/src/GHC/Internal/System/Environment/ExecutablePath.hsc
• − libraries/ghc-internal/src/GHC/Internal/System/Exit.hs
• libraries/ghc-internal/src/GHC/Internal/System/IO.hs
• libraries/ghc-internal/src/GHC/Internal/System/IO/Error.hs
• libraries/ghc-internal/src/GHC/Internal/System/Mem.hs
• libraries/ghc-internal/src/GHC/Internal/System/Posix/Internals.hs
• libraries/ghc-internal/src/GHC/Internal/System/Posix/Types.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/Text/ParserCombinators/ReadP.hs
• libraries/ghc-internal/src/GHC/Internal/Text/ParserCombinators/ReadPrec.hs
• − libraries/ghc-internal/src/GHC/Internal/Text/Read.hs
• libraries/ghc-internal/src/GHC/Internal/Text/Read/Lex.hs
• libraries/ghc-internal/src/GHC/Internal/TopHandler.hs
• libraries/ghc-internal/src/GHC/Internal/Tuple.hs
• libraries/ghc-internal/src/GHC/Internal/TypeError.hs
• libraries/ghc-internal/src/GHC/Internal/TypeLits.hs
• libraries/ghc-internal/src/GHC/Internal/TypeLits/Internal.hs
• libraries/ghc-internal/src/GHC/Internal/TypeNats.hs
• libraries/ghc-internal/src/GHC/Internal/TypeNats/Internal.hs
• libraries/ghc-internal/src/GHC/Internal/Types.hs
• libraries/ghc-internal/src/GHC/Internal/Unicode.hs
• libraries/ghc-internal/src/GHC/Internal/Unicode/Bits.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/src/GHC/Internal/Unsafe/Coerce.hs
• libraries/ghc-internal/src/GHC/Internal/Wasm/Prim/Conc.hs
• libraries/ghc-internal/src/GHC/Internal/Wasm/Prim/Conc/Internal.hs
• libraries/ghc-internal/src/GHC/Internal/Wasm/Prim/Exports.hs
• libraries/ghc-internal/src/GHC/Internal/Wasm/Prim/Flag.hs
• libraries/ghc-internal/src/GHC/Internal/Wasm/Prim/Imports.hs
• libraries/ghc-internal/src/GHC/Internal/Wasm/Prim/Types.hs
• libraries/ghc-internal/src/GHC/Internal/Weak.hs
• libraries/ghc-internal/src/GHC/Internal/Weak/Finalize.hs
• libraries/ghc-internal/src/GHC/Internal/Windows.hs
• libraries/ghc-internal/src/GHC/Internal/Word.hs
• + libraries/ghc-internal/tests/Makefile
• testsuite/tests/driver/OneShotTH.stdout-javascript-unknown-ghcjs → 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/T15395.hs
• + libraries/ghc-internal/tests/backtraces/T15395.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/tests/stack-annotation/ann_frame005.hs
• + libraries/ghc-internal/tests/stack-annotation/ann_frame005.stdout
• libraries/ghc-internal/tools/ucd2haskell/exe/UCD2Haskell/ModuleGenerators.hs
• libraries/ghc-internal/tools/ucd2haskell/ucd.sh
• libraries/ghc-internal/tools/ucd2haskell/ucd2haskell.cabal
• libraries/ghc-internal/tools/ucd2haskell/unicode_version
• libraries/ghc-platform/src/GHC/Platform/ArchOS.hs
• libraries/ghc-prim/changelog.md
• libraries/ghc-prim/ghc-prim.cabal
• − libraries/ghci/GHCi/BinaryArray.hs
• + libraries/ghci/GHCi/Coverage.hs
• libraries/ghci/GHCi/CreateBCO.hs
• + libraries/ghci/GHCi/Debugger.hs
• libraries/ghci/GHCi/Message.hs
• libraries/ghci/GHCi/ObjLink.hs
• libraries/ghci/GHCi/ResolvedBCO.hs
• libraries/ghci/GHCi/Run.hs
• libraries/ghci/GHCi/Server.hs
• libraries/ghci/GHCi/TH.hs
• libraries/ghci/ghci.cabal.in
• libraries/haskeline
• libraries/hpc
• + libraries/libffi-clib
• libraries/mtl
• 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/template-haskell/vendored-filepath/System/FilePath/Posix.hs
• libraries/template-haskell/vendored-filepath/System/FilePath/Windows.hs
• libraries/terminfo
• libraries/text
• libraries/time
• libraries/transformers
• libraries/unix
• libraries/xhtml
• linters/lint-codes/LintCodes/Coverage.hs
• linters/lint-codes/LintCodes/Static.hs
• − linters/lint-codes/Makefile
• − linters/lint-notes/Makefile
• linters/lint-whitespace/lint-whitespace.cabal
• llvm-passes
• llvm-targets
• − m4/find_ghc_bootstrap_prog.m4
• m4/find_ld.m4
• m4/find_llvm_prog.m4
• m4/find_python.m4
• m4/fp_check_pthreads.m4
• − m4/fp_check_timer_create.m4
• m4/fp_cmm_cpp_cmd_with_args.m4
• − m4/fp_copy_shellvar.m4
• m4/fp_find_libdw.m4
• m4/fp_find_nm.m4
• + m4/fp_linker_supports_verbatim.m4
• m4/fp_prog_cc_linker_target.m4
• − m4/fp_prog_ld_flag.m4
• − m4/fp_prog_sort.m4
• − m4/fp_set_cflags_c99.m4
• − m4/fp_settings.m4
• m4/fp_setup_project_version.m4
• m4/fp_setup_windows_toolchain.m4
• − m4/fp_visibility_hidden.m4
• m4/fptools_alex.m4
• m4/fptools_ghc_version.m4
• m4/fptools_happy.m4
• m4/fptools_set_c_ld_flags.m4
• m4/fptools_set_platform_vars.m4
• m4/ghc_select_file_extensions.m4
• m4/ghc_toolchain.m4
• m4/prep_target_file.m4
• + m4/subst_tooldir.m4
• mk/get-win32-tarballs.py
• mk/hsc2hs.in
• mk/system-cxx-std-lib-1.0.conf.in
• − mk/win32-tarballs.md5sum
• nofib
• packages
• rts/.gitignore
• + rts/.ubsan-suppressions
• + rts/AllocArray.c
• + rts/AllocArray.h
• rts/Apply.cmm
• rts/BeginPrivate.h
• + rts/BuiltinClosures.c
• + rts/BuiltinClosures.h
• rts/Capability.c
• rts/Capability.h
• rts/CloneStack.c
• rts/CloneStack.h
• rts/ClosureFlags.c
• + rts/ClosureTable.c
• + rts/ClosureTable.h
• rts/Compact.cmm
• rts/Continuation.c
• rts/ContinuationOps.cmm
• rts/Disassembler.c
• rts/EndPrivate.h
• rts/Exception.cmm
• rts/ExecPage.c
• rts/Hash.c
• rts/Heap.c
• rts/HeapStackCheck.cmm
• rts/Hpc.c
• rts/IOManager.c
• rts/IOManager.h
• rts/IOManagerInternals.h
• rts/IPE.c
• rts/Interpreter.c
• rts/Interpreter.h
• rts/Jumps.h
• rts/LdvProfile.c
• rts/Linker.c
• rts/LinkerInternals.h
• − rts/Makefile
• rts/ZeroSlop.c → rts/MarkSlop.c
• rts/Messages.c
• rts/Prelude.h
• rts/PrimOps.cmm
• rts/Printer.c
• rts/ProfHeap.c
• rts/Profiling.c
• rts/RaiseAsync.c
• rts/RaiseAsync.h
• 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/RtsSymbols.h
• + rts/RtsToHsIface.c
• rts/RtsUtils.c
• rts/STM.c
• rts/STM.h
• rts/Schedule.c
• rts/Schedule.h
• rts/Stats.c
• rts/StgCRun.c
• rts/StgMiscClosures.cmm
• rts/StgStartup.cmm
• rts/StgStdThunks.cmm
• rts/Task.c
• rts/Task.h
• rts/ThreadLabels.c
• rts/ThreadPaused.c
• rts/Threads.c
• rts/Threads.h
• rts/Ticker.h
• + rts/TimeoutQueue.c
• + rts/TimeoutQueue.h
• rts/Timer.c
• rts/Timer.h
• 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/Cmm.h
• − rts/include/Makefile
• 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/EventLogFormat.h
• rts/include/rts/EventLogWriter.h
• rts/include/rts/Flags.h
• rts/include/rts/IOInterface.h
• rts/include/rts/IPE.h
• rts/include/rts/Messages.h
• rts/include/rts/NonMoving.h
• rts/include/rts/OSThreads.h
• rts/include/rts/PosixSource.h
• + rts/include/rts/RtsToHsIface.h
• rts/include/rts/StableName.h
• rts/include/rts/StablePtr.h
• rts/include/rts/Threads.h
• rts/include/rts/Timer.h
• rts/include/rts/Types.h
• rts/include/rts/ghc_ffi.h
• rts/include/rts/prof/CCS.h
• rts/include/rts/storage/Block.h
• rts/include/rts/storage/ClosureMacros.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/include/stg/Ticky.h
• rts/include/stg/Types.h
• rts/js/arith.js
• rts/js/mem.js
• rts/js/profiling.js
• rts/linker/Elf.c
• rts/linker/InitFini.c
• rts/linker/LoadArchive.c
• rts/linker/MachO.c
• rts/linker/PEi386.c
• + rts/posix/FdWakeup.c
• + rts/posix/FdWakeup.h
• + rts/posix/MIO.c
• + rts/posix/MIO.h
• rts/posix/OSMem.c
• rts/posix/OSThreads.c
• + rts/posix/Poll.c
• + rts/posix/Poll.h
• rts/posix/Select.c
• rts/posix/Select.h
• rts/posix/Signals.c
• rts/posix/Signals.h
• rts/posix/Ticker.c
• + rts/posix/Timeout.c
• + rts/posix/Timeout.h
• − rts/posix/ticker/Pthread.c
• − rts/posix/ticker/Setitimer.c
• − rts/posix/ticker/TimerCreate.c
• − rts/posix/ticker/TimerFd.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
• + 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/Evac_thr.c → rts/sm/Evac_par.c
• rts/sm/GC.c
• rts/sm/GCTDecl.h
• rts/sm/GCThread.h
• rts/sm/MBlock.c
• 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/Scav_thr.c → rts/sm/Scav_par.c
• rts/sm/Storage.c
• rts/wasm/JSFFI.c
• rts/wasm/scheduler.cmm
• rts/win32/AsyncMIO.c
• rts/win32/AsyncMIO.h
• rts/win32/AsyncWinIO.c
• rts/win32/AsyncWinIO.h
• rts/win32/AwaitEvent.c
• rts/win32/AwaitEvent.h
• rts/win32/ConsoleHandler.h
• rts/win32/MIOManager.h
• rts/win32/OSThreads.c
• rts/win32/ThrIOManager.h
• rts/win32/Ticker.c
• rts/win32/WorkQueue.h
• − rts/win32/libHSffi.def
• − rts/win32/libHSghc-internal.def
• + rts/win32/libHSghc-internal.def.in
• − rts/win32/libHSghc-prim.def
• rts/win32/veh_excn.h
• testsuite/.gitignore
• testsuite/config/ghc
• + testsuite/driver/_elffile.py
• testsuite/driver/cpu_features.py
• testsuite/driver/junit.py
• − testsuite/driver/kill_extra_files.py
• testsuite/driver/perf_notes.py
• testsuite/driver/runtests.py
• testsuite/driver/testglobals.py
• testsuite/driver/testlib.py
• testsuite/driver/testutil.py
• testsuite/ghc-config/ghc-config.hs
• testsuite/mk/boilerplate.mk
• testsuite/mk/test.mk
• + testsuite/tests/MiniQuickCheck.hs
• testsuite/tests/ado/ado004.hs
• testsuite/tests/annotations/should_fail/annfail02.hs
• testsuite/tests/annotations/should_fail/annfail02.stderr
• testsuite/tests/annotations/should_fail/annfail03.stderr
• testsuite/tests/annotations/should_fail/annfail04.stderr
• testsuite/tests/annotations/should_fail/annfail06.stderr
• testsuite/tests/annotations/should_fail/annfail09.stderr
• testsuite/tests/annotations/should_run/all.T
• testsuite/tests/arityanal/should_compile/Arity01.stderr
• testsuite/tests/arityanal/should_compile/Arity05.stderr
• testsuite/tests/arityanal/should_compile/Arity08.stderr
• testsuite/tests/arityanal/should_compile/Arity11.stderr
• testsuite/tests/arityanal/should_compile/Arity14.stderr
• testsuite/tests/arityanal/should_compile/T21755.stderr
• testsuite/tests/arityanal/should_compile/all.T
• testsuite/tests/array/should_run/arr020.hs
• testsuite/tests/arrows/gadt/T17423.stderr
• testsuite/tests/arrows/should_compile/T21301.stderr
• testsuite/tests/backpack/cabal/bkpcabal08/bkpcabal08.stdout
• testsuite/tests/backpack/should_compile/T13149.bkp
• testsuite/tests/backpack/should_fail/T19244a.stderr
• testsuite/tests/backpack/should_fail/bkpfail11.stderr
• testsuite/tests/backpack/should_fail/bkpfail43.stderr
• + 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/T26640.hs
• + testsuite/tests/bytecode/T26640.script
• + testsuite/tests/bytecode/T26640.stdout
• + testsuite/tests/bytecode/T27001.hs
• + testsuite/tests/bytecode/T27001.stdout
• + testsuite/tests/bytecode/TLinkable/BCOTemplate.hs
• + testsuite/tests/bytecode/TLinkable/LinkableUsage01.stderr
• + testsuite/tests/bytecode/TLinkable/LinkableUsage02.stderr
• + testsuite/tests/bytecode/TLinkable/Makefile
• + testsuite/tests/bytecode/TLinkable/all.T
• + testsuite/tests/bytecode/TLinkable/genLinkables.sh
• + testsuite/tests/bytecode/TLinkable/linkable-space.hs
• + testsuite/tests/bytecode/TLinkable/linkable-space.stdout
• testsuite/tests/bytecode/all.T
• + testsuite/tests/bytecode/tuplestress/ByteCode.hs
• + testsuite/tests/bytecode/tuplestress/Common.hs-incl
• + testsuite/tests/bytecode/tuplestress/Obj.hs
• + testsuite/tests/bytecode/tuplestress/TupleStress.hs
• + testsuite/tests/bytecode/tuplestress/TupleStress.stdout
• + testsuite/tests/bytecode/tuplestress/all.T
• + testsuite/tests/cabal/Bytecode.hs
• + testsuite/tests/cabal/BytecodeForeign.c
• + testsuite/tests/cabal/BytecodeForeign.hs
• testsuite/tests/cabal/Makefile
• testsuite/tests/cabal/all.T
• + testsuite/tests/cabal/bytecode.pkg
• + testsuite/tests/cabal/bytecode.script
• + testsuite/tests/cabal/bytecode_foreign.pkg
• + testsuite/tests/cabal/bytecode_foreign.script
• testsuite/tests/cabal/ghcpkg03.stderr
• testsuite/tests/cabal/ghcpkg03.stderr-mingw32
• testsuite/tests/cabal/ghcpkg05.stderr
• testsuite/tests/cabal/ghcpkg05.stderr-mingw32
• + testsuite/tests/cabal/ghcpkg10.stdout
• + testsuite/tests/cabal/pkg_bytecode.stderr
• + testsuite/tests/cabal/pkg_bytecode.stdout
• + testsuite/tests/cabal/pkg_bytecode_foreign.stderr
• + testsuite/tests/cabal/pkg_bytecode_foreign.stdout
• + testsuite/tests/cabal/pkg_bytecode_with_gbc.stderr
• + testsuite/tests/cabal/pkg_bytecode_with_gbc.stdout
• + testsuite/tests/cabal/pkg_bytecode_with_o.stderr
• + testsuite/tests/cabal/pkg_bytecode_with_o.stdout
• + testsuite/tests/cmm/opt/T25664.hs
• + testsuite/tests/cmm/opt/T25664.stdout
• testsuite/tests/cmm/opt/all.T
• testsuite/tests/cmm/should_compile/all.T
• testsuite/tests/cmm/should_run/AtomicFetch.hs
• testsuite/tests/cmm/should_run/AtomicFetch_cmm.cmm
• + testsuite/tests/cmm/should_run/T27447.hs
• + testsuite/tests/cmm/should_run/T27447.stdout
• + testsuite/tests/cmm/should_run/T27447_cmm.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/T25177.stderr
• + testsuite/tests/codeGen/should_compile/T25650.hs
• + testsuite/tests/codeGen/should_compile/T25650.stdout-ws-32
• + testsuite/tests/codeGen/should_compile/T25650.stdout-ws-64
• testsuite/tests/codeGen/should_compile/all.T
• testsuite/tests/codeGen/should_compile/debug.stdout
• + testsuite/tests/codeGen/should_fail/T26958.hs
• testsuite/tests/codeGen/should_fail/all.T
• + testsuite/tests/codeGen/should_gen_asm/aarch64-shl-subword.asm
• + testsuite/tests/codeGen/should_gen_asm/aarch64-shl-subword.hs
• + testsuite/tests/codeGen/should_gen_asm/aarch64-sxth-mul2.asm
• + testsuite/tests/codeGen/should_gen_asm/aarch64-sxth-mul2.cmm
• + testsuite/tests/codeGen/should_gen_asm/aarch64-sxtw.asm
• + testsuite/tests/codeGen/should_gen_asm/aarch64-sxtw.cmm
• + testsuite/tests/codeGen/should_gen_asm/aarch64-ushr-subword.asm
• + testsuite/tests/codeGen/should_gen_asm/aarch64-ushr-subword.hs
• testsuite/tests/codeGen/should_gen_asm/all.T
• + testsuite/tests/codeGen/should_gen_asm/avx512-int64-minmax.asm
• + testsuite/tests/codeGen/should_gen_asm/avx512-int64-minmax.hs
• + testsuite/tests/codeGen/should_gen_asm/avx512-int64-mul.asm
• + testsuite/tests/codeGen/should_gen_asm/avx512-int64-mul.hs
• + testsuite/tests/codeGen/should_gen_asm/avx512-word64-minmax.asm
• + testsuite/tests/codeGen/should_gen_asm/avx512-word64-minmax.hs
• + 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/CgStaticPointers.hs
• testsuite/tests/codeGen/should_run/CgStaticPointersNoFullLazyness.hs
• testsuite/tests/codeGen/should_run/T13825-unit.hs
• testsuite/tests/codeGen/should_run/T16617.hs
• testsuite/tests/codeGen/should_run/T16617.stdout
• + testsuite/tests/codeGen/should_run/T21227.hs
• + testsuite/tests/codeGen/should_run/T21227.stdout
• testsuite/tests/codeGen/should_run/T23146/T23146_liftedeq.hs
• + testsuite/tests/codeGen/should_run/T23146/T25636.script
• + testsuite/tests/codeGen/should_run/T23146/T25636.stdout
• testsuite/tests/codeGen/should_run/T23146/all.T
• + testsuite/tests/codeGen/should_run/T24016.hs
• + testsuite/tests/codeGen/should_run/T24016.stdout
• + testsuite/tests/codeGen/should_run/T25636a/T25636a.script
• + testsuite/tests/codeGen/should_run/T25636a/T25636a.stdout
• + testsuite/tests/codeGen/should_run/T25636a/all.T
• + testsuite/tests/codeGen/should_run/T25636b/T25636b.script
• + testsuite/tests/codeGen/should_run/T25636b/T25636b.stdout
• + testsuite/tests/codeGen/should_run/T25636b/all.T
• + testsuite/tests/codeGen/should_run/T25636c/T25636c.script
• + testsuite/tests/codeGen/should_run/T25636c/T25636c.stdout
• + testsuite/tests/codeGen/should_run/T25636c/all.T
• + testsuite/tests/codeGen/should_run/T25636d/T25636d.script
• + testsuite/tests/codeGen/should_run/T25636d/T25636d.stdout
• + testsuite/tests/codeGen/should_run/T25636d/all.T
• + testsuite/tests/codeGen/should_run/T25636e/T25636e.script
• + testsuite/tests/codeGen/should_run/T25636e/T25636e.stdout
• + testsuite/tests/codeGen/should_run/T25636e/all.T
• + testsuite/tests/codeGen/should_run/T26537.hs
• + testsuite/tests/codeGen/should_run/T26537.stdout
• + testsuite/tests/codeGen/should_run/T27046.hs
• + testsuite/tests/codeGen/should_run/T27046_cmm.cmm
• + testsuite/tests/codeGen/should_run/T27072d.hs
• + testsuite/tests/codeGen/should_run/T27072d.stdout
• + testsuite/tests/codeGen/should_run/T27072d_c.c
• + testsuite/tests/codeGen/should_run/T27072d_check.c
• + testsuite/tests/codeGen/should_run/T27072w.hs
• + testsuite/tests/codeGen/should_run/T27072w.stdout
• + testsuite/tests/codeGen/should_run/T27072w_c.c
• + testsuite/tests/codeGen/should_run/T9811.hs
• + testsuite/tests/codeGen/should_run/T9811.stdout
• testsuite/tests/codeGen/should_run/Word2Float32.hs
• testsuite/tests/codeGen/should_run/Word2Float32.stdout
• testsuite/tests/codeGen/should_run/Word2Float64.hs
• testsuite/tests/codeGen/should_run/Word2Float64.stdout
• + testsuite/tests/codeGen/should_run/aarch64-subword-ops.hs
• + testsuite/tests/codeGen/should_run/aarch64-subword-ops.stdout
• + testsuite/tests/codeGen/should_run/aarch64-sxtw-cmm.cmm
• + testsuite/tests/codeGen/should_run/aarch64-sxtw-run.hs
• + testsuite/tests/codeGen/should_run/aarch64-sxtw-run.stdout
• + testsuite/tests/codeGen/should_run/aarch64-ushr-subword-run.hs
• + testsuite/tests/codeGen/should_run/aarch64-ushr-subword-run.stdout
• testsuite/tests/codeGen/should_run/all.T
• testsuite/tests/codeGen/should_run/cgrun025.stderr
• testsuite/tests/concurrent/prog001/all.T
• + testsuite/tests/concurrent/should_run/T26341.hs
• + testsuite/tests/concurrent/should_run/T26341.stdout
• + testsuite/tests/concurrent/should_run/T26341a.hs
• + testsuite/tests/concurrent/should_run/T26341a.stdout
• + testsuite/tests/concurrent/should_run/T26341b.hs
• + testsuite/tests/concurrent/should_run/T26341b.stdout
• + testsuite/tests/concurrent/should_run/T27105.hs
• testsuite/tests/concurrent/should_run/all.T
• testsuite/tests/core-to-stg/T14895.stderr
• testsuite/tests/core-to-stg/T19700.hs
• testsuite/tests/core-to-stg/T24124.stderr
• testsuite/tests/core-to-stg/T25284/Cls.hs
• + testsuite/tests/core-to-stg/T25924/B.hs
• + testsuite/tests/core-to-stg/T25924/Main.hs
• + testsuite/tests/core-to-stg/T25924/all.T
• + testsuite/tests/core-to-stg/T25924a.hs
• + testsuite/tests/core-to-stg/T25924a.stdout
• testsuite/tests/core-to-stg/all.T
• testsuite/tests/corelint/LintEtaExpand.stderr
• + testsuite/tests/corelint/T15907.hs
• + testsuite/tests/corelint/T15907A.hs
• testsuite/tests/corelint/T21115b.stderr
• + testsuite/tests/corelint/T27374.hs
• testsuite/tests/corelint/all.T
• testsuite/tests/count-deps/CountDepsAst.stdout
• testsuite/tests/count-deps/CountDepsParser.stdout
• testsuite/tests/cpranal/should_compile/T18174.stderr
• testsuite/tests/cpranal/should_compile/T18401.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/T13208.stdout
• testsuite/tests/deSugar/should_compile/T16615.stderr
• testsuite/tests/deSugar/should_compile/T2431.stderr
• + testsuite/tests/deSugar/should_compile/T25996.hs
• + testsuite/tests/deSugar/should_compile/T25996.stderr
• + testsuite/tests/deSugar/should_compile/T27383.hs
• testsuite/tests/deSugar/should_compile/all.T
• testsuite/tests/deSugar/should_fail/DsStrictFail.hs
• testsuite/tests/deSugar/should_fail/DsStrictFail.stderr
• testsuite/tests/deSugar/should_fail/all.T
• + testsuite/tests/deSugar/should_run/LazyFieldAnnotationsSemantics.hs
• + testsuite/tests/deSugar/should_run/LazyFieldAnnotationsSemantics.stdout
• testsuite/tests/deSugar/should_run/T20024.stderr
• testsuite/tests/deSugar/should_run/all.T
• testsuite/tests/deSugar/should_run/dsrun005.stderr
• testsuite/tests/deSugar/should_run/dsrun007.stderr
• testsuite/tests/deSugar/should_run/dsrun008.stderr
• + testsuite/tests/default/T25825.hs
• testsuite/tests/default/all.T
• testsuite/tests/default/default-fail05.stderr
• + testsuite/tests/dependent/should_fail/SelfDepCls.hs
• + testsuite/tests/dependent/should_fail/SelfDepCls.stderr
• testsuite/tests/dependent/should_fail/T11334b.stderr
• testsuite/tests/dependent/should_fail/T13135_simple.stderr
• + testsuite/tests/dependent/should_fail/T15588.hs
• + testsuite/tests/dependent/should_fail/T15588.stderr
• testsuite/tests/dependent/should_fail/T16326_Fail6.stderr
• testsuite/tests/dependent/should_fail/all.T
• testsuite/tests/deriving/should_compile/T14682.stderr
• testsuite/tests/deriving/should_compile/T15798b.hs
• testsuite/tests/deriving/should_compile/T15798c.hs
• testsuite/tests/deriving/should_compile/T15798c.stderr
• testsuite/tests/deriving/should_compile/T20815.hs
• testsuite/tests/deriving/should_compile/T24955a.hs
• testsuite/tests/deriving/should_compile/T24955a.stderr
• testsuite/tests/deriving/should_compile/T24955b.hs
• testsuite/tests/deriving/should_compile/T24955c.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/T10598_fail4.hs
• testsuite/tests/deriving/should_fail/T10598_fail4.stderr
• testsuite/tests/deriving/should_fail/T10598_fail5.hs
• testsuite/tests/deriving/should_fail/T10598_fail5.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/T4846.stderr
• testsuite/tests/deriving/should_fail/T5498.stderr
• testsuite/tests/deriving/should_fail/T6147.stderr
• testsuite/tests/deriving/should_fail/T7148.stderr
• testsuite/tests/deriving/should_fail/T7148a.stderr
• testsuite/tests/deriving/should_fail/T8984.stderr
• testsuite/tests/deriving/should_fail/deriving-via-fail.stderr
• testsuite/tests/deriving/should_fail/deriving-via-fail4.stderr
• testsuite/tests/deriving/should_fail/deriving-via-fail5.stderr
• testsuite/tests/deriving/should_run/T9576.stderr
• testsuite/tests/determinism/determ017/A.hs
• testsuite/tests/diagnostic-codes/codes.stdout
• testsuite/tests/dmdanal/should_compile/T13143.stderr
• testsuite/tests/dmdanal/should_compile/T16029.stdout
• testsuite/tests/dmdanal/should_compile/T18894.stderr
• testsuite/tests/dmdanal/should_compile/T18982.stderr
• testsuite/tests/dmdanal/should_compile/T23398.hs
• testsuite/tests/dmdanal/should_compile/T23398.stderr
• + testsuite/tests/dmdanal/should_compile/T27106.hs
• + testsuite/tests/dmdanal/should_compile/T27106.stderr
• testsuite/tests/dmdanal/should_compile/all.T
• + testsuite/tests/dmdanal/should_run/M1.hs
• + testsuite/tests/dmdanal/should_run/T26416.hs
• + testsuite/tests/dmdanal/should_run/T26416.stdout
• + testsuite/tests/dmdanal/should_run/T26748.hs
• + testsuite/tests/dmdanal/should_run/T26748.stdout
• testsuite/tests/dmdanal/should_run/all.T
• testsuite/tests/dmdanal/sigs/T21081.stderr
• testsuite/tests/dmdanal/sigs/T21119.stderr
• testsuite/tests/dmdanal/sigs/T21888.stderr
• testsuite/tests/dmdanal/sigs/T22241.hs
• testsuite/tests/driver/Makefile
• + testsuite/tests/driver/T10531/A.hs
• + testsuite/tests/driver/T10531/B.hs
• + testsuite/tests/driver/T10531/C.hs
• + testsuite/tests/driver/T10531/Makefile
• + testsuite/tests/driver/T10531/all.T
• testsuite/tests/driver/T11429c.stderr
• + testsuite/tests/driver/T13729/A/A.cabal
• + testsuite/tests/driver/T13729/A/Setup.hs
• + testsuite/tests/driver/T13729/A/TH.hs
• + testsuite/tests/driver/T13729/A/Types1.hs
• + testsuite/tests/driver/T13729/A/Types2.hs
• + testsuite/tests/driver/T13729/B/B.cabal
• + testsuite/tests/driver/T13729/B/Main.hs
• + testsuite/tests/driver/T13729/B/Setup.hs
• + testsuite/tests/driver/T13729/Makefile
• + testsuite/tests/driver/T13729/Setup.hs
• + testsuite/tests/driver/T13729/all.T
• testsuite/tests/driver/T16167.stderr
• − testsuite/tests/driver/T16167.stdout
• testsuite/tests/driver/T16318/Makefile
• testsuite/tests/driver/T18125/Makefile
• + testsuite/tests/driver/T18177.hs
• testsuite/tests/driver/T20030/test1/all.T
• testsuite/tests/driver/T20030/test2/all.T
• testsuite/tests/driver/T20030/test3/all.T
• testsuite/tests/driver/T20030/test4/all.T
• testsuite/tests/driver/T20030/test5/all.T
• testsuite/tests/driver/T20030/test6/all.T
• + testsuite/tests/driver/T2057/Makefile
• + testsuite/tests/driver/T2057/README.md
• + testsuite/tests/driver/T2057/T2057.stderr
• + testsuite/tests/driver/T2057/all.T
• + testsuite/tests/driver/T2057/app/Main.hs
• + testsuite/tests/driver/T2057/pkgA1/A.hs
• + testsuite/tests/driver/T2057/pkgA1/pkg.conf
• + testsuite/tests/driver/T2057/pkgA2/A.hs
• + testsuite/tests/driver/T2057/pkgA2/pkg.conf
• + testsuite/tests/driver/T2057/pkgB/B.hs
• + testsuite/tests/driver/T2057/pkgB/pkg.conf
• + testsuite/tests/driver/T20604/T20604.stdout-javascript-unknown-ghcjs
• testsuite/tests/driver/T20604/all.T
• + testsuite/tests/driver/T20696/T20696.stderr-ext-interp
• testsuite/tests/driver/T21682.stderr
• + testsuite/tests/driver/T24120.hs
• + testsuite/tests/driver/T26423/Hello.hs
• + testsuite/tests/driver/T26423/Makefile
• + testsuite/tests/driver/T26423/T26423.hs
• + testsuite/tests/driver/T26423/T26423.stderr
• + testsuite/tests/driver/T26423/T26423.stdout
• + testsuite/tests/driver/T26423/all.T
• + testsuite/tests/driver/T26423/test/Test.hs
• + testsuite/tests/driver/T26423/test/test.pkg
• + testsuite/tests/driver/T26435.ghc.stderr
• + testsuite/tests/driver/T26435.hs
• + testsuite/tests/driver/T26435.stdout
• + testsuite/tests/driver/T26551.hs
• + testsuite/tests/driver/T26551.stderr
• + testsuite/tests/driver/T27370/Makefile
• + testsuite/tests/driver/T27370/T27370.hs
• + testsuite/tests/driver/T27370/T27370.pp
• + testsuite/tests/driver/T27370/T27370.stderr
• + testsuite/tests/driver/T27370/all.T
• testsuite/tests/driver/T4437.hs
• testsuite/tests/driver/T5313.hs
• testsuite/tests/driver/T8526/T8526.script
• + testsuite/tests/driver/TUnitInfo/Foo.hs
• + testsuite/tests/driver/TUnitInfo/Makefile
• + testsuite/tests/driver/TUnitInfo/all.T
• + testsuite/tests/driver/TUnitInfo/genMhu.sh
• + testsuite/tests/driver/TUnitInfo/generic-unit-info-space-mhu.stdout
• + testsuite/tests/driver/TUnitInfo/generic-unit-info-space-single.stdout
• + testsuite/tests/driver/TUnitInfo/generic-unit-info-space.hs
• + testsuite/tests/driver/TUnitInfo/generic-unit-info-space.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_object20.stdout
• + testsuite/tests/driver/bytecode-object/bytecode_object21.stderr
• + testsuite/tests/driver/bytecode-object/bytecode_object21.stdout
• + testsuite/tests/driver/bytecode-object/bytecode_object23.stdout
• + testsuite/tests/driver/bytecode-object/bytecode_object24.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/dynamicToo/dynamicToo001/Makefile
• testsuite/tests/driver/fat-iface/T22405/T22405.stdout
• testsuite/tests/driver/fat-iface/T22405/T22405b.stdout
• testsuite/tests/driver/fat-iface/fat010.stdout-javascript-unknown-ghcjs
• testsuite/tests/driver/fat-iface/fat011.stderr
• + testsuite/tests/driver/fat-iface/fat012.stderr-ext-interp
• testsuite/tests/driver/fat-iface/fat014.script
• testsuite/tests/driver/fat-iface/fat014.stdout
• + testsuite/tests/driver/fat-iface/fat015.stderr-ext-interp
• + testsuite/tests/driver/fully-static/Hello.hs
• + testsuite/tests/driver/fully-static/Makefile
• + testsuite/tests/driver/fully-static/all.T
• + testsuite/tests/driver/fully-static/fully-static.stdout
• + testsuite/tests/driver/fully-static/test/Test.hs
• + testsuite/tests/driver/fully-static/test/test.pkg
• testsuite/tests/driver/implicit-dyn-too/Makefile
• testsuite/tests/driver/j-space/Makefile
• testsuite/tests/driver/j-space/all.T
• testsuite/tests/driver/j-space/genJspace
• testsuite/tests/driver/j-space/jspace.hs
• testsuite/tests/driver/json.stderr
• testsuite/tests/driver/json2.stderr
• − testsuite/tests/driver/json_dump.hs
• − testsuite/tests/driver/json_dump.stderr
• testsuite/tests/driver/json_warn.stderr
• testsuite/tests/driver/linkwhole/Main.hs
• + 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/mostly-static/Hello.hs
• + testsuite/tests/driver/mostly-static/Makefile
• + testsuite/tests/driver/mostly-static/all.T
• + testsuite/tests/driver/mostly-static/mostly-static.stdout
• + testsuite/tests/driver/mostly-static/test/test.c
• + testsuite/tests/driver/mostly-static/test/test.h
• + testsuite/tests/driver/mostly-static/test/test.pkg
• testsuite/tests/driver/multipleHomeUnits/all.T
• testsuite/tests/driver/multipleHomeUnits/multipleHomeUnits_recomp_th.stdout
• + testsuite/tests/driver/multipleHomeUnits/plugin01/all.T
• + testsuite/tests/driver/multipleHomeUnits/plugin01/appunit
• + testsuite/tests/driver/multipleHomeUnits/plugin01/p/MyPlugin.hs
• + testsuite/tests/driver/multipleHomeUnits/plugin01/pluginunit
• + testsuite/tests/driver/multipleHomeUnits/plugin01/q/App.hs
• + testsuite/tests/driver/multipleHomeUnits/plugin02/all.T
• + testsuite/tests/driver/multipleHomeUnits/plugin02/appunit
• + testsuite/tests/driver/multipleHomeUnits/plugin02/p/MyPlugin.hs
• + testsuite/tests/driver/multipleHomeUnits/plugin02/pluginunit
• + testsuite/tests/driver/multipleHomeUnits/plugin02/q/App.hs
• + testsuite/tests/driver/multipleHomeUnits/plugin02/r/RexLib.hs
• + testsuite/tests/driver/multipleHomeUnits/plugin02/reexportunit
• testsuite/tests/driver/options_ghc/Mod_fbyte_code.hs
• testsuite/tests/driver/options_ghc/all.T
• testsuite/tests/driver/options_ghc/options_ghc_fbyte-code.stderr
• testsuite/tests/driver/recomp011/all.T
• testsuite/tests/driver/recomp015/all.T
• + testsuite/tests/driver/recomp022/A1.hs
• + testsuite/tests/driver/recomp022/A2.hs
• + testsuite/tests/driver/recomp022/A3.hs
• + testsuite/tests/driver/recomp022/B.hs
• + testsuite/tests/driver/recomp022/C.hs
• + testsuite/tests/driver/recomp022/Makefile
• + testsuite/tests/driver/recomp022/all.T
• + testsuite/tests/driver/recomp022/recomp022a.stdout
• + testsuite/tests/driver/recomp022/recomp022b.stdout
• + testsuite/tests/driver/recomp26183/M.hs
• + testsuite/tests/driver/recomp26183/M2A.hs
• + testsuite/tests/driver/recomp26183/M2B.hs
• + testsuite/tests/driver/recomp26183/Makefile
• + testsuite/tests/driver/recomp26183/all.T
• + testsuite/tests/driver/recomp26183/recomp26183.stderr
• + testsuite/tests/driver/recomp26705/M.hs
• + testsuite/tests/driver/recomp26705/M2A.hs
• + testsuite/tests/driver/recomp26705/M2B.hs
• + testsuite/tests/driver/recomp26705/Makefile
• + testsuite/tests/driver/recomp26705/all.T
• + testsuite/tests/driver/recomp26705/recomp26705.stderr
• testsuite/tests/driver/recompHash/recompHash.stdout-javascript-unknown-ghcjs
• testsuite/tests/driver/recompNoTH/recompNoTH.stdout-javascript-unknown-ghcjs
• − testsuite/tests/driver/th-new-test/th-new-test.stdout-javascript-unknown-ghcjs
• + testsuite/tests/exceptions/T26759.hs
• + testsuite/tests/exceptions/T26759.stderr
• + testsuite/tests/exceptions/T26759a.hs
• + testsuite/tests/exceptions/T26759a.stderr
• + testsuite/tests/exceptions/T26759a.stdout
• testsuite/tests/exceptions/all.T
• + testsuite/tests/ffi/should_compile/T26852.h
• + testsuite/tests/ffi/should_compile/T26852.hs
• + testsuite/tests/ffi/should_compile/T26852.stderr
• testsuite/tests/ffi/should_compile/all.T
• + testsuite/tests/ffi/should_run/PrimFFIUnboxedSum.hs
• + testsuite/tests/ffi/should_run/PrimFFIUnboxedSum.stdout
• + testsuite/tests/ffi/should_run/PrimFFIUnboxedSum_cmm.cmm
• 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/CasePrune.stderr
• testsuite/tests/gadt/T12468.stderr
• testsuite/tests/gadt/T20485.hs
• testsuite/tests/generics/GenDerivOutput.hs
• testsuite/tests/generics/GenDerivOutput1_0.hs
• testsuite/tests/generics/GenDerivOutput1_1.hs
• testsuite/tests/generics/T10604/T10604_deriving.hs
• testsuite/tests/generics/T10604/T10604_deriving.stderr
• testsuite/tests/generics/T10604/all.T
• + testsuite/tests/generics/T27245.hs
• + testsuite/tests/generics/T27245.stdout
• testsuite/tests/generics/all.T
• + 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/T24386.hs
• + testsuite/tests/ghc-api/T25121_status.hs
• + testsuite/tests/ghc-api/T25121_status.stdout
• + 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/T26910.hs
• + testsuite/tests/ghc-api/T26910.stdout
• + testsuite/tests/ghc-api/T26910_Input.hs
• + testsuite/tests/ghc-api/T27240.hs
• + testsuite/tests/ghc-api/T27273.hs
• testsuite/tests/ghc-api/T6145.hs
• testsuite/tests/ghc-api/T8639_api.hs
• + testsuite/tests/ghc-api/TypeMapStringLiteral.hs
• testsuite/tests/ghc-api/all.T
• testsuite/tests/ghc-api/annotations-literals/literals.hs
• testsuite/tests/ghc-api/annotations-literals/literals.stdout
• testsuite/tests/ghc-api/annotations-literals/parsed.hs
• testsuite/tests/ghc-api/apirecomp001/myghc.hs
• + testsuite/tests/ghc-api/downsweep/IncrementalDownsweep.hs
• + testsuite/tests/ghc-api/downsweep/IncrementalDownsweep.modules/A.hs
• + testsuite/tests/ghc-api/downsweep/IncrementalDownsweep.modules/B.hs
• + testsuite/tests/ghc-api/downsweep/IncrementalDownsweep.modules/C.hs
• + testsuite/tests/ghc-api/downsweep/IncrementalDownsweep.modules/D.hs
• + testsuite/tests/ghc-api/downsweep/IncrementalDownsweep.modules/X.hs
• + testsuite/tests/ghc-api/downsweep/IncrementalDownsweep.modules/Y.hs
• + testsuite/tests/ghc-api/downsweep/IncrementalDownsweep.modules/Z.hs
• + testsuite/tests/ghc-api/downsweep/IncrementalDownsweep.stdout
• testsuite/tests/ghc-api/downsweep/OldModLocation.hs
• testsuite/tests/ghc-api/downsweep/PartialDownsweep.hs
• testsuite/tests/ghc-api/downsweep/all.T
• testsuite/tests/ghc-api/exactprint/T22919.stderr
• testsuite/tests/ghc-api/exactprint/Test20239.stderr
• testsuite/tests/ghc-api/exactprint/ZeroWidthSemi.stderr
• testsuite/tests/ghc-api/fixed-nodes/FixedNodes.hs
• testsuite/tests/ghc-api/fixed-nodes/InterfaceModuleGraph.hs
• testsuite/tests/ghc-api/fixed-nodes/ModuleGraphInvariants.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-api/settings/LibDir.hs
• + testsuite/tests/ghc-api/settings/LibDir.stdout
• + testsuite/tests/ghc-api/settings/all.T
• testsuite/tests/ghc-e/should_fail/T18441fail5.stderr
• testsuite/tests/ghc-e/should_fail/T18441fail7.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/T26998.hs
• + 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/T8487.stdout
• testsuite/tests/ghci.debugger/scripts/all.T
• testsuite/tests/ghci.debugger/scripts/break011.stdout
• testsuite/tests/ghci.debugger/scripts/break012.hs
• testsuite/tests/ghci.debugger/scripts/break012.stdout
• testsuite/tests/ghci.debugger/scripts/break017.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/break025.stdout
• testsuite/tests/ghci.debugger/scripts/print012.stdout
• testsuite/tests/ghci.debugger/scripts/print034.stdout
• testsuite/tests/ghci/T13786/all.T
• testsuite/tests/ghci/T16793/T16793.stdout
• testsuite/tests/ghci/T18060/T18060.stdout
• + testsuite/tests/ghci/T27532/Makefile
• + testsuite/tests/ghci/T27532/T27532.stdout
• + testsuite/tests/ghci/T27532/T27532j4.stdout
• + testsuite/tests/ghci/T27532/a.script
• + testsuite/tests/ghci/T27532/all.T
• + testsuite/tests/ghci/T27532/b.script
• + testsuite/tests/ghci/T27532/genT27532Modules
• + testsuite/tests/ghci/T9074/Makefile
• + testsuite/tests/ghci/T9074/T9074.hs
• + testsuite/tests/ghci/T9074/T9074.stdout
• + testsuite/tests/ghci/T9074/T9074a.c
• + testsuite/tests/ghci/T9074/T9074b.c
• + testsuite/tests/ghci/T9074/all.T
• + testsuite/tests/ghci/custom-external-interpreter-commands/Main.hs
• + testsuite/tests/ghci/custom-external-interpreter-commands/all.T
• + testsuite/tests/ghci/custom-external-interpreter-commands/custom-external-interpreter-commands.stdout
• − testsuite/tests/ghci/linking/T11531.stderr
• testsuite/tests/ghci/linking/all.T
• testsuite/tests/ghci/linking/dyn/T3372.hs
• testsuite/tests/ghci/linking/dyn/all.T
• testsuite/tests/ghci/prog-mhu001/prog-mhu001c.stdout
• testsuite/tests/ghci/prog-mhu002/all.T
• testsuite/tests/ghci/prog-mhu002/prog-mhu002c.stdout
• testsuite/tests/ghci/prog-mhu003/prog-mhu003.stderr
• testsuite/tests/ghci/prog-mhu004/prog-mhu004a.stderr
• + 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/prog-mhu005b.script
• + testsuite/tests/ghci/prog-mhu005/prog-mhu005b.stdout
• + testsuite/tests/ghci/prog-mhu005/prog-mhu005c.script
• + testsuite/tests/ghci/prog-mhu005/prog-mhu005c.stderr
• + testsuite/tests/ghci/prog-mhu005/prog-mhu005c.stdout
• + testsuite/tests/ghci/prog-mhu005/prog-mhu005d.script
• + testsuite/tests/ghci/prog-mhu005/prog-mhu005d.stderr
• + testsuite/tests/ghci/prog-mhu005/prog-mhu005d.stdout
• + testsuite/tests/ghci/prog-mhu005/prog-mhu005e.script
• + testsuite/tests/ghci/prog-mhu005/prog-mhu005e.stderr
• + testsuite/tests/ghci/prog-mhu005/prog-mhu005e.stdout
• + testsuite/tests/ghci/prog-mhu005/prog-mhu005f.script
• + testsuite/tests/ghci/prog-mhu005/prog-mhu005f.stderr
• + testsuite/tests/ghci/prog-mhu005/prog-mhu005f.stdout
• + testsuite/tests/ghci/prog-mhu005/prog-mhu005g.script
• + testsuite/tests/ghci/prog-mhu005/prog-mhu005g.stderr
• + testsuite/tests/ghci/prog-mhu005/prog-mhu005g.stdout
• + testsuite/tests/ghci/prog-mhu005/unitA
• + testsuite/tests/ghci/prog-mhu005/unitB
• + testsuite/tests/ghci/prog-mhu006/Makefile
• + testsuite/tests/ghci/prog-mhu006/a/A.hs
• + testsuite/tests/ghci/prog-mhu006/all.T
• + testsuite/tests/ghci/prog-mhu006/b/B.hs
• + testsuite/tests/ghci/prog-mhu006/prog-mhu006a.script
• + testsuite/tests/ghci/prog-mhu006/prog-mhu006a.stdout
• + testsuite/tests/ghci/prog-mhu006/unitA
• + testsuite/tests/ghci/prog-mhu006/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.script
• testsuite/tests/ghci/prog018/prog018.stdout
• testsuite/tests/ghci/prog020/Makefile
• testsuite/tests/ghci/prog020/all.T
• testsuite/tests/ghci/prog020/ghci.prog020.script → testsuite/tests/ghci/prog020/ghci.prog020a.script
• testsuite/tests/ghci/prog020/ghci.prog020.stderr → testsuite/tests/ghci/prog020/ghci.prog020a.stderr
• testsuite/tests/ghci/prog020/ghci.prog020.stdout → testsuite/tests/ghci/prog020/ghci.prog020a.stdout
• + testsuite/tests/ghci/prog020/ghci.prog020b.script
• + testsuite/tests/ghci/prog020/ghci.prog020b.stderr
• + testsuite/tests/ghci/prog020/ghci.prog020b.stdout
• + testsuite/tests/ghci/prog021/A.hs
• + testsuite/tests/ghci/prog021/B.hs
• libraries/doc/Makefile → 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/prog022/ghci.prog022c.script
• + testsuite/tests/ghci/prog022/ghci.prog022c.stderr
• + testsuite/tests/ghci/prog022/ghci.prog022c.stdout
• + testsuite/tests/ghci/prog022/ghci.prog022d.script
• + testsuite/tests/ghci/prog022/ghci.prog022d.stderr
• + testsuite/tests/ghci/prog022/ghci.prog022d.stdout
• + testsuite/tests/ghci/prog022/ghci.prog022e.script
• + testsuite/tests/ghci/prog022/ghci.prog022e.stderr
• + testsuite/tests/ghci/prog022/ghci.prog022e.stdout
• + testsuite/tests/ghci/prog022/ghci.prog022f.script
• + testsuite/tests/ghci/prog022/ghci.prog022f.stderr
• + testsuite/tests/ghci/prog022/ghci.prog022f.stdout
• + testsuite/tests/ghci/prog023/Makefile
• + testsuite/tests/ghci/prog023/all.T
• + testsuite/tests/ghci/prog023/prog023a.script
• + testsuite/tests/ghci/prog023/prog023a.stdout
• + testsuite/tests/ghci/prog023/prog023b.script
• + testsuite/tests/ghci/prog023/prog023b.stdout
• + testsuite/tests/ghci/prog023/src/A.hs
• + testsuite/tests/ghci/prog024/Makefile
• + testsuite/tests/ghci/prog024/all.T
• + testsuite/tests/ghci/prog024/prog024a.script
• + testsuite/tests/ghci/prog024/prog024a.stdout
• + testsuite/tests/ghci/prog024/prog024b.script
• + testsuite/tests/ghci/prog024/prog024b.stdout
• + testsuite/tests/ghci/prog024/prog024c.script
• + testsuite/tests/ghci/prog024/prog024c.stderr
• + testsuite/tests/ghci/prog024/prog024c.stdout
• + testsuite/tests/ghci/prog024/prog024d.script
• + testsuite/tests/ghci/prog024/prog024d.stderr
• + testsuite/tests/ghci/prog024/prog024d.stdout
• + testsuite/tests/ghci/prog024/prog024e.script
• + testsuite/tests/ghci/prog024/prog024e.stdout
• + testsuite/tests/ghci/prog024/prog024f.script
• + testsuite/tests/ghci/prog024/prog024f.stdout
• + testsuite/tests/ghci/prog024/src/A.hs
• + testsuite/tests/ghci/prog024/src/B.hs
• + testsuite/tests/ghci/prog025/Makefile
• + testsuite/tests/ghci/prog025/a/A.hs
• + testsuite/tests/ghci/prog025/all.T
• + testsuite/tests/ghci/prog025/prog025a.script
• + testsuite/tests/ghci/prog025/prog025a.stdout
• + testsuite/tests/ghci/prog025/prog025b.script
• + testsuite/tests/ghci/prog025/prog025b.stdout
• + testsuite/tests/ghci/prog025/testpkg/Test.hs
• + testsuite/tests/ghci/prog025/testpkg/testpkg-0.1.0.0.pkg
• + testsuite/tests/ghci/prog025/testpkg/testpkg-0.2.0.0.pkg
• + testsuite/tests/ghci/prog025/unitA
• testsuite/tests/ghci/recompTHghci/all.T
• testsuite/tests/ghci/recompTHghci/recompTHghci.script
• testsuite/tests/ghci/scripts/Defer02.stderr
• testsuite/tests/ghci/scripts/ListTuplePunsPpr.stdout
• testsuite/tests/ghci/scripts/ListTuplePunsPprNoAbbrevTuple.stdout
• testsuite/tests/ghci/scripts/Makefile
• testsuite/tests/ghci/scripts/T10321.stdout
• testsuite/tests/ghci/scripts/T10963.stderr
• testsuite/tests/ghci/scripts/T12005.script
• testsuite/tests/ghci/scripts/T13869.script
• testsuite/tests/ghci/scripts/T13997.script
• testsuite/tests/ghci/scripts/T13997.stdout
• testsuite/tests/ghci/scripts/T15325.stderr
• testsuite/tests/ghci/scripts/T17669.script
• 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/T20150.stdout
• testsuite/tests/ghci/scripts/T20217.script
• testsuite/tests/ghci/scripts/T20217.stdout
• testsuite/tests/ghci/scripts/T20587.script
• testsuite/tests/ghci/scripts/T24459.stdout
• + testsuite/tests/ghci/scripts/T24632.hs
• + testsuite/tests/ghci/scripts/T24632.script
• + testsuite/tests/ghci/scripts/T24632.stdout
• + testsuite/tests/ghci/scripts/T26233.script
• + testsuite/tests/ghci/scripts/T26233.stderr
• + testsuite/tests/ghci/scripts/T26233.stdout
• testsuite/tests/ghci/scripts/T4175.stdout
• testsuite/tests/ghci/scripts/T6105.script
• 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.script
• testsuite/tests/ghci/scripts/T8042.stdout
• testsuite/tests/ghci/scripts/T8042recomp.script
• testsuite/tests/ghci/scripts/T8042recomp.stdout
• testsuite/tests/ghci/scripts/T8353.script
• testsuite/tests/ghci/scripts/T8353.stderr
• testsuite/tests/ghci/scripts/T8469.stdout
• testsuite/tests/ghci/scripts/T8535.stdout
• testsuite/tests/ghci/scripts/T8959b.stderr
• testsuite/tests/ghci/scripts/T9881.stdout
• testsuite/tests/ghci/scripts/all.T
• + testsuite/tests/ghci/scripts/bytecodeIPE.hs
• + testsuite/tests/ghci/scripts/bytecodeIPE.script
• + testsuite/tests/ghci/scripts/bytecodeIPE.stdout
• testsuite/tests/ghci/scripts/ghci020.stdout
• 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/ghci064.stdout
• testsuite/tests/ghci/scripts/ghci065.stdout
• − testsuite/tests/ghci/shell.hs
• testsuite/tests/ghci/should_run/BinaryArray.hs
• testsuite/tests/ghci/should_run/Makefile
• testsuite/tests/ghci/should_run/PackedDataCon/packeddatacon.T
• testsuite/tests/ghci/should_run/T10145.stdout
• testsuite/tests/ghci/should_run/T10920.stderr
• testsuite/tests/ghci/should_run/T18064.script
• testsuite/tests/ghci/should_run/T18594.stdout
• + testsuite/tests/ghci/should_run/T25636f.hs
• + testsuite/tests/ghci/should_run/T25636f.stdout
• + testsuite/tests/ghci/should_run/T27287.hs
• + testsuite/tests/ghci/should_run/T27287.stdout
• testsuite/tests/ghci/should_run/UnboxedTuples/unboxedtuples.T
• testsuite/tests/ghci/should_run/UnliftedDataTypeInterp/unlifteddatatypeinterp.T
• testsuite/tests/ghci/should_run/all.T
• testsuite/tests/ghci/should_run/tc-plugin-ghci/TcPluginGHCi.hs
• testsuite/tests/haddock/haddock_examples/haddock.Test.stderr
• 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/perf/Fold.hs
• 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/haddock/should_compile_flag_haddock/T24221.stderr
• testsuite/tests/haddock/should_compile_flag_haddock/haddockLinear.hs
• testsuite/tests/haddock/should_compile_flag_haddock/haddockLinear.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/T25709.hs
• testsuite/tests/hiefile/should_run/TestUtils.hs
• testsuite/tests/hiefile/should_run/all.T
• testsuite/tests/hpc/Makefile
• testsuite/tests/hpc/T17073.stdout → testsuite/tests/hpc/T17073a.stdout
• + testsuite/tests/hpc/T17073b.stdout
• testsuite/tests/hpc/T20568.stdout → testsuite/tests/hpc/T20568a.stdout
• + testsuite/tests/hpc/T20568b.stdout
• testsuite/tests/hpc/all.T
• testsuite/tests/hpc/fork/Makefile
• testsuite/tests/hpc/function/Makefile
• testsuite/tests/hpc/function/test.T
• + testsuite/tests/hpc/function/tough1.stderr
• + testsuite/tests/hpc/function/tough1.stdout
• testsuite/tests/hpc/function2/test.T
• + testsuite/tests/hpc/function2/tough3.script
• + testsuite/tests/hpc/ghc_ghci/BytecodeMain.hs
• testsuite/tests/hpc/ghc_ghci/Makefile
• + testsuite/tests/hpc/ghc_ghci/hpc_ghc_ghci_bytecode.stdout
• + testsuite/tests/hpc/ghc_ghci/hpc_ghci01.stdout
• + testsuite/tests/hpc/ghc_ghci/hpc_ghci02.stdout
• testsuite/tests/hpc/ghc_ghci/test.T
• + 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/Makefile
• + testsuite/tests/hpc/simple/hpc002.hs
• + testsuite/tests/hpc/simple/hpc002.stdout
• + testsuite/tests/hpc/simple/hpc003.hs
• + testsuite/tests/hpc/simple/hpc003.script
• + testsuite/tests/hpc/simple/hpc003.stdout
• testsuite/tests/hpc/simple/test.T
• testsuite/tests/impredicative/T17332.stderr
• testsuite/tests/indexed-types/should_compile/CEqCanOccursCheck.hs
• testsuite/tests/indexed-types/should_compile/PushedInAsGivens.stderr
• testsuite/tests/indexed-types/should_compile/T12538.stderr
• testsuite/tests/indexed-types/should_compile/T15322.hs
• testsuite/tests/indexed-types/should_compile/T15322.stderr
• testsuite/tests/indexed-types/should_compile/T2238.hs
• testsuite/tests/indexed-types/should_fail/T12522a.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/T7354.hs
• testsuite/tests/indexed-types/should_fail/T8518.stderr
• testsuite/tests/indexed-types/should_fail/T9580.stderr
• testsuite/tests/indexed-types/should_fail/T9662.stderr
• testsuite/tests/indexed-types/should_fail/all.T
• + testsuite/tests/interface-stability/.gitignore
• testsuite/tests/interface-stability/README.mkd
• 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/download-base-exports.sh
• testsuite/tests/interface-stability/ghc-bignum-exports.stdout
• 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/javascript/T24886.hs
• + testsuite/tests/javascript/T24886.stderr
• + testsuite/tests/javascript/T24886.stdout
• testsuite/tests/javascript/all.T
• testsuite/tests/javascript/closure/all.T
• + testsuite/tests/javascript/js-c-sources/T27033.hs
• + testsuite/tests/javascript/js-c-sources/T27033.stdout
• + testsuite/tests/javascript/js-c-sources/T27033_c.c
• + testsuite/tests/javascript/js-c-sources/T27033_js.js
• testsuite/tests/javascript/js-c-sources/all.T
• testsuite/tests/javascript/js-mk_tup.hs
• testsuite/tests/javascript/js-mk_tup.stdout
• testsuite/tests/jsffi/all.T
• + testsuite/tests/jsffi/bytearrayarg.hs
• + testsuite/tests/jsffi/bytearrayarg.mjs
• + testsuite/tests/jsffi/bytearrayarg.stdout
• testsuite/tests/layout/layout001.stdout
• testsuite/tests/layout/layout002.stdout
• testsuite/tests/layout/layout003.stdout
• testsuite/tests/layout/layout004.stdout
• testsuite/tests/layout/layout005.stdout
• testsuite/tests/layout/layout006.stdout
• testsuite/tests/layout/layout007.stdout
• testsuite/tests/layout/layout008.stdout
• testsuite/tests/layout/layout009.stdout
• + testsuite/tests/lib/stm/T26028.hs
• + testsuite/tests/lib/stm/T26028.stdout
• + testsuite/tests/lib/stm/T26291a.hs
• + testsuite/tests/lib/stm/T26291a.stdout
• + testsuite/tests/lib/stm/T26291b.hs
• + testsuite/tests/lib/stm/T26291b.stdout
• + testsuite/tests/lib/stm/all.T
• testsuite/tests/linear/should_compile/Linear1Rule.hs
• + testsuite/tests/linear/should_compile/LinearEtaExpansions.hs
• − testsuite/tests/linear/should_compile/LinearListComprehension.hs
• testsuite/tests/linear/should_compile/MultConstructor.hs
• testsuite/tests/linear/should_compile/NonLinearRecord.hs
• testsuite/tests/linear/should_compile/OldList.hs
• testsuite/tests/linear/should_compile/T1735Min.hs
• testsuite/tests/linear/should_compile/T19400.hs
• testsuite/tests/linear/should_compile/T22546.hs
• testsuite/tests/linear/should_compile/T23025.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/LinearErrOrigin.hs
• testsuite/tests/linear/should_fail/LinearErrOrigin.stderr
• testsuite/tests/linear/should_fail/LinearLet10.hs
• testsuite/tests/linear/should_fail/LinearLet10.stderr
• testsuite/tests/linear/should_fail/LinearLet7.stderr
• testsuite/tests/linear/should_fail/LinearPartialSig.hs
• testsuite/tests/linear/should_fail/LinearPartialSig.stderr
• testsuite/tests/linear/should_fail/LinearRole.hs
• testsuite/tests/linear/should_fail/LinearRole.stderr
• + testsuite/tests/linear/should_fail/LinearUnknownModifierKind.hs
• + testsuite/tests/linear/should_fail/LinearUnknownModifierKind.stderr
• testsuite/tests/linear/should_fail/LinearVar.hs
• testsuite/tests/linear/should_fail/LinearVar.stderr
• testsuite/tests/linear/should_fail/T18888.hs
• testsuite/tests/linear/should_fail/T18888_datakinds.hs
• testsuite/tests/linear/should_fail/T18888_datakinds.stderr
• testsuite/tests/linear/should_fail/T19361.hs
• testsuite/tests/linear/should_fail/T19361.stderr
• testsuite/tests/linear/should_fail/T20083.hs
• testsuite/tests/linear/should_fail/T20083.stderr
• testsuite/tests/linear/should_fail/T21278.hs
• testsuite/tests/linear/should_fail/T21278.stderr
• testsuite/tests/linear/should_fail/T25081.hs
• testsuite/tests/linear/should_fail/T25081.stderr
• + testsuite/tests/linear/should_fail/TooManyMultiplicities.hs
• + testsuite/tests/linear/should_fail/TooManyMultiplicities.stderr
• + testsuite/tests/linear/should_fail/TooManyMultiplicitiesU.hs
• + testsuite/tests/linear/should_fail/TooManyMultiplicitiesU.stderr
• testsuite/tests/linear/should_fail/TypeClass.hs
• testsuite/tests/linear/should_fail/TypeClass.stderr
• testsuite/tests/linear/should_fail/all.T
• 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/Makefile
• testsuite/tests/linters/all.T
• + testsuite/tests/linters/changelog-d.stdout
• testsuite/tests/linters/notes.stdout
• testsuite/tests/linters/regex-linters/check-rts-includes.py
• + 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/mdo/should_fail/mdofail006.stderr
• + testsuite/tests/modifiers/Makefile
• + testsuite/tests/modifiers/should_compile/LinearNoModifiers.hs
• + testsuite/tests/modifiers/should_compile/Makefile
• + testsuite/tests/modifiers/should_compile/Modifier1Linear.hs
• + testsuite/tests/modifiers/should_compile/Modifier1Linear.stderr
• + testsuite/tests/modifiers/should_compile/Modifiers.hs
• + testsuite/tests/modifiers/should_compile/Modifiers.stderr
• + testsuite/tests/modifiers/should_compile/ModifiersSuggestLinear.hs
• + testsuite/tests/modifiers/should_compile/ModifiersSuggestLinear.stderr
• + testsuite/tests/modifiers/should_compile/all.T
• + testsuite/tests/modifiers/should_fail/Makefile
• + testsuite/tests/modifiers/should_fail/ModifiersExprUnexpectedInQuote.hs
• + testsuite/tests/modifiers/should_fail/ModifiersExprUnexpectedInQuote.stderr
• + testsuite/tests/modifiers/should_fail/ModifiersForbiddenHere.hs
• + testsuite/tests/modifiers/should_fail/ModifiersForbiddenHere.stderr
• + testsuite/tests/modifiers/should_fail/ModifiersNoExt.hs
• + testsuite/tests/modifiers/should_fail/ModifiersNoExt.stderr
• + testsuite/tests/modifiers/should_fail/ModifiersUnexpectedInQuote.hs
• + testsuite/tests/modifiers/should_fail/ModifiersUnexpectedInQuote.stderr
• + testsuite/tests/modifiers/should_fail/ModifiersUnknownKind.hs
• + testsuite/tests/modifiers/should_fail/ModifiersUnknownKind.stderr
• + testsuite/tests/modifiers/should_fail/all.T
• testsuite/tests/module/T20007.hs
• testsuite/tests/module/T20007.stderr
• − testsuite/tests/module/T21752.stderr
• + testsuite/tests/module/T25901_exp_plain_wc.hs
• + testsuite/tests/module/T25901_exp_plain_wc.stderr
• + testsuite/tests/module/T25901_imp_plain_wc.hs
• + testsuite/tests/module/T25901_imp_plain_wc.stderr
• + testsuite/tests/module/T27380.hs
• + testsuite/tests/module/T27380.stderr
• testsuite/tests/module/all.T
• testsuite/tests/module/mod150.stderr
• testsuite/tests/module/mod151.stderr
• testsuite/tests/module/mod152.stderr
• testsuite/tests/module/mod153.stderr
• testsuite/tests/module/mod184.stderr
• testsuite/tests/module/mod185.stderr
• testsuite/tests/module/mod4.stderr
• + testsuite/tests/module/mod70b.hs
• + testsuite/tests/module/mod70b.stderr
• testsuite/tests/module/mod90.hs
• testsuite/tests/module/mod90.stderr
• testsuite/tests/monadfail/MonadFailErrors.stderr
• testsuite/tests/numeric/should_compile/T14170.stdout
• testsuite/tests/numeric/should_compile/T14465.stdout
• testsuite/tests/numeric/should_compile/T15547.stderr
• testsuite/tests/numeric/should_compile/T16402.stderr-ws-64
• testsuite/tests/numeric/should_compile/T20347.stderr
• testsuite/tests/numeric/should_compile/T20374.stderr
• testsuite/tests/numeric/should_compile/T20376.stderr
• testsuite/tests/numeric/should_compile/T23907.stderr
• + testsuite/tests/numeric/should_compile/T26229.hs
• testsuite/tests/numeric/should_compile/T7116.stdout
• 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/T21176.hs
• + testsuite/tests/numeric/should_run/T21176.stdout
• + testsuite/tests/numeric/should_run/T21176.stdout-ws-32
• + testsuite/tests/numeric/should_run/T26230.hs
• + testsuite/tests/numeric/should_run/T26230.stdout
• testsuite/tests/numeric/should_run/T7014.hs
• 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_compile/DRFPatSynExport.stdout
• + testsuite/tests/overloadedrecflds/should_compile/T26686.hs
• + testsuite/tests/overloadedrecflds/should_compile/T26686.stderr
• testsuite/tests/overloadedrecflds/should_compile/all.T
• testsuite/tests/overloadedrecflds/should_fail/DRFHoleFits.stderr
• testsuite/tests/overloadedrecflds/should_fail/NoFieldSelectorsFail.hs
• testsuite/tests/overloadedrecflds/should_fail/T16745.stderr
• testsuite/tests/overloadedrecflds/should_fail/T18999_NoDisambiguateRecordFields.hs
• 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/overloadedstrings/should_fail/T25926.hs
• + testsuite/tests/overloadedstrings/should_fail/T25926.stderr
• + testsuite/tests/overloadedstrings/should_fail/T27124.hs
• + testsuite/tests/overloadedstrings/should_fail/T27124.stderr
• + testsuite/tests/overloadedstrings/should_fail/all.T
• + testsuite/tests/overloadedstrings/should_run/T27124a.hs
• testsuite/tests/overloadedstrings/should_run/all.T
• + testsuite/tests/package/ImportReexport.hs
• + testsuite/tests/package/ImportReexport.stderr
• testsuite/tests/package/T20010/all.T
• testsuite/tests/package/all.T
• testsuite/tests/parser/should_compile/DumpParsedAst.stderr
• testsuite/tests/parser/should_compile/DumpParsedAstComments.stderr
• testsuite/tests/parser/should_compile/DumpRenamedAst.stderr
• testsuite/tests/parser/should_compile/DumpSemis.stderr
• testsuite/tests/parser/should_compile/DumpTypecheckedAst.stderr
• testsuite/tests/parser/should_compile/KindSigs.stderr
• testsuite/tests/parser/should_compile/ListTuplePunsSuccess1.hs
• + testsuite/tests/parser/should_compile/T12002.hs
• + testsuite/tests/parser/should_compile/T12002.stderr
• + testsuite/tests/parser/should_compile/T13087.stderr
• testsuite/tests/parser/should_compile/T14189.stderr
• testsuite/tests/parser/should_compile/T15279.stderr
• testsuite/tests/parser/should_compile/T15323.stderr
• testsuite/tests/parser/should_compile/T18834a.stderr
• testsuite/tests/parser/should_compile/T19082.stderr
• testsuite/tests/parser/should_compile/T20452.stderr
• testsuite/tests/parser/should_compile/T20718.stderr
• testsuite/tests/parser/should_compile/T20718b.stderr
• testsuite/tests/parser/should_compile/T20846.stderr
• testsuite/tests/parser/should_compile/T23315/T23315.stderr
• testsuite/tests/parser/should_compile/all.T
• + testsuite/tests/parser/should_fail/ListTuplePunsFail6.hs
• + testsuite/tests/parser/should_fail/ListTuplePunsFail6.stderr
• + testsuite/tests/parser/should_fail/NoBlockArgumentsFail4.hs
• + testsuite/tests/parser/should_fail/NoBlockArgumentsFail4.stderr
• testsuite/tests/parser/should_fail/NoBlockArgumentsFailArrowCmds.hs
• testsuite/tests/parser/should_fail/NoBlockArgumentsFailArrowCmds.stderr
• + testsuite/tests/parser/should_fail/NoDoAndIfThenElseArrowCmds.hs
• + testsuite/tests/parser/should_fail/NoDoAndIfThenElseArrowCmds.stderr
• testsuite/tests/parser/should_fail/ParserNoLambdaCase.hs
• testsuite/tests/parser/should_fail/ParserNoLambdaCase.stderr
• 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/RecordDotSyntaxFail9.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.hs
• testsuite/tests/parser/should_fail/T16270h.stderr
• testsuite/tests/parser/should_fail/T17865.stderr
• testsuite/tests/parser/should_fail/T19928.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/T26860ppr.hs
• + testsuite/tests/parser/should_fail/T26860ppr.stderr
• + testsuite/tests/parser/should_fail/T26860ppr_overloaded.hs
• + testsuite/tests/parser/should_fail/T26860ppr_overloaded.stderr
• + testsuite/tests/parser/should_fail/T26860ppr_tylit.hs
• + testsuite/tests/parser/should_fail/T26860ppr_tylit.stderr
• testsuite/tests/parser/should_fail/T8431.stderr
• testsuite/tests/parser/should_fail/all.T
• + testsuite/tests/parser/should_fail/badRuleMarker.hs
• + testsuite/tests/parser/should_fail/badRuleMarker.stderr
• + testsuite/tests/parser/should_fail/patFail010.hs
• + testsuite/tests/parser/should_fail/patFail010.stderr
• + testsuite/tests/parser/should_fail/patFail011.hs
• + testsuite/tests/parser/should_fail/patFail011.stderr
• + testsuite/tests/parser/should_fail/precOutOfRange.hs
• + testsuite/tests/parser/should_fail/precOutOfRange.stderr
• testsuite/tests/parser/should_fail/readFail001.hs
• testsuite/tests/parser/should_fail/readFail001.stderr
• testsuite/tests/parser/should_fail/readFail038.stderr
• + testsuite/tests/parser/should_fail/unpack_data_con.hs
• + testsuite/tests/parser/should_fail/unpack_data_con.stderr
• testsuite/tests/parser/should_run/ListTuplePunsConstraints.hs
• + testsuite/tests/parser/should_run/StringStartsWithNull.hs
• + testsuite/tests/parser/should_run/StringStartsWithNull.stdout
• + 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/ExtraConstraints3.stderr
• testsuite/tests/partial-sigs/should_compile/SomethingShowable.hs
• testsuite/tests/partial-sigs/should_compile/SplicesUsed.stderr
• testsuite/tests/partial-sigs/should_compile/T10403.stderr
• + testsuite/tests/partial-sigs/should_compile/T11107.hs
• + testsuite/tests/partial-sigs/should_compile/T11107.stderr
• testsuite/tests/partial-sigs/should_compile/T12844.stderr
• testsuite/tests/partial-sigs/should_compile/T15039a.stderr
• testsuite/tests/partial-sigs/should_compile/T15039b.stderr
• testsuite/tests/partial-sigs/should_compile/T15039c.stderr
• testsuite/tests/partial-sigs/should_compile/T15039d.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/T12634.stderr
• testsuite/tests/partial-sigs/should_fail/T14584a.stderr
• + 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/all.T
• testsuite/tests/patsyn/should_fail/T10426.stderr
• + 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_fail/import-syntax-no-ext.hs
• + testsuite/tests/patsyn/should_fail/import-syntax-no-ext.stderr
• + testsuite/tests/patsyn/should_fail/patsyn_where_fail1.hs
• + testsuite/tests/patsyn/should_fail/patsyn_where_fail1.stderr
• + testsuite/tests/patsyn/should_fail/patsyn_where_fail2.hs
• + testsuite/tests/patsyn/should_fail/patsyn_where_fail2.stderr
• + testsuite/tests/patsyn/should_fail/patsyn_where_fail3.hs
• + testsuite/tests/patsyn/should_fail/patsyn_where_fail3.stderr
• + testsuite/tests/patsyn/should_fail/patsyn_where_fail4.hs
• + testsuite/tests/patsyn/should_fail/patsyn_where_fail4.stderr
• testsuite/tests/patsyn/should_run/ghci.stderr
• + testsuite/tests/perf/compiler/FamAppCachePerf.hs
• testsuite/tests/perf/compiler/Makefile
• testsuite/tests/perf/compiler/MultiLayerModulesDefsGhci.script
• + testsuite/tests/perf/compiler/MultiLayerModulesDefsGhciWithBytecodeFiles.script
• + testsuite/tests/perf/compiler/SimplCastPerf.hs
• testsuite/tests/perf/compiler/T11068.stdout
• + testsuite/tests/perf/compiler/T13820.hs
• + testsuite/tests/perf/compiler/T13960.hs
• + testsuite/tests/perf/compiler/T26425.hs
• + testsuite/tests/perf/compiler/T26426.hs
• + testsuite/tests/perf/compiler/T26989.hs
• + testsuite/tests/perf/compiler/T26989a.hs
• + testsuite/tests/perf/compiler/T27336.hs
• testsuite/tests/perf/compiler/T3064.hs
• testsuite/tests/perf/compiler/T4007.stdout
• testsuite/tests/perf/compiler/T9675.hs
• testsuite/tests/perf/compiler/all.T
• testsuite/tests/perf/compiler/genMultiComp.py
• testsuite/tests/perf/compiler/hard_hole_fits.stderr
• + 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/T11226.hs
• + testsuite/tests/perf/should_run/T11226.stdout
• + testsuite/tests/perf/should_run/T1216.hs
• + testsuite/tests/perf/should_run/T1216.stdout
• testsuite/tests/perf/should_run/T3586.hs
• testsuite/tests/perf/should_run/UniqLoop.hs
• testsuite/tests/perf/should_run/all.T
• testsuite/tests/perf/size/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/T23110.hs
• + testsuite/tests/plugins/T23110.script
• + testsuite/tests/plugins/T23110.stdout
• + testsuite/tests/plugins/T24486-plugin/Makefile
• + testsuite/tests/plugins/T24486-plugin/Setup.hs
• + testsuite/tests/plugins/T24486-plugin/T24486-plugin.cabal
• + testsuite/tests/plugins/T24486-plugin/T24486_Plugin.hs
• + testsuite/tests/plugins/T24486.hs
• + testsuite/tests/plugins/T24486_Helper.hs
• testsuite/tests/plugins/all.T
• testsuite/tests/plugins/annotation-plugin/SayAnnNames.hs
• testsuite/tests/plugins/defaulting-plugin/DefaultInterference.hs
• testsuite/tests/plugins/defaulting-plugin/DefaultInvalid.hs
• testsuite/tests/plugins/defaulting-plugin/DefaultLifted.hs
• testsuite/tests/plugins/defaulting-plugin/DefaultMultiParam.hs
• testsuite/tests/plugins/echo-plugin/Echo.hs
• testsuite/tests/plugins/late-plugin/LatePlugin.hs
• testsuite/tests/plugins/plugins09.stdout
• testsuite/tests/plugins/plugins10.stdout
• testsuite/tests/plugins/plugins11.stdout
• testsuite/tests/plugins/simple-plugin/Simple/ReplacePlugin.hs
• testsuite/tests/plugins/static-plugins.stdout
• testsuite/tests/plugins/test-defaulting-plugin.stderr
• testsuite/tests/plugins/test-hole-plugin.stderr
• testsuite/tests/pmcheck/should_compile/T11303.hs
• testsuite/tests/pmcheck/should_compile/T12957.stderr
• testsuite/tests/pmcheck/should_compile/T15753c.hs
• + testsuite/tests/pmcheck/should_compile/T15753c.stderr
• testsuite/tests/pmcheck/should_compile/T15753d.hs
• + testsuite/tests/pmcheck/should_compile/T15753d.stderr
• + testsuite/tests/pmcheck/should_compile/T22652.hs
• + testsuite/tests/pmcheck/should_compile/T22652a.hs
• + testsuite/tests/pmcheck/should_compile/T24867.hs
• + testsuite/tests/pmcheck/should_compile/T24867.stderr
• + 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/T27314.hs
• + testsuite/tests/pmcheck/should_compile/T27360.hs
• testsuite/tests/pmcheck/should_compile/all.T
• testsuite/tests/pmcheck/should_compile/pmcOrPats.stderr
• testsuite/tests/polykinds/T13393.stderr
• + testsuite/tests/polykinds/T13882.hs
• testsuite/tests/polykinds/T15789.stderr
• + testsuite/tests/polykinds/T18186.hs
• + testsuite/tests/polykinds/T18186.stderr
• testsuite/tests/polykinds/T18451.stderr
• testsuite/tests/polykinds/T6068.stdout
• testsuite/tests/polykinds/T7151.hs
• testsuite/tests/polykinds/T7151.stderr
• testsuite/tests/polykinds/T7328.stderr
• testsuite/tests/polykinds/T7433.hs
• testsuite/tests/polykinds/T7433.stderr
• testsuite/tests/polykinds/T7594.hs
• testsuite/tests/polykinds/all.T
• testsuite/tests/primops/should_run/UnliftedIOPort.hs
• testsuite/tests/primops/should_run/all.T
• testsuite/tests/printer/AnnotationNoListTuplePuns.stdout
• testsuite/tests/printer/Makefile
• + testsuite/tests/printer/PprInfixHole.hs
• + testsuite/tests/printer/PprModifiers.hs
• + testsuite/tests/printer/PprQualifiedStrings.hs
• testsuite/tests/printer/T17697.stderr
• testsuite/tests/printer/T18052a.stderr
• testsuite/tests/printer/T18791.stderr
• testsuite/tests/printer/Test10309.hs
• testsuite/tests/printer/Test20297.stdout
• testsuite/tests/printer/Test20315.hs
• testsuite/tests/printer/Test20315.stderr
• testsuite/tests/printer/Test24533.stdout
• + testsuite/tests/printer/Test27291.hs
• + testsuite/tests/printer/TestLevelImports.hs
• + testsuite/tests/printer/TestNamedDefaults.hs
• testsuite/tests/printer/all.T
• testsuite/tests/process/T3994.hs
• testsuite/tests/process/all.T
• − testsuite/tests/process/process010.stdout-i386-unknown-solaris2
• testsuite/tests/profiling/perf/T23103/all.T
• + testsuite/tests/profiling/should_compile/T26056.hs
• + testsuite/tests/profiling/should_compile/T27121.hs
• + testsuite/tests/profiling/should_compile/T27121_aux.hs
• + testsuite/tests/profiling/should_compile/T27182.hs
• + testsuite/tests/profiling/should_compile/T27386.hs
• testsuite/tests/profiling/should_compile/all.T
• + testsuite/tests/profiling/should_run/T27225.hs
• + testsuite/tests/profiling/should_run/T27225.stdout
• + testsuite/tests/profiling/should_run/T27225b.hs
• + testsuite/tests/profiling/should_run/T27225b.stdout
• testsuite/tests/profiling/should_run/all.T
• testsuite/tests/profiling/should_run/caller-cc/CallerCc1.prof.sample
• testsuite/tests/profiling/should_run/caller-cc/all.T
• testsuite/tests/profiling/should_run/callstack001.stdout
• testsuite/tests/profiling/should_run/callstack002.stderr
• testsuite/tests/profiling/should_run/callstack002.stdout
• testsuite/tests/profiling/should_run/scc001.prof.sample
• testsuite/tests/profiling/should_run/staticcallstack002.stdout
• testsuite/tests/programs/andy_cherry/test.T
• testsuite/tests/programs/thurston-modular-arith/Main.hs
• + testsuite/tests/qualified-strings/Makefile
• + testsuite/tests/qualified-strings/should_compile/Example/Length.hs
• + testsuite/tests/qualified-strings/should_compile/all.T
• + testsuite/tests/qualified-strings/should_compile/qstrings_redundant_pattern.hs
• + testsuite/tests/qualified-strings/should_compile/qstrings_redundant_pattern.stderr
• + testsuite/tests/qualified-strings/should_fail/Example/Length.hs
• + testsuite/tests/qualified-strings/should_fail/Makefile
• + testsuite/tests/qualified-strings/should_fail/all.T
• + testsuite/tests/qualified-strings/should_fail/qstrings_bad_expr.hs
• + testsuite/tests/qualified-strings/should_fail/qstrings_bad_expr.stderr
• + testsuite/tests/qualified-strings/should_fail/qstrings_bad_pat.hs
• + testsuite/tests/qualified-strings/should_fail/qstrings_bad_pat.stderr
• + testsuite/tests/qualified-strings/should_fail/qstrings_multiline_no_ext.hs
• + testsuite/tests/qualified-strings/should_fail/qstrings_multiline_no_ext.stderr
• + testsuite/tests/qualified-strings/should_run/Example/ByteStringAscii.hs
• + testsuite/tests/qualified-strings/should_run/Example/ByteStringUtf8.hs
• + testsuite/tests/qualified-strings/should_run/Example/Text.hs
• + testsuite/tests/qualified-strings/should_run/Makefile
• + testsuite/tests/qualified-strings/should_run/all.T
• + testsuite/tests/qualified-strings/should_run/qstrings_expr.hs
• + testsuite/tests/qualified-strings/should_run/qstrings_expr.stdout
• + testsuite/tests/qualified-strings/should_run/qstrings_pat.hs
• + testsuite/tests/qualified-strings/should_run/qstrings_pat.stdout
• + testsuite/tests/qualified-strings/should_run/qstrings_th.hs
• + testsuite/tests/qualified-strings/should_run/qstrings_th.stdout
• testsuite/tests/quantified-constraints/T15290a.stderr
• testsuite/tests/quantified-constraints/T15316A.stderr
• testsuite/tests/quantified-constraints/T15359.hs
• testsuite/tests/quantified-constraints/T17267.stderr
• testsuite/tests/quantified-constraints/T17267a.stderr
• testsuite/tests/quantified-constraints/T17267b.stderr
• testsuite/tests/quantified-constraints/T17267c.stderr
• testsuite/tests/quantified-constraints/T17267e.stderr
• testsuite/tests/quantified-constraints/T17458.stderr
• testsuite/tests/quantified-constraints/T19690.stderr
• testsuite/tests/quantified-constraints/T19921.stderr
• testsuite/tests/quantified-constraints/T21006.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/quasiquotation/qq005/test.T
• testsuite/tests/quasiquotation/qq006/test.T
• + 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.stderr
• testsuite/tests/quotes/T10384.stderr
• testsuite/tests/quotes/T5721.stderr
• testsuite/tests/quotes/TH_localname.stderr
• testsuite/tests/quotes/all.T
• + testsuite/tests/rebindable/T10381.hs
• testsuite/tests/rebindable/all.T
• testsuite/tests/rebindable/rebindable6.stderr
• 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/T1792_imports.stdout
• testsuite/tests/rename/should_compile/T18264.stdout
• testsuite/tests/rename/should_compile/T22478a.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/T25901_exp_1.hs
• + testsuite/tests/rename/should_compile/T25901_exp_1_helper.hs
• + testsuite/tests/rename/should_compile/T25901_exp_2.hs
• + testsuite/tests/rename/should_compile/T25901_exp_2_helper.hs
• + testsuite/tests/rename/should_compile/T25901_imp_hq.hs
• + testsuite/tests/rename/should_compile/T25901_imp_hu.hs
• + testsuite/tests/rename/should_compile/T25901_imp_sq.hs
• + testsuite/tests/rename/should_compile/T25901_imp_su.hs
• + testsuite/tests/rename/should_compile/T25901_sub_e.hs
• + testsuite/tests/rename/should_compile/T25901_sub_f.hs
• + testsuite/tests/rename/should_compile/T25901_sub_f.stderr
• + testsuite/tests/rename/should_compile/T25901_sub_g.hs
• + testsuite/tests/rename/should_compile/T25901_sub_g.stderr
• + testsuite/tests/rename/should_compile/T25901_sub_g_helper.hs
• testsuite/tests/rename/should_compile/T4239.stdout
• testsuite/tests/rename/should_compile/all.T
• testsuite/tests/rename/should_compile/rn039.ghc.stderr
• testsuite/tests/rename/should_fail/RnStaticPointersFail01.stderr
• testsuite/tests/rename/should_fail/RnStaticPointersFail03.stderr
• testsuite/tests/rename/should_fail/T10668.hs
• testsuite/tests/rename/should_fail/T10668.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/T12681.hs
• testsuite/tests/rename/should_fail/T12681.stderr
• testsuite/tests/rename/should_fail/T13568.hs
• testsuite/tests/rename/should_fail/T13568.stderr
• testsuite/tests/rename/should_fail/T13644.hs
• testsuite/tests/rename/should_fail/T13644.stderr
• testsuite/tests/rename/should_fail/T13847.hs
• testsuite/tests/rename/should_fail/T13847.stderr
• testsuite/tests/rename/should_fail/T14032c.hs
• 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/T19843l.hs
• testsuite/tests/rename/should_fail/T19843l.stderr
• + testsuite/tests/rename/should_fail/T21101.hs
• + testsuite/tests/rename/should_fail/T21101.stderr
• testsuite/tests/rename/should_fail/T23570b.stderr
• testsuite/tests/rename/should_fail/T25899e2.stderr
• + testsuite/tests/rename/should_fail/T25901_exp_fail_1.hs
• + testsuite/tests/rename/should_fail/T25901_exp_fail_1.stderr
• + testsuite/tests/rename/should_fail/T25901_exp_fail_1_helper.hs
• + testsuite/tests/rename/should_fail/T25901_exp_fail_2.hs
• + testsuite/tests/rename/should_fail/T25901_exp_fail_2.stderr
• + testsuite/tests/rename/should_fail/T25901_exp_fail_2_helper.hs
• + testsuite/tests/rename/should_fail/T25901_imp_hq_fail_5.hs
• + testsuite/tests/rename/should_fail/T25901_imp_hq_fail_5.stderr
• + testsuite/tests/rename/should_fail/T25901_imp_hq_fail_6.hs
• + testsuite/tests/rename/should_fail/T25901_imp_hq_fail_6.stderr
• + testsuite/tests/rename/should_fail/T25901_imp_hu_fail_4.hs
• + testsuite/tests/rename/should_fail/T25901_imp_hu_fail_4.stderr
• + testsuite/tests/rename/should_fail/T25901_imp_sq_fail_2.hs
• + testsuite/tests/rename/should_fail/T25901_imp_sq_fail_2.stderr
• + testsuite/tests/rename/should_fail/T25901_imp_sq_fail_3.hs
• + testsuite/tests/rename/should_fail/T25901_imp_sq_fail_3.stderr
• + testsuite/tests/rename/should_fail/T25901_imp_su_fail_1.hs
• + testsuite/tests/rename/should_fail/T25901_imp_su_fail_1.stderr
• + testsuite/tests/rename/should_fail/T25901_sub_a.hs
• + testsuite/tests/rename/should_fail/T25901_sub_a.stderr
• + testsuite/tests/rename/should_fail/T25901_sub_b.hs
• + testsuite/tests/rename/should_fail/T25901_sub_b.stderr
• + testsuite/tests/rename/should_fail/T25901_sub_c.hs
• + testsuite/tests/rename/should_fail/T25901_sub_c.stderr
• + testsuite/tests/rename/should_fail/T25901_sub_c_helper.hs
• + testsuite/tests/rename/should_fail/T25901_sub_d.hs
• + testsuite/tests/rename/should_fail/T25901_sub_d.stderr
• + testsuite/tests/rename/should_fail/T25901_sub_d_helper.hs
• + testsuite/tests/rename/should_fail/T25901_sub_w.hs
• + testsuite/tests/rename/should_fail/T25901_sub_w.stderr
• + testsuite/tests/rename/should_fail/T26545.hs
• + testsuite/tests/rename/should_fail/T26545.stderr
• testsuite/tests/rename/should_fail/T5385.hs
• testsuite/tests/rename/should_fail/T5385.stderr
• testsuite/tests/rename/should_fail/T9815.stderr
• testsuite/tests/rename/should_fail/T9815b.stderr
• testsuite/tests/rename/should_fail/T9815bghci.stderr
• testsuite/tests/rename/should_fail/T9815ghci.stderr
• 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/RepPolyCase1.stderr
• − testsuite/tests/rep-poly/RepPolyCase2.stderr
• testsuite/tests/rep-poly/RepPolyNPlusK.stderr
• testsuite/tests/rep-poly/RepPolyRecordUpdate.stderr
• testsuite/tests/rep-poly/RepPolyRightSection.stderr
• testsuite/tests/rep-poly/RepPolyRule3.stderr
• testsuite/tests/rep-poly/RepPolyTuple4.stderr
• testsuite/tests/rep-poly/T12709.stderr
• testsuite/tests/rep-poly/T13233.stderr
• − testsuite/tests/rep-poly/T17021.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/T26528.hs
• testsuite/tests/rep-poly/UnliftedNewtypesLevityBinder.stderr
• testsuite/tests/rep-poly/all.T
• testsuite/tests/roles/should_compile/Roles1.stderr
• testsuite/tests/roles/should_compile/Roles13.stderr
• testsuite/tests/roles/should_compile/Roles14.stderr
• testsuite/tests/roles/should_compile/Roles2.stderr
• testsuite/tests/roles/should_compile/Roles3.stderr
• testsuite/tests/roles/should_compile/Roles4.stderr
• testsuite/tests/roles/should_compile/T8958.stderr
• testsuite/tests/roles/should_fail/Roles5.hs
• testsuite/tests/roles/should_fail/Roles5.stderr
• testsuite/tests/roles/should_fail/RolesIArray.stderr
• + testsuite/tests/rts/ClosureTable.hs
• + testsuite/tests/rts/ClosureTable_c.c
• testsuite/tests/rts/KeepCafsBase.hs
• testsuite/tests/rts/KeepCafsMain.hs
• testsuite/tests/rts/Makefile
• testsuite/tests/rts/T13676.script
• testsuite/tests/rts/T17574.hs
• + testsuite/tests/rts/T19048.hs
• + testsuite/tests/rts/T19048.stdout
• testsuite/tests/rts/T19381.hs
• + testsuite/tests/rts/T22859.hs
• + testsuite/tests/rts/T22859.stderr
• + testsuite/tests/rts/T25275/DebugIpe.hs
• + testsuite/tests/rts/T25275/T25275_A.stdout
• + testsuite/tests/rts/T25275/T25275_B.stdout
• + testsuite/tests/rts/T25275/T25275_C.stdout
• + testsuite/tests/rts/T25275/T25275_D.stdout
• + testsuite/tests/rts/T25275/TraceIpe.hs
• + testsuite/tests/rts/T25275/all.T
• + testsuite/tests/rts/T27123.hs
• + testsuite/tests/rts/T27131.hs
• + testsuite/tests/rts/T27131.stdout
• + testsuite/tests/rts/T27131_c.c
• + testsuite/tests/rts/T27434.hs
• + testsuite/tests/rts/T27434.stdout
• + testsuite/tests/rts/TimeoutQueue.c
• + testsuite/tests/rts/TimeoutQueue.stdout
• testsuite/tests/rts/all.T
• + testsuite/tests/rts/cloneThreadStackMigrating.hs
• testsuite/tests/rts/exec_signals_child.c
• testsuite/tests/rts/flags/all.T
• testsuite/tests/rts/ipe/IpeStats/Fold.hs
• testsuite/tests/rts/ipe/T24005/all.T
• testsuite/tests/rts/ipe/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/Makefile
• − 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/linker/T27072/Lib.c
• + testsuite/tests/rts/linker/T27072/Makefile
• + testsuite/tests/rts/linker/T27072/T27072.stdout
• + testsuite/tests/rts/linker/T27072/all.T
• + testsuite/tests/rts/linker/T27072/main.c
• + testsuite/tests/rts/linker/T6107.hs
• + testsuite/tests/rts/linker/T6107.stdout
• + testsuite/tests/rts/linker/T6107_sym1.s
• + testsuite/tests/rts/linker/T6107_sym2.s
• testsuite/tests/rts/linker/all.T
• testsuite/tests/rts/linker/rdynamic.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/rts/resizeMutableByteArrayInPlace.hs
• testsuite/tests/runghc/Makefile
• + testsuite/tests/runghc/T16145.hs
• + testsuite/tests/runghc/T16145.stdout
• + testsuite/tests/runghc/T16145_aux.hs
• testsuite/tests/runghc/T7859.stderr-mingw32
• testsuite/tests/runghc/all.T
• testsuite/tests/safeHaskell/flags/SafeFlags17.stderr
• testsuite/tests/safeHaskell/safeLanguage/SafeLang15.stderr
• testsuite/tests/saks/should_compile/all.T
• testsuite/tests/saks/should_compile/saks023.stdout
• testsuite/tests/saks/should_compile/saks034.stdout
• testsuite/tests/saks/should_compile/saks035.stdout
• testsuite/tests/showIface/DocsInHiFile.hs
• testsuite/tests/showIface/DocsInHiFile1.stdout
• testsuite/tests/showIface/DocsInHiFileTH.hs
• testsuite/tests/showIface/DocsInHiFileTH.stdout
• testsuite/tests/showIface/DocsInHiFileTHExternal.hs
• testsuite/tests/showIface/HaddockIssue849.hs
• testsuite/tests/showIface/HaddockIssue849.stdout
• testsuite/tests/showIface/HaddockOpts.hs
• testsuite/tests/showIface/HaddockOpts.stdout
• testsuite/tests/showIface/HaddockSpanIssueT24378.hs
• testsuite/tests/showIface/HaddockSpanIssueT24378.stdout
• testsuite/tests/showIface/MagicHashInHaddocks.hs
• testsuite/tests/showIface/MagicHashInHaddocks.stdout
• testsuite/tests/showIface/Makefile
• testsuite/tests/showIface/NoExportList.hs
• testsuite/tests/showIface/NoExportList.stdout
• testsuite/tests/showIface/PragmaDocs.stdout
• testsuite/tests/showIface/ReExports.stdout
• + testsuite/tests/showIface/T26246a.hs
• + testsuite/tests/showIface/T26246a.stdout
• testsuite/tests/showIface/all.T
• + testsuite/tests/simd/should_run/FloatConstant.hs
• + testsuite/tests/simd/should_run/FloatConstant.stdout
• + testsuite/tests/simd/should_run/IntConstant.hs
• + testsuite/tests/simd/should_run/IntConstant.stdout
• + testsuite/tests/simd/should_run/Makefile
• + testsuite/tests/simd/should_run/StackAlignment32.hs
• + testsuite/tests/simd/should_run/StackAlignment32.stdout
• + testsuite/tests/simd/should_run/StackAlignment32_main.c
• + testsuite/tests/simd/should_run/StackAlignment64.hs
• + testsuite/tests/simd/should_run/StackAlignment64.stdout
• + testsuite/tests/simd/should_run/StackAlignment64_main.c
• + testsuite/tests/simd/should_run/T25030.hs
• + testsuite/tests/simd/should_run/T25030.stdout
• + 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/T26411.hs
• + testsuite/tests/simd/should_run/T26411.stdout
• + testsuite/tests/simd/should_run/T26411b.hs
• + testsuite/tests/simd/should_run/T26411b.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_arith.hs
• testsuite/tests/simd/should_run/doublex2_arith.stdout
• testsuite/tests/simd/should_run/doublex2_arith_baseline.hs
• testsuite/tests/simd/should_run/doublex2_arith_baseline.stdout
• testsuite/tests/simd/should_run/doublex2_fma.hs
• testsuite/tests/simd/should_run/doublex2_fma.stdout
• + 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_arith.hs
• testsuite/tests/simd/should_run/floatx4_arith.stdout
• testsuite/tests/simd/should_run/floatx4_arith_baseline.hs
• testsuite/tests/simd/should_run/floatx4_arith_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/int16x8_arith.hs
• testsuite/tests/simd/should_run/int16x8_arith.stdout
• testsuite/tests/simd/should_run/int16x8_arith_baseline.hs
• testsuite/tests/simd/should_run/int16x8_arith_baseline.stdout
• testsuite/tests/simd/should_run/int16x8_shuffle.hs
• testsuite/tests/simd/should_run/int16x8_shuffle.stdout
• testsuite/tests/simd/should_run/int16x8_shuffle_baseline.hs
• testsuite/tests/simd/should_run/int16x8_shuffle_baseline.stdout
• testsuite/tests/simd/should_run/int32x4_arith.hs
• testsuite/tests/simd/should_run/int32x4_arith.stdout
• testsuite/tests/simd/should_run/int32x4_arith_baseline.hs
• testsuite/tests/simd/should_run/int32x4_arith_baseline.stdout
• testsuite/tests/simd/should_run/int64x2_arith.hs
• testsuite/tests/simd/should_run/int64x2_arith.stdout
• testsuite/tests/simd/should_run/int64x2_arith_baseline.hs
• testsuite/tests/simd/should_run/int64x2_arith_baseline.stdout
• testsuite/tests/simd/should_run/int8x16_arith.hs
• testsuite/tests/simd/should_run/int8x16_arith.stdout
• testsuite/tests/simd/should_run/int8x16_arith_baseline.hs
• testsuite/tests/simd/should_run/int8x16_arith_baseline.stdout
• testsuite/tests/simd/should_run/int8x16_shuffle.hs
• testsuite/tests/simd/should_run/int8x16_shuffle.stdout
• testsuite/tests/simd/should_run/int8x16_shuffle_baseline.hs
• testsuite/tests/simd/should_run/int8x16_shuffle_baseline.stdout
• testsuite/tests/simd/should_run/simd006.hs
• testsuite/tests/simd/should_run/simd010.hs
• testsuite/tests/simd/should_run/simd013C.c
• + 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/T9646/test.T
• 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/Makefile
• testsuite/tests/simplCore/should_compile/OpaqueNoCastWW.stderr
• testsuite/tests/simplCore/should_compile/RewriteHigherOrderPatterns.stderr
• testsuite/tests/simplCore/should_compile/T11562.hs
• + testsuite/tests/simplCore/should_compile/T12640.hs
• + testsuite/tests/simplCore/should_compile/T12640.stderr
• testsuite/tests/simplCore/should_compile/T13156.stdout
• testsuite/tests/simplCore/should_compile/T14003.stderr
• + testsuite/tests/simplCore/should_compile/T14908.hs
• + testsuite/tests/simplCore/should_compile/T14908_Deps.hs
• testsuite/tests/simplCore/should_compile/T14978.stdout
• testsuite/tests/simplCore/should_compile/T15056.stderr
• testsuite/tests/simplCore/should_compile/T15205.stderr
• testsuite/tests/simplCore/should_compile/T15445.stderr
• + testsuite/tests/simplCore/should_compile/T16122.hs
• + testsuite/tests/simplCore/should_compile/T16122.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/T18013.stderr
• + testsuite/tests/simplCore/should_compile/T18032.hs
• + testsuite/tests/simplCore/should_compile/T18032.stderr
• testsuite/tests/simplCore/should_compile/T18078.stderr
• testsuite/tests/simplCore/should_compile/T18668.stderr
• testsuite/tests/simplCore/should_compile/T18995.stderr
• + testsuite/tests/simplCore/should_compile/T19166.hs
• + testsuite/tests/simplCore/should_compile/T19166.stderr
• testsuite/tests/simplCore/should_compile/T19246.stderr
• testsuite/tests/simplCore/should_compile/T19599.stderr
• testsuite/tests/simplCore/should_compile/T19599a.stderr
• testsuite/tests/simplCore/should_compile/T19672.stderr
• testsuite/tests/simplCore/should_compile/T19890.stderr
• testsuite/tests/simplCore/should_compile/T21391.hs
• testsuite/tests/simplCore/should_compile/T21763.stderr
• testsuite/tests/simplCore/should_compile/T21763a.stderr
• testsuite/tests/simplCore/should_compile/T21917.stderr
• testsuite/tests/simplCore/should_compile/T21948.stderr
• testsuite/tests/simplCore/should_compile/T21960.hs
• 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/T23074.stderr
• testsuite/tests/simplCore/should_compile/T23307.stderr
• testsuite/tests/simplCore/should_compile/T23307a.stderr
• testsuite/tests/simplCore/should_compile/T24229a.stderr
• testsuite/tests/simplCore/should_compile/T24229b.stderr
• testsuite/tests/simplCore/should_compile/T24359a.stderr
• + testsuite/tests/simplCore/should_compile/T24606.hs
• testsuite/tests/simplCore/should_compile/T24808.stderr
• testsuite/tests/simplCore/should_compile/T25160.stderr
• testsuite/tests/simplCore/should_compile/T25389.stderr
• − testsuite/tests/simplCore/should_compile/T25713.stderr
• + testsuite/tests/simplCore/should_compile/T25718.hs
• + testsuite/tests/simplCore/should_compile/T25718.stderr
• + testsuite/tests/simplCore/should_compile/T25718a.hs
• + testsuite/tests/simplCore/should_compile/T25718a.stderr
• + testsuite/tests/simplCore/should_compile/T25718b.hs
• + testsuite/tests/simplCore/should_compile/T25718b.stderr
• + testsuite/tests/simplCore/should_compile/T25718c.hs
• + testsuite/tests/simplCore/should_compile/T25718c.stderr-ws-32
• + testsuite/tests/simplCore/should_compile/T25718c.stderr-ws-64
• + 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/T26615.hs
• + testsuite/tests/simplCore/should_compile/T26615.stderr
• + testsuite/tests/simplCore/should_compile/T26615a.hs
• + testsuite/tests/simplCore/should_compile/T26642.hs
• + testsuite/tests/simplCore/should_compile/T26681.hs
• + testsuite/tests/simplCore/should_compile/T26682.hs
• + testsuite/tests/simplCore/should_compile/T26682a.hs
• + testsuite/tests/simplCore/should_compile/T26709.hs
• + testsuite/tests/simplCore/should_compile/T26709.stderr
• + testsuite/tests/simplCore/should_compile/T26722.hs
• + testsuite/tests/simplCore/should_compile/T26722.stderr
• + testsuite/tests/simplCore/should_compile/T26805.hs
• + testsuite/tests/simplCore/should_compile/T26805.stderr
• + testsuite/tests/simplCore/should_compile/T26826.hs
• + testsuite/tests/simplCore/should_compile/T26903.hs
• + testsuite/tests/simplCore/should_compile/T26903.stderr
• + testsuite/tests/simplCore/should_compile/T26941.hs
• + testsuite/tests/simplCore/should_compile/T26941_aux.hs
• + testsuite/tests/simplCore/should_compile/T27261.hs
• + testsuite/tests/simplCore/should_compile/T27261_aux.hs
• + testsuite/tests/simplCore/should_compile/T27296.hs
• + testsuite/tests/simplCore/should_compile/T27296.stdout
• + testsuite/tests/simplCore/should_compile/T27296b.hs
• + testsuite/tests/simplCore/should_compile/T27296b.stdout
• testsuite/tests/simplCore/should_compile/T3717.stderr
• testsuite/tests/simplCore/should_compile/T3772.stdout
• + testsuite/tests/simplCore/should_compile/T4081.hs
• + testsuite/tests/simplCore/should_compile/T4081.stderr
• testsuite/tests/simplCore/should_compile/T4201.stdout
• testsuite/tests/simplCore/should_compile/T4908.stderr
• testsuite/tests/simplCore/should_compile/T4930.stderr
• testsuite/tests/simplCore/should_compile/T7360.stderr
• testsuite/tests/simplCore/should_compile/T8274.stdout
• testsuite/tests/simplCore/should_compile/T8331.stderr
• testsuite/tests/simplCore/should_compile/T8832.hs
• testsuite/tests/simplCore/should_compile/T8832.stdout
• testsuite/tests/simplCore/should_compile/T8848a.stderr
• testsuite/tests/simplCore/should_compile/T9400.stderr
• + testsuite/tests/simplCore/should_compile/T9445.hs
• + testsuite/tests/simplCore/should_compile/TrickyJoins.hs
• testsuite/tests/simplCore/should_compile/all.T
• testsuite/tests/simplCore/should_compile/noinline01.stderr
• testsuite/tests/simplCore/should_compile/par01.stderr
• testsuite/tests/simplCore/should_compile/rule2.stderr
• testsuite/tests/simplCore/should_compile/simpl017.stderr
• testsuite/tests/simplCore/should_compile/spec-inline.stderr
• testsuite/tests/simplCore/should_compile/spec004.stderr
• + testsuite/tests/simplCore/should_run/T26323.hs
• + testsuite/tests/simplCore/should_run/T26323.stdout
• + testsuite/tests/simplCore/should_run/T27005.hs
• + testsuite/tests/simplCore/should_run/T27005.stdout
• + testsuite/tests/simplCore/should_run/T27005_aux.hs
• + testsuite/tests/simplCore/should_run/T27071.hs
• + testsuite/tests/simplCore/should_run/T27071.stdout
• testsuite/tests/simplCore/should_run/T3591.hs
• testsuite/tests/simplCore/should_run/all.T
• testsuite/tests/simplStg/should_compile/T15226b.stderr
• testsuite/tests/simplStg/should_compile/T22840.stderr
• testsuite/tests/simplStg/should_compile/T24806.hs
• testsuite/tests/simplStg/should_compile/T24806.stderr
• + testsuite/tests/simplStg/should_compile/T27005b.hs
• + testsuite/tests/simplStg/should_compile/T27005b.stderr
• testsuite/tests/simplStg/should_compile/all.T
• testsuite/tests/simplStg/should_compile/inferTags004.hs
• testsuite/tests/simplStg/should_compile/inferTags004.stderr
• + testsuite/tests/simplStg/should_run/T27005a.hs
• + testsuite/tests/simplStg/should_run/T27005a.stdout
• testsuite/tests/simplStg/should_run/all.T
• + testsuite/tests/simplStg/should_run/unpack_enum.hs
• + testsuite/tests/simplStg/should_run/unpack_enum.stdout
• + 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/SI07.stderr-ext-interp
• testsuite/tests/splice-imports/SI08.stderr
• testsuite/tests/splice-imports/SI08_oneshot.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/SI36.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/T26616.hs
• + testsuite/tests/splice-imports/T26616.stderr
• testsuite/tests/splice-imports/all.T
• testsuite/tests/tcplugins/Common.hs
• testsuite/tests/tcplugins/CtIdPlugin.hs
• testsuite/tests/tcplugins/RewritePerfPlugin.hs
• testsuite/tests/tcplugins/T11462_Plugin.hs
• testsuite/tests/tcplugins/T11525_Plugin.hs
• + testsuite/tests/tcplugins/T26395.hs
• + testsuite/tests/tcplugins/T26395.stderr
• + testsuite/tests/tcplugins/T26395_Plugin.hs
• + testsuite/tests/tcplugins/TcPlugin_InitStop_Ghci.hs
• + testsuite/tests/tcplugins/TcPlugin_InitStop_Ghci.script
• + testsuite/tests/tcplugins/TcPlugin_InitStop_Ghci.stderr
• + testsuite/tests/tcplugins/TcPlugin_InitStop_Ghci.stdout
• + testsuite/tests/tcplugins/TcPlugin_InitStop_NoCode.hs
• + testsuite/tests/tcplugins/TcPlugin_InitStop_NoCode.hs-boot
• + testsuite/tests/tcplugins/TcPlugin_InitStop_NoCode.stderr
• + testsuite/tests/tcplugins/TcPlugin_InitStop_NoCode_aux.hs
• + testsuite/tests/tcplugins/TcPlugin_InitStop_Warn.hs
• + testsuite/tests/tcplugins/TcPlugin_InitStop_Warn.stderr
• testsuite/tests/tcplugins/TcPlugin_RewritePerf.hs
• testsuite/tests/tcplugins/TcPlugin_RewritePerf.stderr
• testsuite/tests/tcplugins/all.T
• + testsuite/tests/tcplugins/tc-plugin-initstop/Makefile
• + testsuite/tests/tcplugins/tc-plugin-initstop/Setup.hs
• + testsuite/tests/tcplugins/tc-plugin-initstop/TcPlugin_InitStop_Plugin.hs
• + testsuite/tests/tcplugins/tc-plugin-initstop/tc-plugin-initstop.cabal
• + 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/QQTopError.stderr
• testsuite/tests/th/T10267.stderr
• testsuite/tests/th/T10945.stderr
• testsuite/tests/th/T11452.stderr
• testsuite/tests/th/T14627.stderr
• testsuite/tests/th/T15321.stderr
• testsuite/tests/th/T16180.hs
• testsuite/tests/th/T16976z.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/T21547.stderr
• testsuite/tests/th/T23829_hasty.stderr
• testsuite/tests/th/T23829_hasty_b.stderr
• testsuite/tests/th/T23829_tardy.ghc.stderr
• testsuite/tests/th/T24111.stdout
• + testsuite/tests/th/T26098A_quote.hs
• + testsuite/tests/th/T26098A_splice.hs
• + testsuite/tests/th/T26098_local.hs
• + testsuite/tests/th/T26098_local.stderr
• + testsuite/tests/th/T26098_quote.hs
• + testsuite/tests/th/T26098_quote.stderr
• + testsuite/tests/th/T26098_splice.hs
• + testsuite/tests/th/T26098_splice.stderr
• + testsuite/tests/th/T26099.hs
• + testsuite/tests/th/T26099.stderr
• + testsuite/tests/th/T26568.hs
• + testsuite/tests/th/T26568.stderr
• + testsuite/tests/th/T26862_th.script
• + testsuite/tests/th/T26862_th.stderr
• + testsuite/tests/th/T27022.hs
• + testsuite/tests/th/T27022.stdout
• testsuite/tests/th/T5795.stderr
• testsuite/tests/th/T7276.stderr
• + testsuite/tests/th/T8306_th.script
• + testsuite/tests/th/T8306_th.stderr
• + testsuite/tests/th/T8306_th.stdout
• testsuite/tests/th/T8412.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_EmptyLamCases.hs
• + testsuite/tests/th/TH_EmptyLamCases.stderr
• + testsuite/tests/th/TH_EmptyMultiIf.hs
• + testsuite/tests/th/TH_EmptyMultiIf.stderr
• testsuite/tests/th/TH_NestedSplicesFail3.stderr
• testsuite/tests/th/TH_NestedSplicesFail4.stderr
• testsuite/tests/th/TH_Promoted1Tuple.hs
• testsuite/tests/th/TH_Roles1.hs
• testsuite/tests/th/TH_Roles2.stderr
• testsuite/tests/th/TH_StaticPointers02.stderr
• testsuite/tests/th/TH_implicitParams.stdout
• testsuite/tests/th/all.T
• testsuite/tests/type-data/should_run/T22332a.stderr
• + testsuite/tests/typecheck/T13180/T13180.hs
• + testsuite/tests/typecheck/T13180/T13180.hs-boot
• + testsuite/tests/typecheck/T13180/T13180.stderr
• + testsuite/tests/typecheck/T13180/T13180A.hs
• + testsuite/tests/typecheck/T13180/all.T
• testsuite/tests/typecheck/T16127/T16127.stderr
• testsuite/tests/typecheck/no_skolem_info/T13499.stderr
• testsuite/tests/typecheck/no_skolem_info/T20063.stderr
• testsuite/tests/typecheck/no_skolem_info/T20232.hs
• testsuite/tests/typecheck/no_skolem_info/T20232.stderr
• testsuite/tests/typecheck/should_compile/DeepSubsumption02.hs
• + testsuite/tests/typecheck/should_compile/ExpansionQLIm.hs
• + testsuite/tests/typecheck/should_compile/LazyFieldAnnotations.hs
• testsuite/tests/typecheck/should_compile/Makefile
• testsuite/tests/typecheck/should_compile/MutRec.hs
• testsuite/tests/typecheck/should_compile/T10770a.hs
• + testsuite/tests/typecheck/should_compile/T11141.hs
• + testsuite/tests/typecheck/should_compile/T11141.stderr
• testsuite/tests/typecheck/should_compile/T11339.hs
• testsuite/tests/typecheck/should_compile/T11339.stderr
• testsuite/tests/typecheck/should_compile/T11397.hs
• + testsuite/tests/typecheck/should_compile/T11505Bar.hs
• + testsuite/tests/typecheck/should_compile/T11505Foo.hs
• + testsuite/tests/typecheck/should_compile/T11505Foo.hs-boot
• + testsuite/tests/typecheck/should_compile/T12046.hs
• testsuite/tests/typecheck/should_compile/T12427a.stderr
• testsuite/tests/typecheck/should_compile/T12507.hs
• testsuite/tests/typecheck/should_compile/T12763.stderr
• testsuite/tests/typecheck/should_compile/T13032.stderr
• testsuite/tests/typecheck/should_compile/T13050.stderr
• testsuite/tests/typecheck/should_compile/T13526.hs
• testsuite/tests/typecheck/should_compile/T13651.hs
• − testsuite/tests/typecheck/should_compile/T13651.stderr
• testsuite/tests/typecheck/should_compile/T13951.hs
• + testsuite/tests/typecheck/should_compile/T14010.hs
• + testsuite/tests/typecheck/should_compile/T14151.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/T15242.stderr
• testsuite/tests/typecheck/should_compile/T16188.hs
• + testsuite/tests/typecheck/should_compile/T17705.hs
• testsuite/tests/typecheck/should_compile/T18406b.stderr
• testsuite/tests/typecheck/should_compile/T18467.hs
• testsuite/tests/typecheck/should_compile/T18467.stderr
• testsuite/tests/typecheck/should_compile/T18529.stderr
• testsuite/tests/typecheck/should_compile/T18920.hs
• + 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/T23135.hs
• testsuite/tests/typecheck/should_compile/T23171.hs
• testsuite/tests/typecheck/should_compile/T23739a.hs
• + testsuite/tests/typecheck/should_compile/T24464.hs
• testsuite/tests/typecheck/should_compile/T25180.stderr
• testsuite/tests/typecheck/should_compile/T2595.hs
• + testsuite/tests/typecheck/should_compile/T25992a.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/T26737.hs
• + testsuite/tests/typecheck/should_compile/T26746.hs
• + testsuite/tests/typecheck/should_compile/T26805a.hs
• testsuite/tests/typecheck/should_compile/T7541.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/WarnDefaultedCallStack.hs
• + testsuite/tests/typecheck/should_compile/WarnDefaultedCallStack.stderr
• testsuite/tests/typecheck/should_compile/abstract_refinement_hole_fits.stderr
• testsuite/tests/typecheck/should_compile/all.T
• testsuite/tests/typecheck/should_compile/constraint_hole_fits.stderr
• testsuite/tests/typecheck/should_compile/free_monad_hole_fits.stderr
• testsuite/tests/typecheck/should_compile/hole_constraints.stderr
• testsuite/tests/typecheck/should_compile/hole_constraints_nested.stderr
• testsuite/tests/typecheck/should_compile/holes.stderr
• testsuite/tests/typecheck/should_compile/holes2.stderr
• testsuite/tests/typecheck/should_compile/holes3.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/tc081.hs
• testsuite/tests/typecheck/should_compile/tc126.hs
• testsuite/tests/typecheck/should_compile/tc141.hs
• testsuite/tests/typecheck/should_compile/type_in_type_hole_fits.stderr
• testsuite/tests/typecheck/should_compile/valid_hole_fits.stderr
• testsuite/tests/typecheck/should_compile/valid_hole_fits_interactions.stderr
• testsuite/tests/typecheck/should_fail/AmbigFDs.hs
• − testsuite/tests/typecheck/should_fail/AmbigFDs.stderr
• testsuite/tests/typecheck/should_fail/ContextStack1.stderr
• testsuite/tests/typecheck/should_fail/DoExpansion1.stderr
• testsuite/tests/typecheck/should_fail/DoExpansion2.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/FunDepOrigin1b.stderr
• testsuite/tests/typecheck/should_fail/LazyFieldsDisabled.stderr
• + testsuite/tests/typecheck/should_fail/LazyFieldsDisabledStrictData.hs
• + testsuite/tests/typecheck/should_fail/LazyFieldsDisabledStrictData.stderr
• testsuite/tests/typecheck/should_fail/T10285.stderr
• testsuite/tests/typecheck/should_fail/T10534.stderr
• testsuite/tests/typecheck/should_fail/T10715b.stderr
• testsuite/tests/typecheck/should_fail/T10971d.stderr
• testsuite/tests/typecheck/should_fail/T11347.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/T12589.stderr
• + testsuite/tests/typecheck/should_fail/T12694.hs
• + testsuite/tests/typecheck/should_fail/T12694.stderr
• testsuite/tests/typecheck/should_fail/T13292.stderr
• testsuite/tests/typecheck/should_fail/T13311.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/T15067.stderr
• testsuite/tests/typecheck/should_fail/T15629.stderr
• testsuite/tests/typecheck/should_fail/T15767.stderr
• testsuite/tests/typecheck/should_fail/T15801.stderr
• testsuite/tests/typecheck/should_fail/T15807.stderr
• + testsuite/tests/typecheck/should_fail/T15850.hs
• + testsuite/tests/typecheck/should_fail/T15850.stderr
• + testsuite/tests/typecheck/should_fail/T15850_Lib.hs
• testsuite/tests/typecheck/should_fail/T15883e.stderr
• testsuite/tests/typecheck/should_fail/T16074.stderr
• + testsuite/tests/typecheck/should_fail/T16275.stderr
• + testsuite/tests/typecheck/should_fail/T16275A.hs
• + testsuite/tests/typecheck/should_fail/T16275B.hs
• + testsuite/tests/typecheck/should_fail/T16275B.hs-boot
• testsuite/tests/typecheck/should_fail/T16512a.stderr
• testsuite/tests/typecheck/should_fail/T17773.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/T20289.hs
• + testsuite/tests/typecheck/should_fail/T20289.stderr
• + testsuite/tests/typecheck/should_fail/T20289_A.hs
• 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/T22645.stderr
• 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/T22924a.stderr
• testsuite/tests/typecheck/should_fail/T22924b.stderr
• + testsuite/tests/typecheck/should_fail/T23162a.hs
• + testsuite/tests/typecheck/should_fail/T23162a.stderr
• + testsuite/tests/typecheck/should_fail/T23162b.hs
• + testsuite/tests/typecheck/should_fail/T23162b.stderr
• + testsuite/tests/typecheck/should_fail/T23162c.hs
• + testsuite/tests/typecheck/should_fail/T23162d.hs
• testsuite/tests/typecheck/should_fail/T23427.hs
• testsuite/tests/typecheck/should_fail/T23427.stderr
• + testsuite/tests/typecheck/should_fail/T23731.hs
• + testsuite/tests/typecheck/should_fail/T23731.stderr
• + testsuite/tests/typecheck/should_fail/T23731b.hs
• + testsuite/tests/typecheck/should_fail/T23731b.stderr
• + testsuite/tests/typecheck/should_fail/T23731b_aux.hs
• 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/T25679.hs
• + testsuite/tests/typecheck/should_fail/T25679.stderr
• + testsuite/tests/typecheck/should_fail/T25949.hs
• + testsuite/tests/typecheck/should_fail/T25949.stderr
• + testsuite/tests/typecheck/should_fail/T25949_aux.hs
• + testsuite/tests/typecheck/should_fail/T26137.hs
• + testsuite/tests/typecheck/should_fail/T26137.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/T26532.hs
• + testsuite/tests/typecheck/should_fail/T26532.stderr
• + testsuite/tests/typecheck/should_fail/T26823.hs
• + testsuite/tests/typecheck/should_fail/T26823.stderr
• + testsuite/tests/typecheck/should_fail/T26861.hs
• + testsuite/tests/typecheck/should_fail/T26861.stderr
• + testsuite/tests/typecheck/should_fail/T26862.hs
• + testsuite/tests/typecheck/should_fail/T26862.stderr
• + testsuite/tests/typecheck/should_fail/T27210.hs
• + testsuite/tests/typecheck/should_fail/T27210.stderr
• + testsuite/tests/typecheck/should_fail/T27390-explicit-kinds.stderr
• + testsuite/tests/typecheck/should_fail/T27390.hs
• + testsuite/tests/typecheck/should_fail/T27390.stderr
• + testsuite/tests/typecheck/should_fail/T27390a.hs
• testsuite/tests/typecheck/should_fail/T2846b.stderr
• testsuite/tests/typecheck/should_fail/T3323.stderr
• testsuite/tests/typecheck/should_fail/T3613.stderr
• testsuite/tests/typecheck/should_fail/T5236.stderr
• testsuite/tests/typecheck/should_fail/T5246.stderr
• testsuite/tests/typecheck/should_fail/T5300.stderr
• testsuite/tests/typecheck/should_fail/T5978.stderr
• testsuite/tests/typecheck/should_fail/T6022.stderr
• testsuite/tests/typecheck/should_fail/T6069.stderr
• testsuite/tests/typecheck/should_fail/T6078.hs
• testsuite/tests/typecheck/should_fail/T7264.stderr
• testsuite/tests/typecheck/should_fail/T7368a.hs
• testsuite/tests/typecheck/should_fail/T7368a.stderr
• testsuite/tests/typecheck/should_fail/T7453.hs
• testsuite/tests/typecheck/should_fail/T7453.stderr
• testsuite/tests/typecheck/should_fail/T7696.stderr
• testsuite/tests/typecheck/should_fail/T7851.stderr
• testsuite/tests/typecheck/should_fail/T7857.stderr
• testsuite/tests/typecheck/should_fail/T8142.stderr
• testsuite/tests/typecheck/should_fail/T8306.stderr
• testsuite/tests/typecheck/should_fail/T8570.hs
• testsuite/tests/typecheck/should_fail/T8570.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/T9858b.stderr
• testsuite/tests/typecheck/should_fail/TcCoercibleFail.hs
• testsuite/tests/typecheck/should_fail/TcCoercibleFail.stderr
• testsuite/tests/typecheck/should_fail/TcCoercibleFail3.stderr
• testsuite/tests/typecheck/should_fail/TcStaticPointersFail02.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/tcfail083.hs
• testsuite/tests/typecheck/should_fail/tcfail083.stderr
• testsuite/tests/typecheck/should_fail/tcfail084.hs
• testsuite/tests/typecheck/should_fail/tcfail084.stderr
• testsuite/tests/typecheck/should_fail/tcfail094.hs
• testsuite/tests/typecheck/should_fail/tcfail094.stderr
• testsuite/tests/typecheck/should_fail/tcfail102.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/tcfail181.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/T16981.hs
• + testsuite/tests/typecheck/should_run/T16981.stdout
• testsuite/tests/typecheck/should_run/T1735.hs
• testsuite/tests/typecheck/should_run/T1735_Help/Basics.hs
• + testsuite/tests/typecheck/should_run/T24773.hs
• + testsuite/tests/typecheck/should_run/T24773.stdout
• testsuite/tests/typecheck/should_run/T3731-short.hs
• testsuite/tests/typecheck/should_run/T3731.hs
• 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/typecheck/should_run/all.T
• testsuite/tests/typecheck/should_run/church.hs
• testsuite/tests/typecheck/should_run/tcrun008.hs
• testsuite/tests/typecheck/should_run/tcrun017.hs
• testsuite/tests/typecheck/should_run/tcrun026.hs
• testsuite/tests/typecheck/should_run/tcrun035.hs
• testsuite/tests/typecheck/should_run/tcrun036.hs
• + 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/unboxedsums4p.hs
• + testsuite/tests/unboxedsums/unboxedsums4p.stderr
• 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/T26967.hs
• + testsuite/tests/vdq-rta/should_compile/T26967.stderr
• + testsuite/tests/vdq-rta/should_compile/T26967_tyop.hs
• + testsuite/tests/vdq-rta/should_compile/T26967_tyop.stderr
• 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/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/DodgyImports.stderr
• + testsuite/tests/warnings/should_compile/DodgyImports02.hs
• + testsuite/tests/warnings/should_compile/DodgyImports02.stderr
• + testsuite/tests/warnings/should_compile/DodgyImports03.hs
• + testsuite/tests/warnings/should_compile/DodgyImports03.stderr
• + testsuite/tests/warnings/should_compile/DodgyImports03_helper.hs
• + testsuite/tests/warnings/should_compile/DodgyImports04.hs
• + testsuite/tests/warnings/should_compile/DodgyImports04.stderr
• testsuite/tests/warnings/should_compile/DodgyImports_hiding.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/SpecMultipleTysMono.hs
• + testsuite/tests/warnings/should_compile/SpecMultipleTysMono.stderr
• + testsuite/tests/warnings/should_compile/T25901_exp_dodgy.hs
• + testsuite/tests/warnings/should_compile/T25901_exp_dodgy.stderr
• + testsuite/tests/warnings/should_compile/T25901_exp_dup_wc_1.hs
• + testsuite/tests/warnings/should_compile/T25901_exp_dup_wc_1.stderr
• + testsuite/tests/warnings/should_compile/T25901_exp_dup_wc_2.hs
• + testsuite/tests/warnings/should_compile/T25901_exp_dup_wc_2.stderr
• + testsuite/tests/warnings/should_compile/T25901_exp_dup_wc_3.hs
• + testsuite/tests/warnings/should_compile/T25901_exp_dup_wc_3.stderr
• + testsuite/tests/warnings/should_compile/T25901_exp_dup_wc_4.hs
• + testsuite/tests/warnings/should_compile/T25901_exp_dup_wc_4.stderr
• + testsuite/tests/warnings/should_compile/T25901_helper_1.hs
• + testsuite/tests/warnings/should_compile/T25901_helper_2.hs
• + testsuite/tests/warnings/should_compile/T25901_helper_3.hs
• + testsuite/tests/warnings/should_compile/T25901_imp_dodgy_1.hs
• + testsuite/tests/warnings/should_compile/T25901_imp_dodgy_1.stderr
• + testsuite/tests/warnings/should_compile/T25901_imp_dodgy_2.hs
• + testsuite/tests/warnings/should_compile/T25901_imp_dodgy_2.stderr
• + testsuite/tests/warnings/should_compile/T25901_imp_unused_1.hs
• + testsuite/tests/warnings/should_compile/T25901_imp_unused_1.stderr
• + testsuite/tests/warnings/should_compile/T25901_imp_unused_2.hs
• + testsuite/tests/warnings/should_compile/T25901_imp_unused_2.stderr
• + testsuite/tests/warnings/should_compile/T25901_imp_unused_3.hs
• + testsuite/tests/warnings/should_compile/T25901_imp_unused_3.stderr
• + testsuite/tests/warnings/should_compile/T25901_imp_unused_4.hs
• + testsuite/tests/warnings/should_compile/T25901_imp_unused_4.stderr
• testsuite/tests/warnings/should_compile/all.T
• testsuite/tests/warnings/should_fail/CaretDiagnostics1.hs
• testsuite/tests/warnings/should_fail/CaretDiagnostics1.stderr
• testsuite/tests/warnings/should_fail/T24396c.hs
• testsuite/tests/warnings/should_fail/T24396c.stderr
• testsuite/tests/wasm/should_run/control-flow/LoadCmmGroup.hs
• testsuite/tests/wasm/should_run/control-flow/RunWasm.hs
• + utils/changelog-d/ChangelogD.hs
• + utils/changelog-d/LICENSE
• + utils/changelog-d/README.md
• + utils/changelog-d/changelog-d.cabal
• utils/check-exact/ExactPrint.hs
• utils/check-exact/Main.hs
• utils/check-exact/Parsers.hs
• utils/check-exact/Preprocess.hs
• utils/check-exact/Transform.hs
• utils/check-exact/Utils.hs
• utils/check-exact/check-exact.cabal
• utils/deriveConstants/Main.hs
• utils/genapply/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/Program.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/CONTRIBUTING.md
• utils/haddock/cabal.project
• utils/haddock/doc/.gitignore
• utils/haddock/doc/Makefile
• + utils/haddock/doc/_static/haddock-custom.css
• utils/haddock/doc/cheatsheet/haddocks.md
• utils/haddock/doc/conf.py
• utils/haddock/doc/markup.rst
• + utils/haddock/doc/snippets/.gitignore
• + utils/haddock/doc/snippets/Lists.hs
• + utils/haddock/doc/snippets/Makefile
• + utils/haddock/doc/snippets/Snippet-List-Bulleted.html
• + utils/haddock/doc/snippets/Snippet-List-Bulleted.tex
• + utils/haddock/doc/snippets/Snippet-List-Definition.html
• + utils/haddock/doc/snippets/Snippet-List-Definition.tex
• + utils/haddock/doc/snippets/Snippet-List-Enumerated.html
• + utils/haddock/doc/snippets/Snippet-List-Enumerated.tex
• + utils/haddock/doc/snippets/Snippet-List-Indentation.html
• + utils/haddock/doc/snippets/Snippet-List-Indentation.tex
• + utils/haddock/doc/snippets/Snippet-List-Multiline-Item.html
• + utils/haddock/doc/snippets/Snippet-List-Multiline-Item.tex
• + utils/haddock/doc/snippets/Snippet-List-Nested-Item.html
• + utils/haddock/doc/snippets/Snippet-List-Nested-Item.tex
• + utils/haddock/doc/snippets/Snippet-List-Not-Newline.html
• + utils/haddock/doc/snippets/Snippet-List-Not-Newline.tex
• + utils/haddock/doc/snippets/Snippet-List-Not-Separated.html
• + utils/haddock/doc/snippets/Snippet-List-Not-Separated.tex
• utils/haddock/haddock-api/haddock-api.cabal
• utils/haddock/haddock-api/src/Haddock.hs
• − utils/haddock/haddock-api/src/Haddock/Backends/HaddockDB.hs
• 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/Parser.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.hs
• utils/haddock/haddock-api/src/Haddock/Backends/Xhtml/Decl.hs
• utils/haddock/haddock-api/src/Haddock/Backends/Xhtml/DocMarkup.hs
• utils/haddock/haddock-api/src/Haddock/Backends/Xhtml/Layout.hs
• utils/haddock/haddock-api/src/Haddock/Backends/Xhtml/Meta.hs
• utils/haddock/haddock-api/src/Haddock/Backends/Xhtml/Names.hs
• utils/haddock/haddock-api/src/Haddock/Backends/Xhtml/Themes.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/Doc.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/Json.hs
• utils/haddock/haddock-api/src/Haddock/Interface/LexParseRn.hs
• utils/haddock/haddock-api/src/Haddock/Interface/ParseModuleHeader.hs
• utils/haddock/haddock-api/src/Haddock/Interface/Rename.hs
• utils/haddock/haddock-api/src/Haddock/Interface/RenameType.hs
• utils/haddock/haddock-api/src/Haddock/InterfaceFile.hs
• utils/haddock/haddock-api/src/Haddock/Options.hs
• utils/haddock/haddock-api/src/Haddock/Parser.hs
• utils/haddock/haddock-api/src/Haddock/Types.hs
• utils/haddock/haddock-api/src/Haddock/Utils.hs
• utils/haddock/haddock-api/src/Haddock/Utils/Json.hs
• utils/haddock/haddock-api/src/Haddock/Utils/Json/Parser.hs
• utils/haddock/haddock-api/src/Haddock/Utils/Json/Types.hs
• utils/haddock/haddock-library/haddock-library.cabal
• utils/haddock/haddock-library/src/Documentation/Haddock/Doc.hs
• utils/haddock/haddock-library/src/Documentation/Haddock/Markup.hs
• utils/haddock/haddock-library/src/Documentation/Haddock/Parser.hs
• utils/haddock/haddock-library/src/Documentation/Haddock/Parser/Util.hs
• utils/haddock/haddock-library/src/Documentation/Haddock/Types.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/A.html
• utils/haddock/html-test/ref/Bug1004.html
• utils/haddock/html-test/ref/Bug1033.html
• utils/haddock/html-test/ref/Bug1050.html
• utils/haddock/html-test/ref/Bug1103.html
• + utils/haddock/html-test/ref/Bug25739.html
• utils/haddock/html-test/ref/Bug26.html
• + utils/haddock/html-test/ref/Bug26246.html
• utils/haddock/html-test/ref/Bug298.html
• utils/haddock/html-test/ref/Bug458.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/DefaultSignatures.html
• utils/haddock/html-test/ref/FunArgs.html
• utils/haddock/html-test/ref/GADTRecords.html
• utils/haddock/html-test/ref/Hash.html
• utils/haddock/html-test/ref/Instances.html
• utils/haddock/html-test/ref/LinearTypes.html
• utils/haddock/html-test/ref/Nesting.html
• utils/haddock/html-test/ref/PatternSyns.html
• + utils/haddock/html-test/ref/PatternSyns2.html
• utils/haddock/html-test/ref/PromotedTypes.html
• utils/haddock/html-test/ref/QuasiExpr.html
• + utils/haddock/html-test/ref/RedactTypeSynonyms.html
• utils/haddock/html-test/ref/T23616.html
• utils/haddock/html-test/ref/Test.html
• utils/haddock/html-test/ref/TitledPicture.html
• utils/haddock/html-test/ref/TypeFamilies3.html
• utils/haddock/html-test/ref/TypeOperators.html
• utils/haddock/html-test/ref/Unicode.html
• utils/haddock/html-test/ref/Unicode2.html
• + utils/haddock/html-test/src/Bug25739.hs
• + utils/haddock/html-test/src/Bug26246.hs
• utils/haddock/html-test/src/LinearTypes.hs
• + utils/haddock/html-test/src/PatternSyns2.hs
• + utils/haddock/html-test/src/RedactTypeSynonyms.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/LinearTypes/LinearTypes.hs
• + utils/haddock/latex-test/src/RedactTypeSynonyms/RedactTypeSynonyms.hs
• utils/hpc
• utils/hsc2hs
• − utils/iserv/cbits/iservmain.c
• − utils/iserv/iserv.cabal.in
• − utils/iserv/src/Main.hs
• utils/jsffi/dyld.mjs
• utils/jsffi/post-link.mjs
• utils/jsffi/prelude.mjs

The diff was not included because it is too large.