[GHC] #15571: Eager AP_STACK blackholing causes incorrect size info for sanity checks

[GHC]

#15571: Eager AP_STACK blackholing causes incorrect size info for sanity checks
-------------------------------------+-------------------------------------
        Reporter:  osa1              |                Owner:  (none)
            Type:  bug               |               Status:  new
        Priority:  normal            |            Milestone:  8.6.1
       Component:  Runtime System    |              Version:  8.5
      Resolution:                    |             Keywords:
Operating System:  Unknown/Multiple  |         Architecture:
                                     |  Unknown/Multiple
 Type of failure:  None/Unknown      |            Test Case:
      Blocked By:                    |             Blocking:
 Related Tickets:  #15508            |  Differential Rev(s):
       Wiki Page:                    |
-------------------------------------+-------------------------------------

Comment (by simonmar):

 Hmm, I wonder if there's a much simpler way. The AP_STACK entry code
 simply copies the payload of the object onto the stack, after doing a
 stack check. So why don't we zero the slop immediately after copying the
 payload? That way we don't overwrite any data, and we don't need any new
 objects or stack frames.

-- 
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/15571#comment:3>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler