| commit | 2a00e26013b0a02411af09352c6731b89023f382 | [log] [tgz] |
|---|---|---|
| author | kangtastic <942136+kangtastic@users.noreply.github.com> | Thu Feb 08 07:35:44 2024 |
| committer | GitHub <noreply@github.com> | Thu Feb 08 07:35:44 2024 |
| tree | 29b1f0242a75bd9307cf2bbe2cb2bf8ae5c317f9 | |
| parent | 9c936417f91ccbe896a1f1a2966364c1adf70f0e [diff] |
Fix broken JS glue for AUDIO_WORKLETS with EXPORT_ES6 (#21192)
WASM Audio Worklets with EXPORT_ES6 may break at runtime:
test.js:989 Uncaught (in promise) TypeError: Cannot set property wasmTable of #<Object> which has only a getter
at receiveInstance (test.js:989:25)
at receiveInstantiationResult (test.js:1011:5)
The read-only getter at issue is created in ASSERTIONS-enabled
builds, and conflicts with the current way of exporting wasmTable
on the Module object.
Exporting wasmTable via EXPORTED_RUNTIME_METHODS prevents the getter
from being created in normal builds. In MINIMAL_RUNTIME builds, we
make sure to delete the getter before manually exporting as before.
We also prevent an ES6 Audio Worklet from loading the .wasm binary
via `new URL()`, as `URL` is unavailable in AudioWorkletGlobalScope.
Main project page: https://emscripten.org
GitHub CI status: 
Chromium builder status: emscripten-releases
Emscripten compiles C and C++ to WebAssembly using LLVM and Binaryen. Emscripten output can run on the Web, in Node.js, and in wasm runtimes.
Emscripten provides Web support for popular portable APIs such as OpenGL and SDL2, allowing complex graphical native applications to be ported, such as the Unity game engine and Google Earth. It can probably port your codebase, too!
While Emscripten mostly focuses on compiling C and C++ using Clang, it can be integrated with other LLVM-using compilers (for example, Rust has Emscripten integration, with the wasm32-unknown-emscripten and asmjs-unknown-emscripten targets).
Emscripten is available under 2 licenses, the MIT license and the University of Illinois/NCSA Open Source License.
Both are permissive open source licenses, with little if any practical difference between them.
The reason for offering both is that (1) the MIT license is well-known and suitable for a compiler toolchain, while (2) LLVM‘s original license, the University of Illinois/NCSA Open Source License, was also offered to allow Emscripten’s code to be integrated upstream into LLVM. The second reason became less important after Emscripten switched to the LLVM wasm backend, at which point there isn't any code we expect to move back and forth between the projects; also, LLVM relicensed to Apache 2.0 + exceptions meanwhile. In practice you can just consider Emscripten as MIT licensed (which allows you to do pretty much anything you want with a compiler, including commercial and non-commercial use).
See LICENSE for the full content of the licenses.