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
As of #12059 we are moving away form the native dynCall functions but because of wasm2c's dependency we currently use the legacy mode when ASYNCIFY is enabled due to this failure.
The only difference I can thing is that perhaps when entering the wasm module via a native dynCall the dynCall function itself has been asyncified but directly calling a function via the table bypasses that?
I can't get this to fail, what am I doing wrong? I applied the PR #12059 , made sure I have latest binaryen, cleared the cache, and then ran ./tests/runner.py wasm*.test_fibers_asyncify and they all pass.
This issue has been automatically marked as stale because there has been no activity in the past year. It will be closed automatically if no further activity occurs in the next 30 days. Feel free to re-open at any time if this issue is still relevant.
As of #12059 we are moving away form the native dynCall functions but because of wasm2c's dependency we currently use the legacy mode when ASYNCIFY is enabled due to this failure.
The only difference I can thing is that perhaps when entering the wasm module via a native dynCall the dynCall function itself has been asyncified but directly calling a function via the table bypasses that?
See #12002
The text was updated successfully, but these errors were encountered: