Re: External STG Interpreter blog post

Indeed it is! I also am very much hoping this can be the missing piece we need to allow Template Haskell to work with a stage 0 GHC, so that we can safely use TH in GHC itself even when the ABI is changing. See https://github.com/ghc-proposals/ghc-proposals/issues/162 for details, where I've also linked Csaba's blog post. (And maybe also https://gitlab.haskell.org/ghc/ghc/-/wikis/cross-compilation/roadmap for more background, and related things like https://github.com/ghc-proposals/ghc-proposals/pull/412.) TH could perhaps be used to replace some of the ad-hoc code gen we have for e.g. RTS constants and primops. This in turn would simplify the build system, allowing for `cabal install ghc` to work without shipping generated Haskell code in the sdist. John On 4/12/21 4:51 AM, Simon Peyton Jones via ghc-devs wrote:

That’s extremely impressive, Csaba.

Maybe of interest to folk who have been thinking about “fat interface files”.

Simon

*From:*ghc-devs *On Behalf Of *Csaba Hruska *Sent:* 10 April 2021 11:49 *To:* GHC developers *Subject:* External STG Interpreter blog post

Hello,

I've written a blog post about GHC-WPC's external stg interpreter. https://www.patreon.com/posts/external-stg-49857800 https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fposts%2Fexternal-stg-49857800&data=04%7C01%7Csimonpj%40microsoft.com%7C1535f88608f549dabb8108d8fc0e4c3f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637536486264337310%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=VXa%2FhDs1ePRS5NTu04buv42yj%2BFKw%2FJzBLQJSwp8qTs%3D&reserved=0

Feedback is welcome.

Cheers,

Csaba

_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs