What changed between GHC 8.8 and 8.10 that could cause this?

Matthew Pickering matthewtpickering at gmail.com
Thu Mar 4 12:45:00 UTC 2021

Perhaps related to 0dc7985663efa1739aafb480759e2e2e7fca2a36 ?

commit 0dc7985663efa1739aafb480759e2e2e7fca2a36
Author: Julian Leviston <julian at leviston.net>
Date:   Sat Feb 2 20:10:51 2019 +1100

    Allow for multiple linker instances. Fixes Haskell portion of #3372.

On Thu, Mar 4, 2021 at 11:55 AM ÉRDI Gergő <gergo at erdi.hu> wrote:
> Hi,
> I'm trying to figure out a Clash  problem and managed to track it down to
> a GHC upgrade; specifically, a given Clash version, when based on GHC
> 8.8, has no problem synthesizing one module after another from one
> process; but the same Clash version with GHC 8.10 fails with link-time
> errors on the second compilation.
> The details are at https://github.com/clash-lang/clash-compiler/issues/1686
> but for now I'm just hoping that some lightbulb will go off for someone if
> some handling of internal state has changed in GHC that could mean that
> the symbol tables of loaded modules could persist between GHC invocations
> from the same process.
> So, does this ring a bell for anyone?
> Thanks,
>         Gergo
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

More information about the ghc-devs mailing list