[Git][ghc/ghc][ghc-9.14] 204 commits: template haskell: use a precise condition when implicitly lifting

29 Jul 2026

      Zubin pushed to branch ghc-9.14 at Glasgow Haskell Compiler / GHC

Commits:
e86c2396 by Matthew Pickering at 2026-05-27T12:05:05+05:30
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

(cherry picked from commit 9c3a09370fc8f047cb475d80c9edfde389af8376)

- - - - -
38aff667 by Cheng Shao at 2026-05-27T12:05:24+05:30
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>
(cherry picked from commit b29147977d09a78e46b94fbefdf6de3fa5e08f83)

- - - - -
b0f887ad by Cheng Shao at 2026-05-27T12:05:29+05:30
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>
(cherry picked from commit 0335d8996ebc34f74a1940928d3a63bcd5efd755)

- - - - -
b4f0eba7 by sheaf at 2026-05-27T12:09:10+05:30
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

(cherry picked from commit 8adfc22242b068417acc43cc682b79ff36ea673b)

- - - - -
9eb467f9 by Alex Washburn at 2026-05-27T12:09:34+05:30
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.

(cherry picked from commit 0a601c30d5e885d9b15b202f1fce55ca263315fb)

- - - - -
c912bf9f by Sean D. Gillespie at 2026-05-27T12:10:14+05:30
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

(cherry picked from commit 9c304ec00750b69acb854cd47e50bda0c34ea543)

- - - - -
9d30bebf by Julian Ospald at 2026-05-27T12:10:27+05:30
Skip uniques test if sources are not available

(cherry picked from commit 5dc2e9eaf60fd72771bf2e8112aec182665461a1)

- - - - -
ab1caefc by Julian Ospald at 2026-05-27T12:10:37+05:30
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.

(cherry picked from commit 643ce801a8b559071683cad0e5adbc26b9fc8385)

- - - - -
0d6b71ee by Andreas Klebinger at 2026-05-27T12:10:47+05:30
Add a perf test for #26425

(cherry picked from commit 4038a28b8594ae91c000d5bc7fceed4815eb4826)

- - - - -
154aa66a by Andreas Klebinger at 2026-05-27T12:10:57+05:30
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
-------------------------

(cherry picked from commit f997618e08ce5aad8b7564b8073889b52bc18700)

- - - - -
35f0e087 by Cheng Shao at 2026-05-27T12:11:05+05:30
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.

(cherry picked from commit 39567e85fa514c0c4dfeaf8faa586a47dd3e11ca)

- - - - -
a0107da2 by Simon Peyton Jones at 2026-05-27T12:11:39+05:30
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.

(cherry picked from commit c052c724d2dfc994994b6548545836969aee8ed8)

- - - - -
265f9e91 by ARATA Mizuki at 2026-05-27T12:11:50+05:30
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

(cherry picked from commit b22777d4b7182f40a31eb430fa27f5fb9ef0f292)

- - - - -
5279821a by sheaf at 2026-05-27T12:12:01+05:30
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

(cherry picked from commit 43fa8be89bdccbbe730daf0be7bdae8dde99ce44)

- - - - -
e48ba856 by sheaf at 2026-05-27T12:12:10+05:30
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

(cherry picked from commit 79dfcfe008af5e04c0f51cc2a3709ee08aebd59b)

- - - - -
c92d07ac by ARATA Mizuki at 2026-05-27T12:12:20+05:30
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>
(cherry picked from commit aada5db93a2f0fd00c0715ad9ca4f666ffb3d9d8)

- - - - -
89a1036c by Andreas Klebinger at 2026-05-27T12:12:28+05:30
Add hpc to release script

(cherry picked from commit 64ec82ffa7f48399e18fcec43051d2b7ddcb7cc2)

- - - - -
0b9684db by Matthew Pickering at 2026-05-27T12:12:37+05:30
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

(cherry picked from commit b7fe744598b4569cd0236268e4f6f5b9d27e12b7)

- - - - -
dd75ad42 by Ben Gamari at 2026-05-27T12:12:53+05:30
gitlab-ci: Run ghcup-metadata jobs on OpenCape runners

This significantly reduces our egress traffic
and makes the jobs significantly faster.

(cherry picked from commit ff3f0d09bce1c261638b572af2bac1d87f1f6df7)

- - - - -
8ea0c77e by Matthew Pickering at 2026-05-27T12:15:49+05:30
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.

(cherry picked from commit ef0dc33b2034fd91e11950751264e8b2e9f03fc4)

- - - - -
c3d58d81 by Georgios Karachalias at 2026-05-27T12:40:52+05:30
Use OsPath in PkgDbRef and UnitDatabase, not FilePath

(cherry picked from commit fa3bd0a67eea13701d1b50053636f9645e999308)

- - - - -
82a56720 by Ben Gamari at 2026-05-27T12:41:23+05:30
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
-------------------------

(cherry picked from commit 0d7c05eca214d396b2a25d9690206d0ef9f2f12b)

- - - - -
d6d82077 by Luite Stegeman at 2026-05-27T12:41:33+05:30
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

(cherry picked from commit c71faa7697f2d0bc8b92173aeb1f063ca8ed235a)

- - - - -
e2c859de by mangoiv at 2026-05-27T12:42:12+05:30
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.

(cherry picked from commit 3bd7dd44152f74d7a9fdd036f26be10c17127127)

- - - - -
e4b9fe3b by mangoiv at 2026-06-10T22:04:34+05:30
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

(cherry picked from commit c7061392bf0c1bf1e1a27820356627638f212a59)

- - - - -
6113c71f by Matthew Pickering at 2026-06-10T22:04:34+05:30
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

(cherry picked from commit 9d371d23c526fd160d7e99bef2bc7da825cf3c0f)

- - - - -
ab8574d3 by Julian Ospald at 2026-06-10T22:04:34+05:30
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.

(cherry picked from commit fc958fc9eb6f6f4db473cdda23c381da8f32163d)

- - - - -
536cf49a by Rodrigo Mesquita at 2026-06-10T22:04:34+05:30
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

(cherry picked from commit 2ef1601a07b28b04ee6dbc9906ee4bceae3fcdeb)

- - - - -
dff1d802 by Rodrigo Mesquita at 2026-06-10T22:04:34+05:30
Add test for #26640

(cherry picked from commit 747153d20405cca9c3893bbb88ace6c96dbd8597)

- - - - -
dfd5dc69 by Recursion Ninja at 2026-06-10T22:04:34+05:30
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

(cherry picked from commit fe2b79f4f21acf077738eb9ae9868c6b28afd1c4)

- - - - -
a364d6cc by Cheng Shao at 2026-06-10T22:04:34+05:30
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.

(cherry picked from commit 46c9746f19828fce4e7a6f3d078d631528a8f455)

- - - - -
fe624a9d by Peter Trommler at 2026-06-10T22:04:35+05:30
Cmm: remove restriction in MachOp folding

(cherry picked from commit 123a8d77ac93a6049e8554ede8dc814cf73e7a25)

- - - - -
ef154233 by sheaf at 2026-06-10T22:04:35+05:30
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.

(cherry picked from commit fca9cd7ce4abc4320c66f6a619063b2c66890504)

- - - - -
b0e2be09 by sheaf at 2026-06-10T22:04:35+05:30
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.

(cherry picked from commit 53150617c8648635b0fbfc4144f04c53e7180a60)

- - - - -
dff528b5 by sheaf at 2026-06-10T22:04:35+05:30
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
-------------------------

(cherry picked from commit c7a56dd1ea2b8bd4cd9dc4a46e07c589db559383)

- - - - -
c82eb00d by sheaf at 2026-06-10T22:04:35+05:30
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

(cherry picked from commit c2e83339593bc31a82a0fdb7f11fa693324f9804)

- - - - -
35b4fa07 by sheaf at 2026-06-10T22:04:35+05:30
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).

(cherry picked from commit 55ab583b40ecdc1abc3307cea1d6a2c958a5ed29)

- - - - -
f0a87570 by Cheng Shao at 2026-06-10T22:04:35+05:30
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>
(cherry picked from commit 1ca4b49a561447222072a44320fa9b0b5f6048e0)

- - - - -
d8af65ce by Cheng Shao at 2026-06-10T22:04:35+05:30
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>
(cherry picked from commit f69c5f1492b275da7d2947612574d5c520a69653)

- - - - -
7cf04b87 by Cheng Shao at 2026-06-10T22:04:35+05:30
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
-------------------------

(cherry picked from commit b26d134a666dcc2ca92d9cffc17cd38ab3af6590)

- - - - -
97592e74 by Aaron Allen at 2026-06-10T22:04:35+05:30
[#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

(cherry picked from commit 8a317b6f6d007b7cb5f2d661849383042892b3d8)

- - - - -
1b2775e9 by Cheng Shao at 2026-06-10T22:04:35+05:30
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)

(cherry picked from commit ae1aeaabac1d49c98be2b48700dcbb4cc402ffe0)

- - - - -
b01d6236 by Cheng Shao at 2026-06-10T22:04:35+05:30
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>
(cherry picked from commit 414d1fe1a51a9b0cfe88fe902cd4f5737d19da69)

- - - - -
ef8f5355 by Cheng Shao at 2026-06-10T22:04:35+05:30
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.

(cherry picked from commit c7f6fba3d0aea3b550441e10a54bb402b73dcd1f)

- - - - -
b49eb609 by Simon Peyton Jones at 2026-06-10T22:04:35+05:30
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.

(cherry picked from commit 52d00c05e1d803b36c93295399fe931c871166bf)

- - - - -
9325cdd8 by Aaron Allen at 2026-06-10T22:04:35+05:30
[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

(cherry picked from commit 8a3900a325a8f476d1e31a84deeab934b9161801)

- - - - -
2a3f2d83 by Simon Peyton Jones at 2026-06-10T22:04:35+05:30
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

(cherry picked from commit 393f9c51437364c959f1de39f91fac41eb6ddcdc)

- - - - -
52e0f1d0 by Simon Peyton Jones at 2026-06-10T22:04:35+05:30
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]

(cherry picked from commit ad76fb0f493f3c7833cd6fd3e712579e6c77697a)

- - - - -
fb772021 by Matthew Pickering at 2026-06-10T22:04:35+05:30
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

(cherry picked from commit 322dd6726b11c7101c28ffb8aeb7cb4cee34ab56)

- - - - -
55f0de7c by Simon Peyton Jones at 2026-06-10T22:04:35+05:30
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.

(cherry picked from commit 641ec3f01974dff9dfd756f3f0499796c8df1a8b)

- - - - -
277250dd by Cheng Shao at 2026-06-10T22:04:35+05:30
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.

(cherry picked from commit 2433e91d41675d56f48f82d22430a8dee915e7a0)

- - - - -
9903f791 by Cheng Shao at 2026-06-10T22:04:35+05:30
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.

(cherry picked from commit e5926fbebf341ee547227d41710d78471eecd09c)

- - - - -
e6229ce4 by Cheng Shao at 2026-06-10T22:04:35+05:30
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>
(cherry picked from commit 244d57d79a555dcecc7590287bb14976d561291a)

- - - - -
44af1ad6 by sheaf at 2026-06-10T22:04:35+05:30
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

(cherry picked from commit 023c301c51e7346af3d4d773c448277ad3645ad2)

- - - - -
2d465bef by fendor at 2026-06-10T22:04:35+05:30
Remove `traceId` from ghc-pkg executable

(cherry picked from commit d0966e64880e9fa30ce07c0fa5ea28108c6e8ad9)

- - - - -
36a901ec by Peter Trommler at 2026-06-10T22:04:35+05:30
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

(cherry picked from commit c1fe009739da8b368e59b87b00d7c568ab571643)

- - - - -
66b3b7c5 by Cheng Shao at 2026-06-10T22:04:35+05:30
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>
(cherry picked from commit b18b2c42c32488ad6d3480a56a1fcd753cad2023)

- - - - -
01890325 by Cheng Shao at 2026-06-10T22:04:35+05:30
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).

(cherry picked from commit eea2036b7c367cc61cd5846379be10954ca75345)

- - - - -
a324fe9a by Cheng Shao at 2026-06-10T22:04:35+05:30
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.

(cherry picked from commit 41432d25b7a66fa36a0e3def429fd98d24e3c780)

- - - - -
f68eaa42 by Andreas Klebinger at 2026-06-10T22:04:35+05:30
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>
(cherry picked from commit 9534b032ecc24fb01609ae6b9861101973ba2a72)

- - - - -
09b2d9d8 by Cheng Shao at 2026-06-10T22:04:35+05:30
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>
(cherry picked from commit ca79475f6b4dfba991e2c933bac9c22d54a4950d)

- - - - -
d7825f12 by Sylvain Henry at 2026-06-10T22:04:35+05:30
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.

(cherry picked from commit 0491f08a965df0d6448bd9cd940d2b86fca2db5d)

- - - - -
ad1b86a9 by Sylvain Henry at 2026-06-10T22:04:36+05:30
GC: suffix parallel GC with "par" instead of "thr"

Avoid some potential confusion (see discussion in !15351).

(cherry picked from commit 211a8f5633f0a5069c0689171f60b57719a242be)

- - - - -
7879b4e2 by Matthew Pickering at 2026-06-10T22:04:36+05:30
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.

(cherry picked from commit ee937134aa0ddf35c1a9dc7334c0aec0de13b719)

- - - - -
1c36c0fc by Zubin Duggal at 2026-06-10T22:04:36+05:30
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

(cherry picked from commit 1b490f5a7bbdb1441948241e6089b31efba9db45)

- - - - -
92e7c4d3 by Peter Trommler at 2026-06-10T22:04:36+05:30
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

(cherry picked from commit 56db94f791c6aae32798d82b74670c9d6392b931)

- - - - -
1ccd07d8 by Matthew Pickering at 2026-06-10T22:05:16+05:30
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

(cherry picked from commit 94dcd15e54146abecf9b4f5e47d258ca3cd40f1b)

- - - - -
244c4852 by sterni at 2026-06-10T22:05:23+05:30
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>
(cherry picked from commit e8f5a45de561ec80c88cd3da2c66502deb32d4c3)

- - - - -
63566924 by Jessica Clarke at 2026-06-10T22:05:23+05:30
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
(cherry picked from commit ce2d62fba69d2ea0c74c46c50628feb8b81719d2)

- - - - -
12963d00 by Michael Karcher at 2026-06-10T22:05:23+05:30
NCG for PPC: add pattern for CmmRegOff to iselExpr64

Closes #26828

(cherry picked from commit 43d977619de65c0cf87695fa5d86f1a3ff3176c3)

- - - - -
d694c8c6 by Matthew Pickering at 2026-06-10T22:05:23+05:30
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

(cherry picked from commit aeeb4a2034e80e26503eb88f5abde85e87a82f7b)

- - - - -
5719f06d by Andrew Lelechenko at 2026-06-10T22:05:23+05:30
Upgrade text submodule to 2.1.4

(cherry picked from commit 9e4d70c2764d117c5cf753127f93056d66e4f0d7)

- - - - -
a7a01f90 by Zubin Duggal at 2026-06-10T22:05:23+05:30
Bump transformers submodule to 0.6.3.0

Fixes #26790

(cherry picked from commit ea0d1317a630799a6b7bea12b24ef7e1ea6ed512)

- - - - -
9edd15f5 by Simon Peyton Jones at 2026-06-10T22:05:23+05:30
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.)

(cherry picked from commit cbe4300ef586c8bee1800426624db12e0237c6b5)

- - - - -
ae37b360 by Simon Peyton Jones at 2026-06-10T22:05:23+05:30
Modify a debug-trace in the Simplifier

...just to show a bit more information.

(cherry picked from commit a193a8dabf280bf53a227f37af4465ef263f6e21)

- - - - -
5ba132ce by Simon Peyton Jones at 2026-06-10T22:05:23+05:30
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.

(cherry picked from commit b579dfdc614e288b0fd754ac69ae7ff723d808be)

- - - - -
68d9a823 by Cheng Shao at 2026-06-10T22:05:23+05:30
libraries: bump Cabal submodule to 3.16.1.0

(cherry picked from commit fac0de1e357caa96913e19d924aad711d3b390cc)

- - - - -
1f502e18 by Cheng Shao at 2026-06-10T22:05:23+05:30
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.

(cherry picked from commit 00589122f8e90e2caabdd190835ab248e67e729b)

- - - - -
953bd84b by Cheng Shao at 2026-06-10T22:05:23+05:30
libraries: bump directory submodule to 1.3.10.1

(cherry picked from commit 84474c711e3a819a2809c6d293d6d6dcf1d68d4b)

- - - - -
fed8a70b by Cheng Shao at 2026-06-10T22:05:23+05:30
libraries: bump exceptions submodule to 0.10.12

(cherry picked from commit 1a9f46621404e9d6b235b5359b4fea5dbb9f31cf)

- - - - -
d2ede9df by Matthew Pickering at 2026-06-10T22:05:23+05:30
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

(cherry picked from commit 0020e38a021b5f0371c48fe73cddf8987acb1eb1)

- - - - -
9bbaed04 by John Paul Adrian Glaubitz at 2026-06-10T22:05:23+05:30
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

(cherry picked from commit 7c52c4f9bc8d6ae6404039ec02efe48fbf7a4778)

- - - - -
a119b15e by Simon Peyton Jones at 2026-06-10T22:05:23+05:30
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

(cherry picked from commit 99d8c146c12146e1e21b1f2d31809845d4afe9d4)

- - - - -
6dfdd1f7 by Cheng Shao at 2026-06-10T22:05:23+05:30
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.

(cherry picked from commit 039f19778e35b193af0de2a2c6ed89556038627a)

- - - - -
888b608f by Brian J. Cardiff at 2026-06-10T22:05:23+05:30
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

(cherry picked from commit 4f2840f2bb729ef1a6660f9f5c46906b7b838147)

- - - - -
480c0b7f by fendor at 2026-06-10T22:07:51+05:30
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.

(cherry picked from commit 4c40df3df7e806e6e21259fa51d872c4f3f9f726)

- - - - -
6c106393 by Vladislav Zavialov at 2026-06-10T22:07:51+05:30
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.

