You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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:
Also, we might want to consider leveraging the new inline probing sequences in some cases instead of calling __chkstk.
CC @mstorsjo
The text was updated successfully, but these errors were encountered: