| commit | 2f197857349732746ef3ab79a7a258d7e8628076 | [log] [tgz] |
|---|---|---|
| author | Sam Clegg <[email protected]> | Fri Sep 24 19:42:46 2021 |
| committer | Sam Clegg <[email protected]> | Wed Oct 20 22:35:01 2021 |
| tree | 084113096334c97d8f3063ea8b97c66f81183c99 | |
| parent | ac7c391ee58c608ab10991a7f67526a758f95f97 [diff] |
Initial support runtime dlopen in multi-threaded applications This change maintains a shared global list of DSOs loaded and adds a `emscripten_thread_sync_code` helper function which can be used to bring the current thread up to date by loading all the modules in the this list. The static table region allocated for a particular module is allocated by the first loading thread. All other threads will use the same pre-allocated region. This change does not yet deal with sychronizing pointers loaded by `dlsym`.
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.