(cherry picked from commit bd3eba86180083a3bd1633994b9e6cd3be501a1d)

- - - - -
820cbb88 by sheaf at 2026-06-10T22:07:51+05:30
Careful with ticked join points in mergeCaseAlts

This commit backports the fix to GHC.Core.Utils.mergeCaseAlts that was
carried out in f726fcc4fb0b59f8ad2e2fa80f1b03efdaf73c30.

That is, this commit addresses the regression that was introduced by
e026bdf275e287005f2c2e534d3ba034ebf11c01, which allowed mergeCaseAlts to
move ticks in between a join point and one of its jumps, which results
in disaster (see #26929 but also #26642, #26693).

See (MC6) in Note [Merge Nested Cases] for a detailed explanation.

(cherry picked from commit 08bc245be70d95801bc1138804ed1de9474fbdc0)
(cherry picked from commit 974586eb5b6a924e8ce3ea8c4b2180ea9c0f3801)
(cherry picked from commit 1cbf9aed2d1f1c766fba0b25986112051bf9a539)

- - - - -
86c8f230 by Sylvain Henry at 2026-06-10T22:07:51+05:30
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.

(cherry picked from commit ad25af90bdbf1269ff9febbcbc9fffa804b11bda)

- - - - -
57ed944b by sheaf at 2026-06-10T22:07:51+05:30
System.Info.fullCompilerVersion: add 'since' annot

Fixes #26973

(cherry picked from commit fc8b8e27398b4d9d901fb65d15a7d8b23df428b8)

- - - - -
307bfbe1 by Luite Stegeman at 2026-06-10T22:07:51+05:30
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

(cherry picked from commit 12f8b82912787e1eb964a9a56e388bd0ec8c741b)

- - - - -
d52e2e80 by Luite Stegeman at 2026-06-10T22:07:51+05:30
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.

(cherry picked from commit f87e5e57dad499bf0d47ef2c074284e87a87dde3)

- - - - -
c2996f89 by Cheng Shao at 2026-06-10T22:07:52+05:30
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.

(cherry picked from commit d054b4676298ea2189cd48fcf175676b97f559e7)

- - - - -
a4ea5689 by Matthew Pickering at 2026-06-10T22:07:52+05:30
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.

(cherry picked from commit d57f01a4dd8b3886a02731c8ca27ee758baa768a)

- - - - -
d6ad8408 by Matthew Pickering at 2026-06-10T22:07:52+05:30
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

(cherry picked from commit 23d111ce0b2bef9bbf1fae2224359b2e1e79be65)

- - - - -
d9e34bd4 by Cheng Shao at 2026-06-10T22:07:52+05:30
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.

(cherry picked from commit 4c58a3aecf8071bfcda6d0787652b89dec4a442f)

- - - - -
162955e0 by Zubin Duggal at 2026-06-10T22:07:52+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.

(cherry picked from commit 870243e4f2a24730539f01ee8e3f3949c42ff312)

- - - - -
1d96bafb by Brandon Simmons at 2026-06-10T22:07:52+05:30
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

(cherry picked from commit 02e68a86e438edb315ba8622c58733d830557574)

- - - - -
89ed5a05 by Andreas Klebinger at 2026-06-10T22:07:52+05:30
Fix missing profiling header for origin_thunk frame.

Fixes #27007

(cherry picked from commit 63ae8eb38c54eaba77949b048a3621a5f4ca76e3)

- - - - -
a6bb3f67 by Andreas Klebinger at 2026-06-10T22:07:52+05:30
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

(cherry picked from commit 43638643adbe999de8d2288a40bdd15c602f6481)

- - - - -
d13be221 by fendor at 2026-06-10T22:07:52+05:30
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.

(cherry picked from commit 86bd9bfc1c0ea85ea7063af5f7d5495246be5094)

- - - - -
0e524b6b by Zubin Duggal at 2026-06-10T22:07:52+05:30
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

(cherry picked from commit 80e2dd4f084eff9cc857b31daf9ea2e9e460c727)

- - - - -
f557ab85 by Luite Stegeman at 2026-06-10T22:07:52+05:30
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

(cherry picked from commit 72b20fc0ad4b6ad12c67f686af5cb42700656886)

- - - - -
cd26930a by Sylvain Henry at 2026-06-10T22:07:52+05:30
JS: install rts/Types.h header file (#27033)

It was an omission, making HsFFI.h not usable with GHC using the JS
backend.

(cherry picked from commit 5b1be555be4f0989d78c274991c5046d7ac6d25e)

- - - - -
801eb2cc by Rodrigo Mesquita at 2026-06-10T22:07:52+05:30
Expose decodeStackWithIpe from ghc-experimental

This decoding is useful to the debugger and it wasn't originally
exported as an oversight.

(cherry picked from commit 67c47771185d5540a9e732f5418ffeaecd4cac5f)

- - - - -
54960c48 by Matthew Pickering at 2026-06-10T22:07:52+05:30
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.

(cherry picked from commit 1851336595243259a37eaac75aba174825aca028)

- - - - -
e71222d0 by ARATA Mizuki at 2026-06-10T22:07:52+05:30
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>
(cherry picked from commit a5ec467ee3d4e77c026437a545981269acde3434)

- - - - -
870b27d0 by sheaf at 2026-06-10T22:07:52+05:30
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>
(cherry picked from commit 45428f88f62896650156dc8222299744ae2a00e4)

- - - - -
7e39423e by Ian Duncan at 2026-06-10T22:07:52+05:30
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.

(cherry picked from commit 2823b03966e495581f4695f07649c5885306b656)

- - - - -
5e9d2873 by Matthew Pickering at 2026-06-10T22:07:52+05:30
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

(cherry picked from commit 5b550754ca0153a705ec607407074fe5716c1f7e)

- - - - -
e74ca3c3 by Wen Kokke at 2026-06-10T22:07:52+05:30
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.

(cherry picked from commit 3d6492ce311611707e80b2594103ddbe93fc6c76)

- - - - -
8fc8235a by Luite Stegeman at 2026-06-10T22:07:52+05:30
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

(cherry picked from commit fcf092dda534cc38637d1f7920aa0dae58fe5273)

- - - - -
5974d0a0 by Luite Stegeman at 2026-06-10T22:07:52+05:30
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

(cherry picked from commit 05094993774191ede5c96770d8c91e8235fb922d)

- - - - -
0958d635 by Zubin Duggal at 2026-06-10T22:07:52+05:30
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

(cherry picked from commit bc4b44870d096d43e8cbc530da1fd613d9e4514f)

- - - - -
6b5165cc by Simon Peyton Jones at 2026-06-10T22:07:52+05:30
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

(cherry picked from commit 3eaac1f2b549a1e8788ab98c061391ce39ee18de)

- - - - -
39764f2c by Andreas Klebinger at 2026-06-10T22:07:52+05:30
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

(cherry picked from commit 28ce1f8afb9dd74bc39148a36f5bf61f8bffdcc6)

- - - - -
c6b091d8 by Matthew Pickering at 2026-06-10T22:07:52+05:30
Make home unit dependencies stored as sets

Co-authored-by: Wolfgang Jeltsch <wolfgang@well-typed.com>
(cherry picked from commit d17d1435d1ac1f1e4f806181da944ec541e79d19)

- - - - -
6efed76c by Zubin Duggal at 2026-06-10T22:07:53+05:30
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

(cherry picked from commit 07267f79d91169f474cacc8bcd38d76a6e97887d)

- - - - -
46f93fbd by Simon Jakobi at 2026-06-10T22:07:53+05:30
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.

(cherry picked from commit 5b82080a3f3dd476e198130218d4da729fb5334a)

- - - - -
7ca13903 by sheaf at 2026-06-10T22:07:53+05:30
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
-------------------------

(cherry picked from commit e8a196c65cee32f06c3d99b74af33457511408c7)

- - - - -
f7ceb7fa by Rodrigo Mesquita at 2026-06-10T22:07:53+05:30
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
-------------------------

(cherry picked from commit 5bd6a96485ff9bfcbf06eaec69776bf8af61b563)

- - - - -
596c4ec8 by Rodrigo Mesquita at 2026-06-10T22:07:53+05:30
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

(cherry picked from commit ce97fd3ed13028034ba27c34a6decdb3460aa4eb)

- - - - -
9835948b by Wolfgang Jeltsch at 2026-06-10T22:07:53+05:30
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>
(cherry picked from commit 5fab22387a66657e5e19f1ba490f09af1168eb06)

- - - - -
df410e5a by Cheng Shao at 2026-06-10T22:07:53+05:30
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.

(cherry picked from commit 38b76b2f1d918f10d2f9d3e57bd0459dfe671d4f)

- - - - -
93811d82 by Ian Duncan at 2026-06-10T22:07:53+05:30
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.

(cherry picked from commit 50188615342098345fc2822ea223ab23791bbf49)

- - - - -
f4afeba1 by fendor at 2026-06-10T22:07:53+05:30
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.

(cherry picked from commit 286f1adff3e78d775ff325caff71d0cee25d710b)

- - - - -
18b5da32 by fendor at 2026-06-10T22:07:53+05:30
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.

(cherry picked from commit 728662de2084069ef53bd5adf2c0e8b1e8814bc0)

- - - - -
f1d9b476 by fendor at 2026-06-10T22:07:53+05:30
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.

(cherry picked from commit 50e999cae0297be156d3cc6a683fc3c7634428f0)

- - - - -
632be513 by Cheng Shao at 2026-06-10T22:07:53+05:30
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.

(cherry picked from commit cccf45da01988801b0c97f7e7ed0160191980226)

- - - - -
6636f01f by sheaf at 2026-06-10T22:07:53+05:30
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

(cherry picked from commit 52c3e6ba9f03d19a4fa85aee6a4c417b538160f7)

- - - - -
b30f3ac1 by sheaf at 2026-06-10T22:07:53+05:30
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

(cherry picked from commit 2da84b7a83f723dc6531cdad5ef3c7e624fda2fe)

- - - - -
87dd2d36 by Simon Peyton Jones at 2026-06-10T22:07:53+05:30
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

(cherry picked from commit 269c4087979ff9d675cd1a59076157211d1c555d)

- - - - -
687e7798 by Simon Peyton Jones at 2026-06-10T22:07:53+05:30
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.

(cherry picked from commit 231adc30be97ae51650aff7a40e00e05f4876af6)

- - - - -
8ed7a710 by Zubin Duggal at 2026-06-10T22:07:53+05:30
Revert "docs: note #26543 in known bugs"

This reverts commit ebc6d49bd309bb843bc58e8c712ade767818e9ac.

Obsolete now that the fix from MR 14474 (commit 231adc30) is backported.

- - - - -
ae07c290 by Luite Stegeman at 2026-06-10T22:07:53+05:30
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.

(cherry picked from commit 404b71c181bde4256565307d495cd2fa124d02f1)

- - - - -
a4070057 by Ben Gamari at 2026-06-10T22:07:53+05:30
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.

(cherry picked from commit d2b89603425b6d08df199deb7b84cfdbd711869a)

- - - - -
7f0a32b8 by Luite Stegeman at 2026-06-10T22:07:53+05:30
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

(cherry picked from commit a85bd503a480cfa31f5afa09eb38f56c85c237de)

- - - - -
8e8e3d32 by Luite Stegeman at 2026-06-10T22:07:53+05:30
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.

(cherry picked from commit e2209031734770a51f04883e5b538b562449cba1)

- - - - -
5648f3e2 by Luite Stegeman at 2026-06-10T22:07:53+05:30
rts: add a few missing i386 relocations in the rts linker

(cherry picked from commit 04d143c02e82e9ca03eb75849959d369d07fb81a)

- - - - -
4ec0815f by Luite Stegeman at 2026-06-10T22:07:53+05:30
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

(cherry picked from commit 014087e7a5753687161a24a1b2bc55c7bf7273fd)

- - - - -
14948642 by Ben Gamari at 2026-06-10T22:07:53+05:30
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.

(cherry picked from commit 039bac4cf9590a6a09aa302b99fa2a0993cc0a32)

- - - - -
6d624f5f by Ben Gamari at 2026-06-10T22:07:53+05:30
base: Capture backtrace from throwSTM

Implements core-libraries-committee#297.

Fixes #25365.

(cherry picked from commit 8c389e8ce9a536da8e396a1df8c726583d0bcc14)

- - - - -
154a4b5b by Ben Gamari at 2026-06-10T22:07:54+05:30
base: Annotate rethrown exceptions in catchSTM with WhileHandling

Implements core-libraries-committee#298

(cherry picked from commit e1ce1fc3ad38d192cd3b6a38cb42051f4b115e95)

- - - - -
a549dfd6 by fendor at 2026-06-11T09:36:54+05:30
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)

(cherry picked from commit 016f79d54d482de01dd396bd9bf79f958d7c4922)

- - - - -
07e10c56 by sheaf at 2026-06-11T09:36:54+05:30
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.

(cherry picked from commit b0233814d63c2802a521dfc7dae08b1ecf494c50)
- - - - -
c7f02460 by mangoiv at 2026-06-11T09:36:54+05:30
libraries/process: bump submodule to v1.6.29.0

This submodule bump resolves a segfault on macos 15.
Fixes #27144

(cherry picked from commit 277a3687c4b729e4d1ff4d4503a5673deba5eda7)
- - - - -
8206e59b by mangoiv at 2026-06-11T09:36:54+05:30
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.

(cherry picked from commit 6779bb0c2d2784182465337ba5e94b7cd8810f2b)
- - - - -
19c9c327 by Luite Stegeman at 2026-06-11T09:36:54+05:30
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

(cherry picked from commit 63ce5770da1712f0da54665d8755772bf38ba51e)
- - - - -
e4e0b611 by Tom McLaughlin at 2026-06-11T09:36:54+05:30
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.

(cherry picked from commit 037a80dc65d3975adf4a35d46876850e644bc80e)
- - - - -
d2e47026 by Zubin Duggal at 2026-06-11T09:36:54+05:30
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

(cherry picked from commit 8db331a381ae47ad9ad5c8613f5d3e2588d5dd55)
- - - - -
4cec40ed by mangoiv at 2026-06-11T09:36:54+05:30
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.

This patch was rewritten to avoid pulling in a refactor.
The original patch is included in master as 4a645683

(cherry picked from commit 53f74985860b35a879bfd0dc642e7fcafffcf5e4)
- - - - -
749824b7 by mangoiv at 2026-06-11T09:36:54+05:30
profiling: partial backport of 2dadf3b0 to fix #27121

This backports fix and test for #27121 from 2dadf3b0 since the entirety
of the patch is not backportable without also backporting two larger
refactorings.

(cherry picked from commit 0ccecfc5b5a118c2c850f876709c21162d35d972)
- - - - -
be9b07ad by Teo Camarasu at 2026-06-11T09:36:54+05:30
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

(cherry picked from commit b14bdd59202e0c32df8e5cc1923677f59c8f16e7)
- - - - -
a664ed30 by Teo Camarasu at 2026-06-11T09:36:54+05:30
base: deprecate GHC internals in GHC.Num

Implements CLC proposal: https://github.com/haskell/core-libraries-committee/issues/360

(cherry picked from commit 75a9053d26183e71b48de4c603b04af2fa4a732d)
- - - - -
1ee3466b by Simon Peyton Jones at 2026-06-11T09:36:54+05:30
Add a deprecation warning for static forms

The accepted
  GHC proposal 732: Simplify static forms
  https://github.com/ghc-proposals/ghc-proposals/pull/732

needs a deprecation warning added to GHC 9.14, to warn about static
forms that mention nested free variables; see #26718.

This MR adds that warning, with test T26718 to check it.

There is no flag to switch the warning off.

(cherry picked from commit 6b7d6287c6ff4fd1b0d3aa2abfdaf73d43c4a9a0)
- - - - -
8e260c6a by Cheng Shao at 2026-06-11T09:36:54+05:30
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.

(cherry picked from commit de54e264c3c87c21e4243c2e9a402923ec7d9d6e)

- - - - -
08c99230 by Cheng Shao at 2026-06-11T09:36:54+05:30
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.

(cherry picked from commit da946a16575a3b261206b75ce958b90b86a5e801)

- - - - -
c77b77e7 by Simon Hengel at 2026-07-15T16:39:36+05:30
Refactor GHC.Driver.Errors.printMessages

(cherry picked from commit 49a44ab79d644590abdeff8699406bbd2d310715)

- - - - -
704f7368 by Simon Hengel at 2026-07-15T16:40:59+05:30
Include the rendered message in -fdiagnostics-as-json output

This implements #26173.

(cherry picked from commit d046b5ab146167bcb86c675d101ff5e3c4eb8c8e)

- - - - -
6850cb8f by fendor at 2026-07-15T16:41:10+05:30
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.

(cherry picked from commit 8f9917557a7ef290dfa8b913c3a4146289586ec6)

- - - - -
41ecaadd by sheaf at 2026-07-15T16:44:19+05:30
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

(cherry picked from commit c9015f0953e72829e89ac768b6ad9ece34c7e187)

- - - - -
985b0e36 by mangoiv at 2026-07-15T16:44:19+05:30
libraries/process: bump submodule to v1.6.30.0

- bump the submodule to the appropriate tag
- suppress benign warning resulting from the change

(cherry picked from commit d9ea2d76545452a7df567b162340079cb024a40c)

- - - - -
16e9f578 by ARATA Mizuki at 2026-07-15T16:44:19+05:30
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

(cherry picked from commit 291ce3aafe4ca3d2562154a28c595a858987d9f1)

- - - - -
c16871c9 by ARATA Mizuki at 2026-07-15T16:44:19+05:30
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

(cherry picked from commit 011be91fdaa7869dff2f30b8f2ecca3c9a713739)

- - - - -
d8f0999a by ARATA Mizuki at 2026-07-15T16:44:20+05:30
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

(cherry picked from commit e8a547133031b7de8f6f9bbd70a7148eda0941ee)

- - - - -
bfcd8dfc by Zubin Duggal at 2026-07-15T16:44:20+05:30
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=ccead81bbc39668376eb5cf47066ac...

Fixes #27366

(cherry picked from commit 9438bec7117433bbc70449d4288f6ee32dbbbec4)

- - - - -
275a0382 by Ian Duncan at 2026-07-15T16:44:54+05:30
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

(cherry picked from commit 636c1c7ae47495f022affa501ea0a40cb55cd4a4)

- - - - -
dec52356 by Luite Stegeman at 2026-07-15T16:46:04+05:30
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

(cherry picked from commit 7fe4f2ec3ce12ea138177c81a019dcfc148fe5d4)

- - - - -
a40f21b5 by Sebastian Graf at 2026-07-15T16:47:03+05:30
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
(cherry picked from commit 67d41299be96798702377e6e2b826f9c8e070821)

- - - - -
46dfc982 by mangoiv at 2026-07-15T16:48:09+05:30
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

(cherry picked from commit c64cca1ef667751c02ce2eb4141349e601aac99c)

- - - - -
e757591a by Simon Hengel at 2026-07-27T15:14:26+05:30
Reference correct package in error messages for reexported modules

(fixes #27417)

(cherry picked from commit a805b2a25021606b30d250e084d4beecbfac0d0a)

- - - - -
fba13ef3 by Luite Stegeman at 2026-07-27T15:14:33+05:30
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

(cherry picked from commit cca0d58963f802a8b2e43aa2dbc58592f8ad07bb)

- - - - -
0500851f by Cheng Shao at 2026-07-27T15:14:33+05:30
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>
(cherry picked from commit 3f00f234d0d5b3b3b2a23a5dc70ce372eb9bbdb4)

- - - - -
31af42e7 by Cheng Shao at 2026-07-27T15:14:33+05:30
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-s...),
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>
(cherry picked from commit 3c0013778b4459c1f8e56cd0dc2600f5bb3769d2)

- - - - -
a56fcdee by mangoiv at 2026-07-27T15:14:33+05:30
ci: retry fetching test metrics

Retry fetching test metrics to make the CI not fail if the services is
temporarily unavailable

(cherry picked from commit b7e24044fde064cb3f0d44c36872a86d024cd7d4)

- - - - -
03e870e1 by Zubin Duggal at 2026-07-27T15:14:33+05:30
Bump semaphore-compat submodule to 2.0.1

This versions includes some cruicial fixes for darwin

(cherry picked from commit 4180af3f71754472dbd49b85179b25fd29bd9998)

- - - - -
1eb8f64b by Zubin Duggal at 2026-07-27T15:14:33+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

(cherry picked from commit 9b714c4c833461c621f0a050680848d7248aa57e)

- - - - -
843e7885 by Zubin Duggal at 2026-07-27T15:14:33+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

(cherry picked from commit 4a59b3eece9b7106fcbe73d2d06a49755be4ea8f)

- - - - -
e8f1b190 by Andreas Klebinger at 2026-07-27T15:14:33+05:30
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.

(cherry picked from commit ed09895d7de1ca116a561868c151fd825a16ad0c)

- - - - -
f1cfd0f4 by Cheng Shao at 2026-07-27T15:14:33+05:30
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>
(cherry picked from commit 67c03eb2c762fdfeb646eb8345341173dd4268b2)

- - - - -
ed840c99 by Cheng Shao at 2026-07-27T15:14:33+05:30
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>
(cherry picked from commit eee8ec5b25ef0f83ba4822e7a0a941df7b0bec5f)

- - - - -
fc129385 by Cheng Shao at 2026-07-27T15:14:33+05:30
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>
(cherry picked from commit d377e83e51d39a06e1f0bf2e35a923a3210b21a2)

- - - - -
2e023223 by Cheng Shao at 2026-07-27T15:14:33+05:30
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>
(cherry picked from commit 8ed038421a20e3e4e681973b2f5098e5bd2144b5)

- - - - -
a52c471f by Cheng Shao at 2026-07-27T15:14:33+05:30
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>
(cherry picked from commit 5aa7000ae246ae6a706437799338295b5801a629)

- - - - -
d26793ae by sheaf at 2026-07-27T15:14:33+05:30
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

(cherry picked from commit f9bcfac2e92457128f5c82dea181edcd0baf7eef)

- - - - -
34061ece by sheaf at 2026-07-27T15:14:33+05:30
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
-------------------------

(cherry picked from commit ce01ccb625514a09e76aded549691da4dfe87de7)

- - - - -
e908040d by sheaf at 2026-07-27T15:14:33+05:30
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

(cherry picked from commit 473b97ebc742305f56e30d5b1bbf95b7681312f0)

- - - - -
6bdf75ab by Ian-Woo Kim at 2026-07-27T15:14:33+05:30
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>
(cherry picked from commit d216412babfd5b5746365f0686ec370fb0892ec7)

- - - - -
6382e45c by Wolfgang Jeltsch at 2026-07-27T15:14:33+05:30
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.

(cherry picked from commit 8e1cc105acae69b1fabd1a9b89e2d1823861f518)

- - - - -
a8cb9679 by Andrea Vezzosi at 2026-07-27T15:14:33+05:30
[Fix #27287] preserve ModBreaks in ModIface

(cherry picked from commit 4396a6f2a4c7799908e1e0b88a218a51d063fdca)

- - - - -
14691377 by mangoiv at 2026-07-27T15:14:33+05:30
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

(cherry picked from commit 141986e3680a24b76e21a7ad4ce6290a7413c7f5)

- - - - -
d3099986 by mangoiv at 2026-07-27T15:14:33+05:30
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>
(cherry picked from commit a72ff58fa86172b1557e405f7246d27914fdae6e)

- - - - -
8ad5f8f7 by Zubin Duggal at 2026-07-27T15:14:33+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

(cherry picked from commit 5ac9ce7d3821c75e2d2cc17fae00b9e865a02987)

- - - - -
1b612594 by Zubin Duggal at 2026-07-27T15:14:33+05:30
testsuite: disable git auto-gc when fetching perf notes

Otherwise the message it prints breaks the parsing

- - - - -
7f030f76 by Sylvain Henry at 2026-07-27T18:52:57+05:30
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.

(cherry picked from commit c9fa3449d78f4fe690acf26a57b1e338a2d580da)

- - - - -
2ee8bc10 by Sylvain Henry at 2026-07-27T18:52:57+05:30
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.

(cherry picked from commit 9e46990976193d71686b070cd4c5d9c7aad43cf2)

- - - - -
d68d81d4 by Andreas Klebinger at 2026-07-28T12:09:45+05:30
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

(cherry picked from commit 01ecb61234b03b94d08ab649395e2da074a4f9d3)

- - - - -
9d33043b by Zubin Duggal at 2026-07-28T12:09:45+05:30
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

(cherry picked from commit f6f2343fbbfdfd8aaed9babf5983e3e24c08ca85)

- - - - -
bf41f75d by Zubin Duggal at 2026-07-28T12:09:45+05:30
hadrian: need libffi before linking the dynamic rts

The rts link passes -lffi but never needed libffi.
Whether the build succeeded or not was a race depending on
if we managed to copy the libary before the link.

- - - - -
cae07835 by Zubin Duggal at 2026-07-28T15:18:03+05:30
test-primops: Switch to the 9.14 branch so we don't try to build on platforms
that GHC 9.14 is not built for. Use the commit instead of the branch so that
it is pinned.

- - - - -
b0fc1bd4 by Zubin Duggal at 2026-07-29T03:06:33+05:30
hadrian: add text and parsec to stage0Packages

text depends on template-haskell-lift, and template-haskell-lift needs to be
built in tree rather than using the boot package, so `text` and `parsec` (which
depends on `text`) must also be built in tree rather than copied from the boot
pkgdb.

Also need to disable -simdutf for text when building the stage0 version, wasm backend
doesn't like -simdutf.

- - - - -
eddff3ab by Zubin Duggal at 2026-07-29T03:06:33+05:30
Prepare 9.14.2

Bump filpath submodule to 1.5.5.0
Bump Win32 submodule to 2.14.2.2

Metric Increase:
    T4029
    T13379
    haddock.base
    libdir

Metric Decrease:
    T5030
    T24602_perf_size
    T25046_perf_size_gzip
    T25046_perf_size_unicode
    T25046_perf_size_unicode_gzip

- - - - -
a94272d2 by Zubin Duggal at 2026-07-29T15:06:09+05:30
ci/test-primops: use branch instead of commit hash

apparently gitlab doesn't like commit hashes in this field

- - - - -
39bc70bd by Zubin Duggal at 2026-07-29T15:06:48+05:30
releng: release script fixes

Also fetch the freebsd job

Fix download site url

- - - - -

872 changed files:

- .gitlab-ci.yml
- .gitlab/generate-ci/gen_ci.hs
- .gitlab/jobs.yaml
- .gitlab/rel_eng/fetch-gitlab-artifacts/fetch_gitlab.py
- .gitlab/rel_eng/upload.sh
- .gitlab/rel_eng/upload_ghc_libs.py
- .gitlab/test-metrics.sh
- .gitmodules
- compiler/GHC.hs
- compiler/GHC/Builtin/Names.hs
- compiler/GHC/Builtin/PrimOps.hs
- compiler/GHC/Builtin/Types.hs
- compiler/GHC/Builtin/Utils.hs
- compiler/GHC/Builtin/primops.txt.pp
- compiler/GHC/ByteCode/Asm.hs
- compiler/GHC/ByteCode/Breakpoints.hs
- compiler/GHC/ByteCode/Instr.hs
- compiler/GHC/ByteCode/Linker.hs
- compiler/GHC/ByteCode/Types.hs
- compiler/GHC/Cmm.hs
- compiler/GHC/Cmm/InitFini.hs
- compiler/GHC/Cmm/LayoutStack.hs
- compiler/GHC/Cmm/Opt.hs
- compiler/GHC/Cmm/Parser.y
- compiler/GHC/Cmm/Sink.hs
- compiler/GHC/CmmToAsm/AArch64/CodeGen.hs
- compiler/GHC/CmmToAsm/AArch64/Instr.hs
- compiler/GHC/CmmToAsm/AArch64/Ppr.hs
- compiler/GHC/CmmToAsm/PPC/CodeGen.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/SpillCost.hs
- compiler/GHC/CmmToAsm/Reg/Linear.hs
- compiler/GHC/CmmToAsm/Reg/Linear/Base.hs
- compiler/GHC/CmmToAsm/Reg/Linear/JoinToTargets.hs
- compiler/GHC/CmmToAsm/Reg/Linear/StackMap.hs
- compiler/GHC/CmmToAsm/Reg/Liveness.hs
- + compiler/GHC/CmmToAsm/Reg/Regs.hs
- compiler/GHC/CmmToAsm/Reg/Target.hs
- compiler/GHC/CmmToAsm/Wasm/FromCmm.hs
- compiler/GHC/CmmToAsm/X86/CodeGen.hs
- compiler/GHC/CmmToAsm/X86/Instr.hs
- compiler/GHC/CmmToAsm/X86/Ppr.hs
- compiler/GHC/CmmToC.hs
- compiler/GHC/CmmToLlvm.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/Lint.hs
- compiler/GHC/Core/Make.hs
- compiler/GHC/Core/Map/Type.hs
- compiler/GHC/Core/Opt/Arity.hs
- compiler/GHC/Core/Opt/DmdAnal.hs
- compiler/GHC/Core/Opt/OccurAnal.hs
- compiler/GHC/Core/Opt/Pipeline/Types.hs
- compiler/GHC/Core/Opt/SetLevels.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/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/Rules.hs
- compiler/GHC/Core/TyCon.hs
- compiler/GHC/Core/Type.hs
- compiler/GHC/Core/Unfold.hs
- compiler/GHC/Core/Utils.hs
- compiler/GHC/CoreToStg/Prep.hs
- compiler/GHC/Data/OsPath.hs
- compiler/GHC/Driver/Backpack.hs
- compiler/GHC/Driver/CodeOutput.hs
- compiler/GHC/Driver/Config/CmmToLlvm.hs
- compiler/GHC/Driver/Config/Core/Lint.hs
- compiler/GHC/Driver/Config/Core/Opt/Simplify.hs
- compiler/GHC/Driver/Config/Finder.hs
- compiler/GHC/Driver/Config/StgToCmm.hs
- compiler/GHC/Driver/Downsweep.hs
- compiler/GHC/Driver/DynFlags.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/Main.hs
- compiler/GHC/Driver/Make.hs
- compiler/GHC/Driver/MakeAction.hs
- compiler/GHC/Driver/MakeSem.hs
- compiler/GHC/Driver/Phases.hs
- compiler/GHC/Driver/Pipeline/Execute.hs
- compiler/GHC/Driver/Session.hs
- compiler/GHC/Hs/Binds.hs
- compiler/GHC/Hs/Doc.hs
- compiler/GHC/Hs/Expr.hs
- compiler/GHC/Hs/Instances.hs
- compiler/GHC/HsToCore/Arrows.hs
- compiler/GHC/HsToCore/Breakpoints.hs
- + compiler/GHC/HsToCore/Breakpoints/Types.hs
- compiler/GHC/HsToCore/Docs.hs
- compiler/GHC/HsToCore/Expr.hs
- compiler/GHC/HsToCore/Foreign/C.hs
- compiler/GHC/HsToCore/Foreign/Wasm.hs
- compiler/GHC/HsToCore/Match.hs
- compiler/GHC/HsToCore/Match.hs-boot
- compiler/GHC/HsToCore/Pmc.hs
- compiler/GHC/HsToCore/Pmc/Solver/Types.hs
- compiler/GHC/HsToCore/Quote.hs
- compiler/GHC/HsToCore/Usage.hs
- compiler/GHC/Iface/Errors.hs
- compiler/GHC/Iface/Errors/Ppr.hs
- compiler/GHC/Iface/Errors/Types.hs
- compiler/GHC/Iface/Load.hs
- compiler/GHC/Iface/Make.hs
- compiler/GHC/Iface/Recomp.hs
- compiler/GHC/Iface/Type.hs
- compiler/GHC/Linker/Loader.hs
- compiler/GHC/Linker/Static.hs
- compiler/GHC/Linker/Types.hs
- compiler/GHC/Parser.y
- compiler/GHC/Rename/Env.hs
- compiler/GHC/Rename/Expr.hs
- compiler/GHC/Rename/HsType.hs
- compiler/GHC/Rename/Module.hs
- compiler/GHC/Rename/Names.hs
- compiler/GHC/Rename/Pat.hs
- compiler/GHC/Rename/Splice.hs
- compiler/GHC/Rename/Splice.hs-boot
- compiler/GHC/Rename/Unbound.hs
- compiler/GHC/Runtime/Interpreter.hs
- compiler/GHC/Runtime/Interpreter/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/StgToByteCode.hs
- compiler/GHC/StgToCmm/Bind.hs
- compiler/GHC/StgToCmm/Config.hs
- compiler/GHC/StgToCmm/Utils.hs
- compiler/GHC/StgToJS/Apply.hs
- compiler/GHC/StgToJS/Expr.hs
- compiler/GHC/StgToJS/Regs.hs
- compiler/GHC/StgToJS/Rts/Rts.hs
- compiler/GHC/StgToJS/Rts/Types.hs
- compiler/GHC/SysTools/Cpp.hs
- compiler/GHC/Tc/Deriv/Generics.hs
- compiler/GHC/Tc/Errors.hs
- compiler/GHC/Tc/Errors/Ppr.hs
- compiler/GHC/Tc/Errors/Types.hs
- compiler/GHC/Tc/Gen/App.hs
- compiler/GHC/Tc/Gen/Export.hs
- compiler/GHC/Tc/Gen/HsType.hs
- compiler/GHC/Tc/Instance/Class.hs
- compiler/GHC/Tc/Solver/Dict.hs
- compiler/GHC/Tc/Solver/Monad.hs
- compiler/GHC/Tc/Types.hs
- compiler/GHC/Tc/Types/Evidence.hs
- compiler/GHC/Tc/Types/Origin.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/TcType.hs
- compiler/GHC/Tc/Utils/Unify.hs
- compiler/GHC/Tc/Zonk/Type.hs
- compiler/GHC/ThToHs.hs
- compiler/GHC/Types/Basic.hs
- compiler/GHC/Types/Demand.hs
- compiler/GHC/Types/Error.hs
- compiler/GHC/Types/Error/Codes.hs
- compiler/GHC/Types/ForeignStubs.hs
- compiler/GHC/Types/Hint.hs
- compiler/GHC/Types/Hint/Ppr.hs
- compiler/GHC/Types/Id/Info.hs
- compiler/GHC/Types/Id/Make.hs
- compiler/GHC/Types/Literal.hs
- compiler/GHC/Types/Name/Reader.hs
- compiler/GHC/Types/RepType.hs
- compiler/GHC/Types/Unique/DFM.hs
- compiler/GHC/Types/Unique/FM.hs
- compiler/GHC/Types/Unique/Set.hs
- compiler/GHC/Types/Var/Env.hs
- compiler/GHC/Unit/Finder.hs
- compiler/GHC/Unit/Finder/Types.hs
- compiler/GHC/Unit/Home/Graph.hs
- compiler/GHC/Unit/Module/Deps.hs
- compiler/GHC/Unit/Module/Graph.hs
- compiler/GHC/Unit/Module/ModGuts.hs
- compiler/GHC/Unit/Module/ModIface.hs
- compiler/GHC/Unit/Module/WholeCoreBindings.hs
- compiler/GHC/Unit/State.hs
- compiler/GHC/Utils/Binary.hs
- compiler/GHC/Utils/Logger.hs
- compiler/GHC/Utils/Misc.hs
- compiler/GHC/Utils/Outputable.hs
- compiler/Language/Haskell/Syntax/Module/Name.hs
- compiler/ghc.cabal.in
- configure.ac
- + docs/users_guide/9.14.2-notes.rst
- docs/users_guide/bugs.rst
- + docs/users_guide/diagnostics-as-json-schema-1_2.json
- docs/users_guide/ghci.rst
- docs/users_guide/release-notes.rst
- docs/users_guide/rtd-theme/layout.html
- docs/users_guide/using-warnings.rst
- docs/users_guide/using.rst
- docs/users_guide/wasm.rst
- ghc/GHCi/UI.hs
- ghc/GHCi/UI/Exception.hs
- ghc/Main.hs
- hadrian/bindist/Makefile
- hadrian/bootstrap/generate_bootstrap_plans
- + hadrian/bootstrap/plan-9_10_3.json
- + hadrian/bootstrap/plan-9_12_4.json
- + hadrian/bootstrap/plan-bootstrap-9_10_3.json
- + hadrian/bootstrap/plan-bootstrap-9_12_4.json
- hadrian/src/Builder.hs
- hadrian/src/CommandLine.hs
- hadrian/src/Context.hs
- hadrian/src/Flavour.hs
- hadrian/src/Hadrian/Haskell/Cabal/Parse.hs
- hadrian/src/Rules/Compile.hs
- hadrian/src/Rules/Documentation.hs
- hadrian/src/Rules/Generate.hs
- hadrian/src/Rules/Library.hs
- hadrian/src/Rules/Register.hs
- hadrian/src/Rules/ToolArgs.hs
- hadrian/src/Settings.hs
- hadrian/src/Settings/Builders/Cabal.hs
- hadrian/src/Settings/Builders/GenPrimopCode.hs
- hadrian/src/Settings/Builders/Ghc.hs
- hadrian/src/Settings/Default.hs
- hadrian/src/Settings/Packages.hs
- hadrian/src/Settings/Warnings.hs
- hie.yaml
- libraries/Cabal
- libraries/Win32
- libraries/base/base.cabal.in
- libraries/base/changelog.md
- libraries/base/src/GHC/Base.hs
- libraries/base/src/GHC/Conc.hs
- libraries/base/src/GHC/Conc/Sync.hs
- libraries/base/src/GHC/Exts.hs
- libraries/base/src/GHC/Num.hs
- libraries/base/src/GHC/Stats.hs
- libraries/base/src/System/Info.hs
- libraries/deepseq
- libraries/directory
- libraries/exceptions
- libraries/filepath
- libraries/ghc-experimental/CHANGELOG.md
- libraries/ghc-experimental/ghc-experimental.cabal.in
- libraries/ghc-experimental/src/GHC/Exception/Backtrace/Experimental.hs
- libraries/ghc-experimental/src/GHC/PrimOps.hs
- libraries/ghc-experimental/src/GHC/Stack/Annotation/Experimental.hs
- + libraries/ghc-experimental/src/GHC/Stack/Decode/Experimental.hs
- + libraries/ghc-experimental/tests/Makefile
- + libraries/ghc-experimental/tests/all.T
- + 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/tests/T27465.hs
- + libraries/ghc-heap/tests/T27465.stdout
- libraries/ghc-heap/tests/all.T
- libraries/ghc-internal/CHANGELOG.md
- libraries/ghc-internal/cbits/Stack.cmm
- libraries/ghc-internal/ghc-internal.cabal.in
- 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/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/Err.hs
- libraries/ghc-internal/src/GHC/Internal/Event/Thread.hs
- libraries/ghc-internal/src/GHC/Internal/Event/Windows.hsc
- libraries/ghc-internal/src/GHC/Internal/Event/Windows/Thread.hs
- libraries/ghc-internal/src/GHC/Internal/Exception.hs
- libraries/ghc-internal/src/GHC/Internal/Heap/InfoTable.hsc
- libraries/ghc-internal/src/GHC/Internal/Heap/InfoTableProf.hsc
- + libraries/ghc-internal/src/GHC/Internal/Prim.hs
- + libraries/ghc-internal/src/GHC/Internal/STM.hs
- libraries/ghc-internal/src/GHC/Internal/Stack/Annotation.hs
- libraries/ghc-internal/src/GHC/Internal/Stack/Decode.hs
- libraries/ghc-internal/src/GHC/Internal/Stats.hsc
- libraries/ghc-internal/src/GHC/Internal/Types.hs
- + libraries/ghc-internal/tests/backtraces/T15395.hs
- + libraries/ghc-internal/tests/backtraces/T15395.stdout
- libraries/ghc-internal/tests/backtraces/all.T
- libraries/ghc-internal/tests/stack-annotation/all.T
- libraries/ghc-internal/tests/stack-annotation/ann_frame001.stdout
- libraries/ghc-internal/tests/stack-annotation/ann_frame002.stdout
- libraries/ghc-internal/tests/stack-annotation/ann_frame003.stdout
- 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/ghci/GHCi/Message.hs
- libraries/ghci/GHCi/Run.hs
- libraries/ghci/GHCi/Server.hs
- libraries/haskeline
- libraries/process
- libraries/semaphore-compat
- libraries/text
- libraries/transformers
- m4/fp_check_pthreads.m4
- m4/fp_prog_cc_linker_target.m4
- m4/fptools_happy.m4
- rts/Apply.cmm
- rts/CloneStack.c
- rts/CloneStack.h
- rts/Compact.cmm
- rts/Continuation.c
- rts/ContinuationOps.cmm
- rts/Exception.cmm
- rts/HeapStackCheck.cmm
- rts/IOManager.c
- rts/Interpreter.c
- rts/Jumps.h
- rts/Linker.c
- rts/LinkerInternals.h
- rts/Messages.c
- rts/PrimOps.cmm
- rts/Printer.c
- rts/RaiseAsync.c
- rts/RtsMessages.c
- rts/RtsSymbols.c
- rts/Schedule.c
- rts/Stats.c
- rts/StgCRun.c
- rts/StgMiscClosures.cmm
- rts/StgStartup.cmm
- rts/ThreadPaused.c
- rts/Threads.c
- rts/Threads.h
- rts/Updates.h
- rts/configure.ac
- rts/eventlog/EventLog.c
- rts/include/RtsAPI.h
- rts/include/rts/Bytecodes.h
- rts/include/rts/Constants.h
- rts/include/rts/Messages.h
- rts/include/rts/storage/ClosureMacros.h
- rts/include/rts/storage/Closures.h
- rts/include/rts/storage/TSO.h
- rts/include/stg/MiscClosures.h
- rts/linker/Elf.c
- rts/linker/LoadArchive.c
- rts/linker/MachO.c
- rts/linker/PEi386.c
- rts/prim/atomic.c
- + rts/rts.buildinfo.in
- rts/rts.cabal
- rts/sm/Compact.c
- rts/sm/Evac.c
- rts/sm/Evac.h
- rts/sm/Evac_thr.c → rts/sm/Evac_par.c
- rts/sm/Scav_thr.c → rts/sm/Scav_par.c
- rts/win32/AsyncMIO.c
- rts/win32/AsyncMIO.h
- testsuite/driver/perf_notes.py
- testsuite/driver/runtests.py
- testsuite/driver/testlib.py
- testsuite/driver/testutil.py
- testsuite/mk/boilerplate.mk
- 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/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/arrows/should_compile/T21301.stderr
- + 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/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/cmm/opt/T25664.hs
- + testsuite/tests/cmm/opt/T25664.stdout
- testsuite/tests/cmm/opt/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_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_run/CgStaticPointers.hs
- testsuite/tests/codeGen/should_run/CgStaticPointersNoFullLazyness.hs
- testsuite/tests/codeGen/should_run/T16617.hs
- testsuite/tests/codeGen/should_run/T16617.stdout
- + 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/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/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/all.T
- testsuite/tests/core-to-stg/T14895.stderr
- + 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/count-deps/CountDepsAst.stdout
- testsuite/tests/count-deps/CountDepsParser.stdout
- + testsuite/tests/deSugar/should_compile/T27383.hs
- testsuite/tests/deSugar/should_compile/all.T
- testsuite/tests/deSugar/should_fail/DsStrictFail.stderr
- testsuite/tests/deSugar/should_run/T20024.stderr
- testsuite/tests/deSugar/should_run/dsrun005.stderr
- testsuite/tests/deSugar/should_run/dsrun007.stderr
- testsuite/tests/deSugar/should_run/dsrun008.stderr
- testsuite/tests/default/default-fail05.stderr
- testsuite/tests/deriving/should_run/T9576.stderr
- testsuite/tests/diagnostic-codes/codes.stdout
- testsuite/tests/dmdanal/should_compile/T13143.stderr
- testsuite/tests/dmdanal/should_compile/T18894.stderr
- testsuite/tests/dmdanal/should_compile/T18982.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/all.T
- testsuite/tests/dmdanal/sigs/T21081.stderr
- testsuite/tests/driver/fat-iface/fat014.stdout
- testsuite/tests/driver/json.stderr
- testsuite/tests/driver/json_warn.stderr
- + 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/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/all.T
- + testsuite/tests/ghc-api/TypeMapStringLiteral.hs
- testsuite/tests/ghc-api/all.T
- testsuite/tests/ghci.debugger/scripts/T26042b.stdout
- testsuite/tests/ghci.debugger/scripts/T26042c.stdout
- testsuite/tests/ghci.debugger/scripts/T26042d2.stdout
- testsuite/tests/ghci.debugger/scripts/T26042f2.stdout
- testsuite/tests/ghci.debugger/scripts/T8487.stdout
- testsuite/tests/ghci.debugger/scripts/break011.stdout
- testsuite/tests/ghci.debugger/scripts/break017.stdout
- testsuite/tests/ghci.debugger/scripts/break025.stdout
- testsuite/tests/ghci/T16793/T16793.stdout
- testsuite/tests/ghci/T18060/T18060.stdout
- + testsuite/tests/ghci/T27532/Makefile
- + testsuite/tests/ghci/T27532/T27532.script
- + testsuite/tests/ghci/T27532/T27532.stdout
- + testsuite/tests/ghci/T27532/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/prog-mhu005/Makefile
- testsuite/tests/ghci/prog-mhu005/all.T
- + 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-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/prog003/prog003.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/prog022/Makefile
- testsuite/tests/ghci/prog022/all.T
- + 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/scripts/Defer02.stderr
- testsuite/tests/ghci/scripts/ListTuplePunsPpr.stdout
- testsuite/tests/ghci/scripts/T13997.stdout
- testsuite/tests/ghci/scripts/T15325.stderr
- testsuite/tests/ghci/scripts/T1914.stdout
- testsuite/tests/ghci/scripts/T20217.stdout
- testsuite/tests/ghci/scripts/T4175.stdout
- testsuite/tests/ghci/scripts/T8042.stdout
- testsuite/tests/ghci/scripts/T8042recomp.stdout
- testsuite/tests/ghci/scripts/T8469.stdout
- testsuite/tests/ghci/scripts/T8535.stdout
- testsuite/tests/ghci/scripts/T9881.stdout
- testsuite/tests/ghci/scripts/ghci020.stdout
- testsuite/tests/ghci/scripts/ghci064.stdout
- testsuite/tests/ghci/should_run/Makefile
- testsuite/tests/ghci/should_run/T10145.stdout
- testsuite/tests/ghci/should_run/T10920.stderr
- testsuite/tests/ghci/should_run/T18594.stdout
- + testsuite/tests/ghci/should_run/T27287.hs
- + testsuite/tests/ghci/should_run/T27287.stdout
- testsuite/tests/ghci/should_run/all.T
- testsuite/tests/indexed-types/should_fail/T1897b.stderr
- testsuite/tests/interface-stability/base-exports.stdout
- testsuite/tests/interface-stability/base-exports.stdout-javascript-unknown-ghcjs
- testsuite/tests/interface-stability/base-exports.stdout-mingw32
- testsuite/tests/interface-stability/base-exports.stdout-ws-32
- testsuite/tests/interface-stability/ghc-experimental-exports.stdout
- testsuite/tests/interface-stability/ghc-experimental-exports.stdout-mingw32
- testsuite/tests/interface-stability/ghc-prim-exports.stdout
- testsuite/tests/interface-stability/ghc-prim-exports.stdout-mingw32
- + testsuite/tests/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/jsffi/all.T
- + testsuite/tests/jsffi/bytearrayarg.hs
- + testsuite/tests/jsffi/bytearrayarg.mjs
- + testsuite/tests/jsffi/bytearrayarg.stdout
- testsuite/tests/linters/all.T
- testsuite/tests/linters/notes.stdout
- testsuite/tests/linters/regex-linters/check-rts-includes.py
- + testsuite/tests/llvm/should_run/T26065.hs
- + testsuite/tests/llvm/should_run/T26065.stdout
- testsuite/tests/llvm/should_run/all.T
- testsuite/tests/numeric/should_run/all.T
- + testsuite/tests/overloadedrecflds/should_compile/T26686.hs
- + testsuite/tests/overloadedrecflds/should_compile/T26686.stderr
- testsuite/tests/overloadedrecflds/should_compile/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/all.T
- testsuite/tests/partial-sigs/should_compile/ExtraConstraints3.stderr
- testsuite/tests/patsyn/should_run/ghci.stderr
- testsuite/tests/perf/compiler/Makefile
- testsuite/tests/perf/compiler/T11068.stdout
- + testsuite/tests/perf/compiler/T26425.hs
- testsuite/tests/perf/compiler/T4007.stdout
- testsuite/tests/perf/compiler/all.T
- testsuite/tests/perf/compiler/genMultiComp.py
- testsuite/tests/perf/should_run/all.T
- testsuite/tests/plugins/Makefile
- + 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/pmcheck/should_compile/T11303.hs
- testsuite/tests/pmcheck/should_compile/T12957.stderr
- + 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/callstack001.stdout
- testsuite/tests/profiling/should_run/scc001.prof.sample
- testsuite/tests/profiling/should_run/staticcallstack002.stdout
- testsuite/tests/quasiquotation/qq001/qq001.stderr
- testsuite/tests/quasiquotation/qq002/qq002.stderr
- testsuite/tests/quasiquotation/qq003/qq003.stderr
- testsuite/tests/quasiquotation/qq004/qq004.stderr
- testsuite/tests/quotes/LiftErrMsg.stderr
- testsuite/tests/quotes/LiftErrMsgDefer.stderr
- testsuite/tests/quotes/LiftErrMsgTyped.stderr
- testsuite/tests/quotes/T10384.stderr
- testsuite/tests/quotes/T5721.stderr
- testsuite/tests/quotes/TH_localname.stderr
- testsuite/tests/rename/should_fail/RnStaticPointersFail01.stderr
- testsuite/tests/rename/should_fail/RnStaticPointersFail03.stderr
- testsuite/tests/rep-poly/RepPolyRightSection.stderr
- testsuite/tests/roles/should_compile/Roles14.stderr
- testsuite/tests/roles/should_compile/Roles3.stderr
- testsuite/tests/roles/should_compile/Roles4.stderr
- testsuite/tests/roles/should_compile/T8958.stderr
- + 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/all.T
- + testsuite/tests/rts/cloneThreadStackMigrating.hs
- testsuite/tests/rts/linker/Makefile
- + 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/safeHaskell/safeLanguage/SafeLang15.stderr
- testsuite/tests/showIface/DocsInHiFile1.stdout
- testsuite/tests/showIface/HaddockSpanIssueT24378.stdout
- testsuite/tests/showIface/MagicHashInHaddocks.stdout
- + 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/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/simplCore/should_compile/Makefile
- testsuite/tests/simplCore/should_compile/T13156.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/T21391.hs
- + testsuite/tests/simplCore/should_compile/T26323b.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/T26826.hs
- + testsuite/tests/simplCore/should_compile/T26903.hs
- + testsuite/tests/simplCore/should_compile/T26903.stderr
- + testsuite/tests/simplCore/should_compile/T27261.hs
- + testsuite/tests/simplCore/should_compile/T27261_aux.hs
- testsuite/tests/simplCore/should_compile/T4201.stdout
- testsuite/tests/simplCore/should_compile/all.T
- + 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/all.T
- 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/splice-imports/SI03.stderr
- testsuite/tests/splice-imports/SI05.stderr
- 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/T26088.stderr
- + testsuite/tests/splice-imports/T26088A.hs
- + testsuite/tests/splice-imports/T26088B.hs
- testsuite/tests/splice-imports/T26090.stderr
- + testsuite/tests/splice-imports/T26616.hs
- + testsuite/tests/splice-imports/T26616.stderr
- testsuite/tests/splice-imports/all.T
- 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/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/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/T5795.stderr
- testsuite/tests/th/all.T
- testsuite/tests/type-data/should_run/T22332a.stderr
- testsuite/tests/typecheck/should_compile/T18406b.stderr
- testsuite/tests/typecheck/should_compile/T18529.stderr
- testsuite/tests/typecheck/should_compile/T26225.hs
- + testsuite/tests/typecheck/should_compile/T26350.hs
- + testsuite/tests/typecheck/should_compile/T26451.hs
- + testsuite/tests/typecheck/should_compile/T26718.hs
- + testsuite/tests/typecheck/should_compile/T26718.stderr
- testsuite/tests/typecheck/should_compile/all.T
- testsuite/tests/typecheck/should_fail/T13292.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/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/T5300.stderr
- testsuite/tests/typecheck/should_fail/all.T
- testsuite/tests/typecheck/should_run/T10284.stderr
- testsuite/tests/typecheck/should_run/T13838.stderr
- testsuite/tests/typecheck/should_run/T9497a-run.stderr
- testsuite/tests/typecheck/should_run/T9497b-run.stderr
- testsuite/tests/typecheck/should_run/T9497c-run.stderr
- testsuite/tests/unsatisfiable/T23816.stderr
- testsuite/tests/unsatisfiable/UnsatDefer.stderr
- utils/check-exact/ExactPrint.hs
- utils/deriveConstants/Main.hs
- utils/genapply/Main.hs
- utils/genprimopcode/Main.hs
- utils/ghc-pkg/Main.hs
- utils/jsffi/post-link.mjs
- utils/jsffi/prelude.mjs

The diff was not included because it is too large.

View it on GitLab: https://gitlab.haskell.org/ghc/ghc/-/compare/8fb179ea934766f4390947ef198d163...

-- 
View it on GitLab: https://gitlab.haskell.org/ghc/ghc/-/compare/8fb179ea934766f4390947ef198d163...
You're receiving this email because of your account on gitlab.haskell.org. Manage all notifications: https://gitlab.haskell.org/-/profile/notifications | Help: https://gitlab.haskell.org/help

[Git][ghc/ghc][ghc-9.14] 204 commits: template haskell: use a precise condition when implicitly lifting

Zubin (＠wz1000)