6 Jun
2011
6 Jun
'11
10:27 p.m.
Right now, I'd just like to have the code run quickly, and to figure out why I'm seeing such a terrible regression under ghc7.
From the #haskell channel, it looks like the horrible speed issue on this code is specific to my system. I'm re-building ghc7 now (bootstrapping ghc7 with ghc7 instead of ghc6), so maybe that will make something happier. If it doesn't, how does one go about figuring out why a program isn't being compiled to use primitive operations? just running ghc -v5 gives me so much information that I can't make any sense of it. Is there a less shotgun-like approach to seeing where the compiler is getting confused?