<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">This sounds pretty exciting! <div class=""><br class=""></div><div class="">Can we expect a full fledged stepping debugger integrated with IDEs via <a href="https://github.com/phoityne/haskell-debug-adapter" class="">https://github.com/phoityne/haskell-debug-adapter</a> ? <a href="https://github.com/phoityne/ghci-dap" class="">https://github.com/phoityne/ghci-dap</a> is still quite limited feature-wise.<div class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 2021-12-02, at 22:52, Csaba Hruska <<a href="mailto:csaba.hruska@gmail.com" class="">csaba.hruska@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="">Hello,</div><div class=""><br class=""></div><div class="">Today I'll do a presentation about the external stg interpreter.</div><div class="">If you are interested please join and ask questions.</div><div class=""><a href="https://skillsmatter.com/meetups/13654-haskell-stg-interp" class="">https://skillsmatter.com/meetups/13654-haskell-stg-interp</a></div><div class=""><br class=""></div><div class=""><div class="">Regards,</div><div class="">Csaba Hruska</div></div><div class=""><br class=""></div><div class="">Abstract:<br class=""><h3 class="">
Haskell: Why and How the External STG Interpreter is Useful
</h3>
<div class="gmail-module__inner"><p class="">The
external STG interpreter is a from scratch implementation of the STG
machine in Haskell. Currently it supports almost all GHC primops and RTS
features. It can run real world Haskell programs that were compiled
with GHC Whole Program Compiler (GHC-WPC). GHC-WPC is a GHC fork that
exports the whole program STG IR.</p><p class="">The external STG interpreter is an excellent tool to study the
runtime behaviour of Haskell programs, i.e. it can run/interpret GHC or
Pandoc. The implementation of the interpreter is in plain simple
Haskell, so it makes compiler backend and tooling development
approachable for everyone. It already has a programmable debugger which
supports step-by-step evaluation, breakpoints and execution region based
inspection. It also can export the whole program memory state and
call-graphs to files for further investigation. These features make it
easy to find a memory leak or to identify a performance bottleneck in a
large real world Haskell application.</p><p class=""><a href="https://github.com/grin-compiler/ghc-whole-program-compiler-project" class="">https://github.com/grin-compiler/ghc-whole-program-compiler-project</a></p>
</div></div></div>
_______________________________________________<br class="">ghc-devs mailing list<br class=""><a href="mailto:ghc-devs@haskell.org" class="">ghc-devs@haskell.org</a><br class="">http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs<br class=""></div></blockquote></div><br class=""></div></div></body></html>