Guard pages instead of Heap/Stack limit checks in Cmm

Recently I have debugged a small program and I saw that there are a lot of Heap/Stack limit checks on function entrances (https://ghc.haskell.org/trac/ghc/browser/ghc/rts/HeapStackCheck.cmm). This is not cheap and introduce more branch mispredictions and instructions. What you think if we use guard OS pages (that trigger exceptions when someone try to read/write on them) around Stack and Heap? Stack and Heap sizes should be aligned on page size (usually 4K) and with sizes that fits 4K pages. We could handle such exceptions so we could do GC if needed. This trick is usually found in some memory managers for finding out-of-bounds bugs.

Trac metadata

Trac field	Value
Version	8.0.2
Type	FeatureRequest
TypeOfFailure	OtherFailure
Priority	normal
Resolution	Unresolved
Component	Compiler
Test case
Differential revisions
BlockedBy
Related
Blocking
CC
Operating system
Architecture

changed weight to 5

added Tfeature request Trac import labels

closed

This is a duplicate of #8703 (closed). I am curious as to whether this would be easier under Linux now that we pre-allocate a contiguous heap.

Trac metadata

Trac field	Value
Resolution	Unresolved → ResolvedDuplicate
Related	- → #8703 (closed)

I'll write to other issue. Thanks!

We could just try first to realloc to extend memory blocks.

added Pnormal label