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

That’s extremely impressive, Csaba.

 

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

Simon

 

From: ghc-devs <ghc-devs-bounces@haskell.org> On Behalf Of Csaba Hruska
Sent: 10 April 2021 11:49
To: GHC developers <ghc-devs@haskell.org>
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

Feedback is welcome.

 

Cheers,

Csaba

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