Implementing stack overflow protection for webassembly is tricky, as there are two stacks:

1. The hidden webassembly stack
2. The stack used for C stack objects that can have their address taken

We need to avoid overflowing either. It generally seems that the first stack is the one most vulnerable to overflow, so perhaps a simple counter would work.

@brettcannon
@hoodmane

Linked PRs

• GH-130397: use __stack_high and __stack_low LLVM WASM attributes #131855
• GH-130397: remove special-casing of C stack depth for WASI #134469
• [3.14] GH-130397: remove special-casing of C stack depth for WASI (GH-134469) #134547