#12622: Unboxed static pointers lead to missing SPT entries -------------------------------------+------------------------------------- Reporter: mboes | Owner: | facundo.dominguez Type: bug | Status: patch Priority: normal | Milestone: Component: Compiler | Version: 8.1 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: | Unknown/Multiple Type of failure: None/Unknown | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Phab:D2709 Wiki Page: | Phab:D2720 -------------------------------------+------------------------------------- Comment (by simonpj): I'm a bit lost reading comment:11. What is step (2)? Lots of stuff is crossed out. Yes `makeStatic` should not be unfolded. I'm not sure why `FloatOut` would need to treat `makeStatic` any more specially than it did `StaticPtr`. Yes, the top level binding `x = makeStatic y` should not be inlined; but I think that'll be the case anyway. Yes, some stuff (making a fingerprint, and `StaticPtr` value) is moved from the desugarer to the SPT construction -- that's a feature! It looks good to me. If you think another approach is better, by all means describe it. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/12622#comment:12 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler