#8703: Use guard pages rather than heap checks -------------------------------------+------------------------------------- Reporter: schyler | Owner: simonmar Type: feature request | Status: closed Priority: normal | Milestone: Component: Runtime System | Version: Resolution: wontfix | Keywords: Operating System: Unknown/Multiple | Architecture: | Unknown/Multiple Type of failure: None/Unknown | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Wiki Page: | -------------------------------------+------------------------------------- Comment (by simonpj): FWIW I believe that in other systems (e.g. ML) they started using guard pages, and moved away from it becuase it was SO HARD to make it work: on different archiectures and OSs, accommodating the non-standard calling conventions we use; dealing with correct GC of the registers that are saved on the trap; dealing with the fact that the stack we have is tiny, unlike the OS stack. If I had 1,000 hours to invest, I would invest it elsewhere. I'm not saying you couldn't make progress here, just that I think you'll find a better cost/benefit ratio elsewhere. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/8703#comment:6 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler