Wasmtime GitHub notifications bot (May 21 2020 at 20:34): Wasmtime GitHub notifications bot (May 21 2020 at 20:34):peterhuene commented on Issue #1740:
Your assessment of this for x86 is correct. In x86, SEH handlers are registered via a stack-based linked list of handlers, with the head in the TIB (at
FS:[0]).As we don't currently have exception handling in Wasm frames and we always use frame pointers, there's nothing here to do for x86.
When we do have exception handling in Wasm frames, we will need completely different prologue/epilogue generation for 32-bit Windows for setting up SEH.
Given the plethora of calling conventions on 32-bit Windows, lack of unwind information, and SEH affecting code gen, it's really an unpleasant target to work with from a tooling perspective.
Wasmtime GitHub notifications bot (May 21 2020 at 20:35):peterhuene commented on Issue #1740:
On the plus side, Microsoft is no longer shipping 32-bit Windows going forward :tada:.
Wasmtime GitHub notifications bot (May 21 2020 at 20:45):whitequark commented on Issue #1740:
On the plus side, Microsoft is no longer shipping 32-bit Windows going forward .
Yeah, but I'll support 32-bit applications forever. I'm trying to ship a Python package that uses wasmtime, and the Python installer suggested by http://python.org is still 32-bit.
Wasmtime GitHub notifications bot (May 21 2020 at 20:45):whitequark edited a comment on Issue #1740:
On the plus side, Microsoft is no longer shipping 32-bit Windows going forward .
Yeah, but it'll support 32-bit applications forever. I'm trying to ship a Python package that uses wasmtime, and the Python installer suggested by http://python.org is still 32-bit.
Last updated: Oct 23 2024 at 20:03 UTC