Update emsdk version from ae6cb9c1 to 60241fe0 (#27561)

This is an automatic change generated by tools/maint/rebaseline_tests.py
--update-emsdk.

emsdk version updated: ae6cb9c1 => 60241fe0

The following revisions were included in this update:

```
- 60241fe0 Roll emscripten from bd3bbeab717d to ca200ba646c0 (1 revision)
- fb721d95 Roll emscripten from c333eb49ae50 to bd3bbeab717d (1 revision)
- 7e7edeb3 Roll llvm-project from 9a1c6e561697 to ecdcdf0577c1 (33 revisions)
- 45d98340 Roll binaryen from 081f8cbb1a13 to 07a6f35f8ae0 (1 revision)
- 8a817fae Roll emscripten from c6285f2a3c15 to c333eb49ae50 (2 revisions)
- 1fe48939 Roll binaryen from 8d9412ef6431 to 081f8cbb1a13 (1 revision)
- 11204535 Roll emscripten from 4b47df092ec9 to c6285f2a3c15 (1 revision)
- d10e6ea3 Roll llvm-project from 4cc02503f584 to 9a1c6e561697 (271 revisions)
- c8fb05a8 Roll emscripten from 4e8b63eac594 to 4b47df092ec9 (1 revision)
- a2e0030d Version 6.0.7 RC
- f983dbd0 Roll v8 from 5280f012d5ce to fd75eb5d6753 (1 revision)
```

Full log:
https://chromium.googlesource.com/emscripten-releases/+log/ae6cb9c1..60241fe0

The following (15) test expectation files were updated by
running the tests with `--rebaseline`:

```
codesize/test_codesize_cxx_ctors1.json: 153947 => 153934 [-13 bytes / -0.01%]
codesize/test_codesize_cxx_ctors2.json: 153353 => 153340 [-13 bytes / -0.01%]
codesize/test_codesize_cxx_except.json: 200106 => 200093 [-13 bytes / -0.01%]
codesize/test_codesize_cxx_except_wasm.json: 169475 => 169462 [-13 bytes / -0.01%]
codesize/test_codesize_cxx_except_wasm_legacy.json: 167335 => 167322 [-13 bytes / -0.01%]
codesize/test_codesize_cxx_lto.json: 119548 => 119535 [-13 bytes / -0.01%]
codesize/test_codesize_cxx_mangle.json: 266436 => 266423 [-13 bytes / -0.00%]
codesize/test_codesize_cxx_noexcept.json: 155857 => 155844 [-13 bytes / -0.01%]
codesize/test_codesize_cxx_wasmfs.json: 180975 => 180962 [-13 bytes / -0.01%]
codesize/test_codesize_files_wasmfs.json: 63240 => 63223 [-17 bytes / -0.03%]
codesize/test_codesize_hello_O1.json: 8060 => 8041 [-19 bytes / -0.24%]
codesize/test_codesize_hello_dylink.json: 44113 => 44096 [-17 bytes / -0.04%]
codesize/test_codesize_hello_dylink_all.json: 858927 => 858910 [-17 bytes / -0.00%]
codesize/test_minimal_runtime_code_size_hello_embind.json: 15004 => 14987 [-17 bytes / -0.11%]
codesize/test_minimal_runtime_code_size_hello_embind_val.json: 11731 => 11714 [-17 bytes / -0.14%]

Average change: -0.04% (-0.24% - -0.00%)
```

Co-authored-by: emscripten-bot <emscripten-bot@users.noreply.github.com>
16 files changed
tree: 65a31bd77cdea3bb746876e38cd3f0eae2506c1a
  1. .circleci/
  2. .github/
  3. cmake/
  4. docs/
  5. html/
  6. media/
  7. site/
  8. src/
  9. system/
  10. test/
  11. third_party/
  12. tools/
  13. .clang-format
  14. .clang-format-ignore
  15. .editorconfig
  16. .git-blame-ignore-revs
  17. .gitattributes
  18. .gitignore
  19. .gitmodules
  20. .prettierrc.yml
  21. .style.yapf
  22. AUTHORS
  23. bootstrap.py
  24. ChangeLog.md
  25. CONTRIBUTING.md
  26. em++.py
  27. em-config.py
  28. emar.py
  29. embuilder.py
  30. emcc.py
  31. emcmake.py
  32. emconfigure.py
  33. emmake.py
  34. emranlib.py
  35. emrun.py
  36. emscan-deps.py
  37. emscons.py
  38. emscripten-version.txt
  39. emsize.py
  40. emstrip.py
  41. eslint.config.mjs
  42. LICENSE
  43. Makefile
  44. package-lock.json
  45. package.json
  46. pyproject.toml
  47. README.md
  48. requirements-dev.txt
  49. SECURITY.md
README.md

emscripten logo

Main project page: https://emscripten.org

GitHub CI status: CircleCI

Chromium builder status: emscripten-releases

Overview

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 target).

Getting Started

For detailed instructions and tutorials, visit the Emscripten Website.

Installation

There are two primary ways to install Emscripten:

  1. Using the Emscripten SDK (emsdk) (Recommended) The easiest way to get started is by using the Emscripten SDK. Follow the instructions on the downloads page to install it.

  2. From a Git Checkout (Manual Installation) If you have cloned the repository from Git, you can install the dependencies manually and then run the bootstrap script:

    ./bootstrap.py
    

    For more details, see the developer guide.

Using the compiler

Run emcc like you would gcc or clang:

$ emcc hello.c -o hello.js
$ node hello.js
Hello, world!

Emscripten will compile your code into a WebAssembly module along with a JavaScript file that can load and run it. You can then run the resulting JavaScript in your browser or under Node.js (or Deno or Bun).

Emscripten can also generate a sample HTML page that then loads the JavaScript:

$ emcc hello.c -o hello.html

You can then serve the generated hello.html using the emrun tool, or a web server of your choosing.

Contributing

For information on how to contribute to the project, see CONTRIBUTING.md and the Contributing section on the website.

License

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.