inside the GHC code generator

Ken Whitegoat ken.whitegoat at
Sat Feb 25 13:16:43 EST 2006

bulat.ziganshin at wrote:
> ...
> as you can see here, gcc isn't unrolled the loop and retained all the
> stack<->register moves. why? the short answer is what gcc just don't
> know that data pointed by the Sp pointer is non-volatile - they can't
> be changed in middle of the program by some async computation or
> exception and don't required to be updated immediately. may be there
> is some way to tell gcc this? this would immediately SUBSTANTIALLY
> improve all ghc code generation
Would the C99 restrict keyword help in this situation?

More information about the Glasgow-haskell-users mailing list