Regarding fixing this or CPR, would nested CPR fix all cases 'like
#16040: Unboxing-Related Performance Issue with Polymorphic Functions -------------------------------------+------------------------------------- Reporter: _recursion | Owner: (none) Type: bug | Status: new Priority: normal | Milestone: Component: Compiler | Version: 8.6.2 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: Type of failure: Runtime | Unknown/Multiple performance bug | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Wiki Page: | -------------------------------------+------------------------------------- Comment (by simonpj): this', as you put it, or even if the nested CPR patch lands would there still be a need for functionality to catch cases like this? I think we want ''both'' nested CPR ''and'' better placement of heap checks. They do different things -- it just so happens that in this case either would solve it. Great that you can work on it. I'd suggest the heap-check placement one, because it's a well-contained problem, I think. Nested CPR may have a longer on-ramp. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/16040#comment:7 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler