Tags: emscripten-core/emscripten
Tags
[EH] Add more explanation to EXPORT_EXCEPTION_HANDLING_HELPERS deprec… …ation (#26517) Like WebAssembly/binaryen#8507, there can be people who use this methods at `-O1` or above. This adds more explanation of the workaround in ChangeeLog, site docs, and the deprecation message. You don't strictly need `decrementExceptionRefcount` to use `getExceptionMessage`, but you need it if you care about asan, because exceptions thrown in Wasm and caught in JS don't get freed unless you explicitly decrement the refcount.
Enable emscripten_futex API for Wasm Workers (#26325) This involves also including `emscripten_thread_state.S` which provides APIs such as `emscripten_is_main_runtime_thread` and emscripten_is_main_browser_thread` which now also work in Wasm Workers. There is a minor code size hit here of ~80 bytes, but I think its worth it to have these low level APIs available everywhere. Depends on: #26309 Fixes: #26314
Remove `MainLoop.method`. NFC (#26254) The `MainLoop.method` property seems to be a string version of `MainLoop.timingMode`. It had exactly one user which was to generate a warning. The warning was firing in the case when the method was `timeout` (which is the same as `timingMode` == `EM_TIMING_SETTIMEOUT`). The warning code would then reset `MainLoop.method` so that it would only fire "once per set main loop". However, since this was changed to `warnOnce` in #10090, the warning actually only fires once per program run.
PreviousNext