Richard Eisenberg <e...@cis.upenn.edu> writes: > These responses are helpful, thanks. > > Is there a primer for how to read the output? Or a small function that > produces the output that I could quickly reverse engineer? > The Wiki is a good place to start although the description there is lacking a bit. [1]
Relatedly, some time ago I started writing a blog article about various aspects of Core with the intent of presenting a document accessible to the average Haskeller with an interest in diving into the compilation pipeline. While it's quite far from done, it's perhaps worth putting up the current state of it. Here it is [2]. > There is a suggestion to look at the core before and after my patch. > Is there a certain phase I should look at? What should I look for? > It would be good to see the Core as it enters strictness analysis. > And where in the GHC code base should I start looking to understand > this better? > compiler/stranal I believe. Of course, take anything I have to say with a large grain of salt; Joachim's opinion is orders of magnitude better informed than mine in this area. Cheers, - Ben [1] https://ghc.haskell.org/trac/ghc/wiki/Commentary/Compiler/Demand [2] http://smart-cactus.org/~ben/posts/2015-01-19-understanding-ghc-core.html
signature.asc
Description: PGP signature
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
