Showing content from https://github.com/kripken/emscripten/issues/6168 below:
Emit WebAssembly by default instead of asm.js · Issue #6168 · emscripten-core/emscripten · GitHub
Skip to content Navigation Menu
Saved searches Use saved searches to filter your results more quickly
Sign up 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 Additional navigation options
Emit WebAssembly by default instead of asm.js #6168
Description
Now that all major browsers support wasm, and wasm output has been pretty stable for a while, maybe it's a good time to change the default output from asm.js to wasm?
Benefits:
- People should be using wasm since it's smaller&faster, unless they have a specific reason to need asm.js. So wasm by default makes more sense.
- Changing to wasm by default would move our test suite to focus mostly on that (e.g. right now almost all browser tests are asm.js). That would lead to better coverage of wasm, and also the wasm tests are faster.
Stuff to think about:
- This is orthogonal to our wasm support switching to the LLVM wasm backend by default Switching to use upstream LLVM backend by default #5488. So we could in theory do asm.js=>wasm earlier or later. Doing it earlier might make sense as it could be done sooner. Also that way means a more gradual change (2 big changes to the default output instead of one huge one).
- Aside from the main work to switch the default, this would require a lot of updates to our docs and tests, and overall we should make an effort to minimize confusion for users.
You can’t perform that action at this time.
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.3