Ah, thanks Simon!
This helps a lot.
Cheers,
Tamar
From: Simon Peyton Jones
Sent: Wednesday, June 15, 2016 13:07
To: loneti...@gmail.com; Ömer Sinan Ağacan
Cc: ghc-devs@haskell.org
Subject: RE: CoreToStg Asserts
Ah yes. This is a long-standing wart:
1. The CoreTidy pass predicts what
<omeraga...@gmail.com>
Cc: ghc-devs@haskell.org
Subject: 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 somet
14, 2016 18:46
To: Phyx
Cc: ghc-devs@haskell.org
Subject: 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
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?
Hi *,
I'm hoping someone could help me understand what the asserts in CoreToStg
on line 240 and 216 are trying to tell me.
I hit both of them while trying to compile libraries as dyn.
WARNING: file compiler\stgSyn\CoreToStg.hs, line 250
$trModule2 False True
ghc-stage1.exe: panic! (the
