ABI considerations regarding stack unwinding on Windows

[briansmith]

Could you please document the approach for handling stack unwinding on Windows. In the OpenSSL/BoringSSL code base the stack unwinding machinery is a source of concern, so it is nice to not see a similar approach. However, also, there doesn't seem to be any indications of how the project intends to support stack unwinding.

(In cryptogams, Andy changed some (all?) of the unwinding to be declarative.)

[jargh]

We don't have much to say, currently (though we can say that explicitly of course). Can you recommend a reference or some models for what you would consider the right approach, if any? If it seems feasible to support it readily, we probably want to try and do so, and either way we can be more explicit in our documentation.

[briansmith]

Here is the relevant reference from Microsoft: https://learn.microsoft.com/en-us/cpp/build/x64-calling-convention?view=msvc-170#unwindability

[briansmith]

Also https://learn.microsoft.com/en-us/cpp/build/prolog-and-epilog?view=msvc-170 and https://learn.microsoft.com/en-us/cpp/build/exception-handling-x64?view=msvc-170