stranal/sigs/UnsatFun

[Ben Gamari]

Richard Eisenberg <eir at 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?
>
> 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?
>
> And where in the GHC code base should I start looking to understand
> this better?
>
> Sorry if these questions seem too easy -- I'm just out of my element
> here. My hunch is that I need to update something in the strictness
> analyzer to look through/around/beyond coercions somewhere. Any ideas
> as to what that might be would be helpful! :)
>
You might also want to look at [1], which appears to offer a nice tour
around the implementation.

Cheers,

- Ben


[1] https://ghc.haskell.org/trac/ghc/wiki/Commentary/Compiler/Demand/RelevantParts

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 472 bytes
Desc: not available
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20151130/68020077/attachment.sig>