-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[browser] Bump emscripten 2.0.14 #48450
Conversation
- This includes the system headers which get copied into place there rather than adding a sequence of extra include directories.
* Default to TEXTDECODER=2 in -Oz builds to save 0.5KB-1KB of build output size. emscripten-core/emscripten#13304 * Fixes `TextDecoder is not defined` problem with running in console as well as when running the AOT console sample. ``` ReferenceError: TextDecoder is not defined at dotnet.js:1:8517 at loadScript (runtime.js:196:3) at runtime.js:280:1 runtime.js:196: Error executing file load (url); ``` * Fixes `TextDecoder is not defined` problem when running tests in console. ``` info: ReferenceError: TextDecoder is not defined info: at dotnet.js:1:8517 info: at loadScript (runtime.js:196:3) info: at runtime.js:280:1 info: info: runtime.js:196: Error executing file info: load (url); info: ^ info: info: 09:54:03.1461730 Process v8 exited with 1 ```
Tagging subscribers to this area: @CoffeeFlux Issue DetailsEmscripten now builds a complete sysroot inside the EM_CACHE directory. Introduced in 2.0.13
Add
|
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsEmscripten now builds a complete sysroot inside the EM_CACHE directory. Introduced in 2.0.13
Add
|
Actually thinking this should be
Also in multithreaded builds |
…g introduced - TextDecoder is enabled by default, but it is not always used, because it is slower decoding short strings compared to using a manually rolled JavaScript implementation, which is why the current default `TEXTDECODER=1` manually decodes short strings, and falls back to TextDecoder for long strings (cutoff is at 16 byte strings).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good but we'll need to wait and bump to the new Docker image once it's available.
Seems to be issues with System.IO.FileNotFoundException : Unable to find the specified file. Looking into the cause of change or report issue |
Have been able to track the failure to pal_io.c in the copying of the metadata. With 2.0.12 this returns This happened in 2.0.13 so that narrows it down. |
…asm-bump-empscripten-fourteen' of https://github.com/kjpou1/runtime into wasm-bump-empscripten-fourteen
This PR is the breaking change: emscripten-core/emscripten#13282 |
Created issue: emscripten-core/emscripten#13547 |
Active issue opened on emcripten : emscripten-core/emscripten#13547
PR open here: emscripten-core/emscripten#13549
Emscripten now builds a complete sysroot inside the EM_CACHE directory. Introduced in 2.0.13
Add
-s TEXTDECODER=1
to EMCC_FLAGS to work around bug introducedTextDecoder is not defined
problem with running in console as well as when running the AOT console sample.TextDecoder is not defined
problem when running tests in console.