GHC issueshttps://gitlab.haskell.org/ghc/ghc/-/issues2024-03-12T14:43:09Zhttps://gitlab.haskell.org/ghc/ghc/-/issues/24524ghc-heap doesn't allow containers 0.72024-03-12T14:43:09ZDavid Feuerghc-heap doesn't allow containers 0.7## Summary
We can't run the `containers` tests with the `containers` version set to 0.7 because `ghc-heap` imposes an upper bound below that.
Optional:
* Operating System:
* System Architecture:## Summary
We can't run the `containers` tests with the `containers` version set to 0.7 because `ghc-heap` imposes an upper bound below that.
Optional:
* Operating System:
* System Architecture:Ben GamariBen Gamarihttps://gitlab.haskell.org/ghc/ghc/-/issues/23180Fix memory ordering of ghc-heap2023-03-25T16:27:01ZBen GamariFix memory ordering of ghc-heap`ghc-heap` currently makes no attempt to ensure that heap object accesses are concurrency safe. We need to address this.`ghc-heap` currently makes no attempt to ensure that heap object accesses are concurrency safe. We need to address this.Ben GamariBen Gamarihttps://gitlab.haskell.org/ghc/ghc/-/issues/16564Make ghc-heap multi-platform2019-10-03T03:14:20ZJohn EricsonMake ghc-heap multi-platform# Motivation
It's been my long-standing goal that GHC should be as target-agnostic as possible. ghc-heap is very low priority on this list, as it can be construed as "target agnostic but host specific" already (i.e. it tells you about i...# Motivation
It's been my long-standing goal that GHC should be as target-agnostic as possible. ghc-heap is very low priority on this list, as it can be construed as "target agnostic but host specific" already (i.e. it tells you about it's own heap). Still, one could imagine it could both do that, and crawl core dumps of foreign code, or do it live with `iserv` for some remote debugging wizardry.
I got the idea when hunting down `TABLES_NEXT_TO_CODE` in !152
# Proposal
Pull out all the CPP / HSC into one module, that fills in some "abi config" struct. Everything else pulls the magic numbers from the struct.
CC @angerman @nomeata