The recent implementation of stack probing for stack-clash (#66525 #66524 etc.)has exposed a few cases where we don't properly probe the stack according to the Windows rules. Specifically:
- For large call frames (calling a function with many arguments, where the caller also has dynamic allocation)
- For SVE locals/spills.
Also, we might want to consider leveraging the new inline probing sequences in some cases instead of calling __chkstk.
CC @mstorsjo