#15770: Missing optimisation opportunity in code gen for always-saturated applications? -------------------------------------+------------------------------------- Reporter: osa1 | Owner: (none) Type: bug | Status: new Priority: normal | Milestone: Component: Compiler | Version: 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:D5232 Wiki Page: | -------------------------------------+------------------------------------- Changes (by osa1): * differential: => Phab:D5232 Comment: Great, because this means less work for #9718. Shall we merge Phab:D5232?
info table and slow entry code to support the heap/stack checks
Out of curiosity, why do we need entry code for heap/stack checks? Do we use slow entry code as continuation when we do GC? Or something else? -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/15770#comment:3 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler