RE: CoreToStg Asserts

Hi Ömer, Thanks for the pointers, should help me find out more. It’s not a stock GHC as I’m working on getting Dynamic linking back on Windows. This assert is triggered on the dyn version of the libs. So something’s bit rotted here. Cheers, Tamar From: Ömer Sinan Ağacan Sent: Tuesday, June

Re: CoreToStg Asserts

Hi Tamar, Have a look at Note [Disgusting computation of CafRefs] in TidyPgm.hs. The assertion triggered here is the one that checks `hasCafRefs` mentioned in that note matches with actual CAF-ness. Are you using stock GHC? Which version? Do you have a minimal program that reproduces this?

RE: Pusing to haddock

Simon Peyton Jones writes: > | tests/alloc/haddock.Cabal  11811321368 + 6.40% 12567003040 > | bytes > | tests/alloc/haddock.compiler  60211764264 + 7.39% > | 64658444232 bytes > | > | The haddock stats changes are probably genuine, I

Re: Pusing to haddock

Hi, Am Dienstag, den 14.06.2016, 08:18 + schrieb Simon Peyton Jones: > For the record, the series of patches, one of which presumably causes > the regression, is below.   Bisecting to the right one would be very > helpful -- but you have to apply the final one (haddock-update) > first. I

RE: Pusing to haddock

| tests/alloc/haddock.Cabal  11811321368 + 6.40% 12567003040 | bytes | tests/alloc/haddock.compiler 60211764264 + 7.39% | 64658444232 bytes | | The haddock stats changes are probably genuine, I assume, but the | expected value in all.T should be

Re: Pusing to haddock

Hi, Am Montag, den 13.06.2016, 22:54 + schrieb Simon Peyton Jones: > I hope that should settle things. it does, but unfortunately, now perf.haskell.org can only give aggregate results for the joint commit: Benchmark name  previous  change  now