If we are going to fix #9718, how much of this do we need? Perhaps very
#15038: Memory Corruption (strange closure type) -------------------------------------+------------------------------------- Reporter: andrewthad | Owner: (none) Type: bug | Status: patch Priority: highest | Milestone: 8.6.1 Component: Compiler | Version: 8.4.1 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: | Unknown/Multiple Type of failure: Runtime crash | Test Case: Blocked By: | Blocking: Related Tickets: #9718 | Differential Rev(s): Phab:D4652 Wiki Page: | -------------------------------------+------------------------------------- Comment (by osa1): I responded in the diff. little? I don't think fixing #9718 would fix this bug because this bug happens in unarise which happens much later than both TidyPgm and CorePrep. I think to avoid this bug we need a way to ensure we don't make things more CAFFY after CAFFYness information is calculated in TidyPgm. This includes all the Stg-to-Stg transforms (CSE, unarise, perhaps new passes added in the future). -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/15038#comment:29 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler