Re:Optimising Haskell for a tight inner loop
by carterschonwald on Thursday January 09, 2014 @02:33PM
(#7032605)
not quite, I think the issue is that llvm doesn't understand ghc's stack, so which I guess is the same issue :)
http://blog.omega-prime.co.uk/?p=135
Quote: "In particular, LLVM conservatively assumes that GHC's stack and the heap may alias". LLVM has to assume that short of Haskell-specific analysis, so updating to LLVM 3.4 won't help with such issues.