dotnet · akoeplinger · Jul 9, 2026 · May 15, 2026 · May 15, 2026 · May 15, 2026
diff --git a/.gitignore b/.gitignore
@@ -97,7 +97,6 @@ test/runner.bat
 tools/file_packager.bat
 tools/webidl_binder.bat
 
-bootstrap.exe
 em++.exe
 emcc.exe
 em-config.exe

diff --git a/AUTHORS b/AUTHORS
@@ -603,3 +603,4 @@ a license to everyone to use it as detailed in LICENSE.)
 * Sean Morris <sean@seanmorr.is>
 * Mitchell Wills <mwills@google.com> (copyright owned by Google, Inc.)
 * Han Jiang <jhcarl0814@gmail.com>
+* Abdelrahman Teima <abdelrahmanteima@gmail.com>
diff --git a/ChangeLog.md b/ChangeLog.md
@@ -18,11 +18,168 @@ to browse the changes between the tags.
 
 See docs/process.md for more on how version tagging works.
 
-5.0.6 (in development)
+6.0.3 (in development)
 ----------------------
+- Added support for compiling FMA intrinsics. All 32 FMA intrinsics are
+  supported, with 256-bit variants emulated via two 128-bit operations. Pass
+  ``-msimd128 -mfma`` to enable. With ``-mrelaxed-simd -mfma``, Wasm relaxed
+  SIMD FMA is used. (#27183)
+- New `AUTO_INIT` setting to opt an instance ES module (`MODULARIZE=instance` or
+  `WASM_ESM_INTEGRATION`) into self-initialization via top-level await on import,
+  rather than exporting a default `init` function. Since there is no
+  init/moduleArg, module-level configuration is unavailable:
+  `INCOMING_MODULE_JS_API` is disabled and passing a non-empty one is an error.
+- The async `poll()`/`select()` implementation was refactored onto a per-inode
+  readiness wait-queue. As part of this, the (undocumented) `stream_ops.poll`
+  FS-backend handler signature changed from `poll(stream, timeout)` to
+  `poll(stream)` returning the current readiness mask; out-of-tree custom FS
+  backends with a `poll` handler must update. (#27226)
+- compiler-rt and libunwind were updated to LLVM 22.1.8. (#27245, #27246)
+- `-fcoverage-mapping` is currently broken due to a mismatch between the version
+  of LLVM used and the imported version of compiler-rt.  We hope to fix this
+  in the next release. (#27261)
+- The default value for `GROWABLE_ARRAYBUFFERS` was reverted to `0` since we
+  found issues with Web API compatibility. (#27260)
+
+6.0.2 - 07/01/26
+----------------
+- The `GROWABLE_ARRAYBUFFERS` setting now supports both `=1` (auto-detect and
+  use the feature) and `=2` (unconditionally use the feature, avoiding the 
+  overhead in multi-threaded builds). It now defaults to `=1`, meaning the
+  feature will be used when available. Note that this only affects programs
+  that are built with `ALLOW_MEMORY_GROWTH`, which is not enabled by default.
+  (#27096, #27212)
+- New `-sNODERAWSOCKETS` setting that backs the POSIX sockets API with real TCP
+  (`node:net`) and UDP (`node:dgram`) sockets on Node.js, with no `ws`, proxy
+  process, or pthreads required. Supports incoming and outgoing TCP, UDP, IPv6,
+  and `-pthread` with `PROXY_TO_PTHREAD`. Uses the public node APIs where
+  available, falling back to `tcp_wrap`/`udp_wrap` on older Node.js. (#27080)
+- The following symbols are no longer included in `INCOMING_MODULE_JS_API`
+  by default:
+  - GL_MAX_TEXTURE_IMAGE_UNITS
+  - SDL_canPlayWithWebAudio
+  - SDL_numSimultaneouslyQueuedBuffers
+  - freePreloadedMediaOnUse
+  - preinitializedWebGLContext
+  - keyboardListeningElement
+  - doNotCaptureKeyboard
+  - extraStackTrace
+  - preloadPlugins
+  - postMainLoop
+  - preMainLoop
+  - forcedAspectRatio
+  - mainScriptUrlOrBlob
+  - onFullScreen
+  - INITIAL_MEMORY
+  - wasmMemory
+  - wasmBinary
+  Anybody using these will see a clear error in their debug builds signaling
+  that they now need to be explicitly added to `-sINCOMING_MODULE_JS_API`.
+
+6.0.1 - 06/22/26
+----------------
+- The ability to redirect JS compiler stderr using `EMCC_STDERR_FILE` was
+  removed.  These days you can use `EMCC_DEBUG` and/or `EMCC_DEBUG_SAVE` to
+  preserve all the intermediate JS compiler files. (#27101)
+- The installed versions of the compiler-rt library now follow the upstream
+  naming convetion of `libclang_rt.<something>.a`. (#27089)
+- Dynamic linking now explicitly requires asynchronous Wasm compilation. The
+  process of loading side modules at startup currently depends on this. (#27086)
+- New experimental `-sCROSS_ORIGIN_STORAGE` linker flag integrating the
+  proposed [Cross-Origin Storage browser API](https://github.com/WICG/cross-origin-storage)
+  as a progressive enhancement for Wasm loading on the web target. See
+  `docs/compiling/CrossOriginStorage.rst` for details. (#27066)
+- The `-sUSE_PTHREADS` and `-sMEMORY64` flags have been deprecated in favor of the
+  more standard `-pthread` and `-m64` (or `--target=wasm64`) flags. (#27025)
+- Adds wasm-bindgen support. When `-sWASM_BINDGEN` is set, Emscripten will call
+  out to `wasm-bindgen` in the users's path and integrate the wasm-bindgen JS
+  with the normal Emscripten JS. Some wasm-bindgen features may not yet be fully
+  supported. (#23493)
+- Fixed `getentropy`/`random_get` spuriously failing under Node.js and the
+  shell environment for small requests. (#27122)
+- The startup process for the generated program now makes use of `async` /
+  `await` under more circumstances (specifically when using `setStatus`, or
+  run dependencies). This means that errors during startup (or during the
+  `main()` function) will more often show up as unhandled promise rejections
+  (`onunhandledreject`) rather than synchronous errors (`onerror`). (#27121)
+
+6.0.0 - 06/04/26
+----------------
+- On Windows, Emscripten now ships `.exe` tool launchers, rather
+  than `.bat` and/or `.ps1`.  This means that any scripts that explicitly
+  reference, e.g. `emcc.bat`, will need to be updated to just `emcc` (or
+  `emcc.exe`).  For the time being you can still get the old `.bat` files by
+  running `tools/maint/create_entry_points.py --bat-files`. (#24858)
+- When performing a streaming Fetch operation, the max chunk size of downloaded
+  bytes that is handed over to the Wasm side from JS is now capped to maximum
+  of 8 megabytes. This ensures that a streaming Fetch stays streaming, rather
+  than transferring the whole (potentially large) file as one huge chunk, which
+  might not fit in the WebAssembly memory. (#26898)
+- The minimum versions of browser engines supported by emscripten's generated
+  code were bumped, allowing us to remove our internal support for transpilation
+  via babel:
+    MIN_CHROME_VERSION: 74 -> 85
+    MIN_FIREFOX_VERSION: 68 -> 79
+    MIN_SAFARI_VERSION: 12.2 -> 14.1
+  This allows us to assume that features such as mutable-globals and sign-ext
+  are universally available.  Disabling these is no longer possible in
+  emscripten.  If you still need to support extremely old browsers, you can
+  manually transpile the output of emscripten (e.g. using babel for JS and
+  binaryen for wasm). (#26677)
+- musl libc updated from v1.2.5 to v1.2.6. (#26860)
+- libpng port updated from 1.6.55 to 1.6.58. (#26592, #26983)
+- The `-m64` compiler flag is now honored, and works as an alias for
+  `-sMEMORY64` and/or `--target=wasm64`. (#26765)
+- The autopersistence feature in IDBFS mount now supports registering a global
+  callback `IDBFS.onAutoPersistStateChanged = active => {}`, which will be
+  notified of all IDBFS sync start and end events. (#26895)
+- google-closure-compiler was updated to 20260429.0.0. (#26869)
+  Closure compiler now provides a native macOS arm64 binary for Apple Silicon,
+  in addition to having native binaries for Win-x64, Linux-x64 and Linux-ARM64.
+  For other platforms for which Closure compiler does not ship a native binary,
+  e.g. Intel x64 Macs and Windows-on-ARM, downloading Java SE Development Kit
+  21.0.11 from https://www.oracle.com/europe/java/technologies/downloads/#java21
+  is required in order to use Emscripten's Closure Compiler integration.
+- The `FAKE_DYLIBS` setting is now disabled by default. This means that
+  `-shared` will produce real dynamic libraries by default (`-sSIDE_MODULE` is
+  implied).  Also, if you include real dynamic libraries in your link command
+  emscripten will now automatically produce a dynamically linked program
+  (`-sMAIN_MODULE=2` is implied). (#25930)
+- The `PThread.runningWorkers` field was removed from the `PThread` object.
+  If you have JS code that was depending on this you can transition to using the
+  `PThread.pthreads` object. (#26998)
+- The POSIX `pause()` function will now return 0 rather than EINTR. (#27044)
+
+5.0.7 - 04/30/26
+----------------
+- mimalloc was updated to 3.3.1. (#26696)
+- The `WASM_JS_TYPES` setting was removed, as the corresponsing propsal was
+  pushed back to phase 1. (#26739)
+- The `-sDETERMINISTIC` setting was removed.  This setting just injected
+  `src/deterministic.js` as a `--pre-js`.  For now, this file remains part of
+  emscripten so folks can sill use it manually if needed.  If you are a user of
+  this feature please let us know otherwise this may be deleted in a future
+  release. (#26648)
+- The emscripten_futex_wait internals were improved to avoid unnecessary thread
+  wakeups.  As part of this change emscripten_futex_wait is now documented to
+  explicitly allow for returning EINTR when the wait is interrupted by an async
+  operation.  All callers of emscripten_futex_wait are advised to use a loop
+  to handle these types of spurious wakeups / interruptions. (#26659, #26735)
+- Attempting to use PTHREAD_PROCESS_SHARED when creating pthread primitives such
+  as locks and condvars will now fail with ENOTSUP. (#26743)
+- When building code with both Wasm Workers and pthreads (hybrid mode) it is now
+  possible to call most of the core pthread APIs (e.g. lock, condvar, etc) from
+  a Wasm Worker.  This mode increases the memory used by each Wasm Worker by
+  ~500 bytes (in the same way that declaring ~500 bytes of TLS data would).
+  (#26757)
+- The filesystem opteration that create new files now honor the global umask,
+  which defaults for 0o222 and can be updated by calling `umask()`. (#50739)
+
+5.0.6 - 04/14/26
+----------------
 - The minimum version of node supported by the generated code was bumped from
   v12.22.0 to v18.3.0. (#26604)
-- The DETERMINISIC settings was marked as deprecated (#26653)
+- The DETERMINISTIC settings was marked as deprecated (#26653)
 - Some musl-internal headers are no longer installed into the sysroot include
   directory.  In particular, `syscall_arch.h` no longer exists, but can be
   replaced with `emscripten/syscalls.h`. (#26658)
@@ -117,10 +274,9 @@ See docs/process.md for more on how version tagging works.
   inconsistent with JS and was not supported in browser devtools. We plan to
   provide this information using Scopes encoding later. (#26149)
 - compiler-rt, libcxx, libcxxabi, libunwind, and llvm-libc were updated to LLVM
-  21.1.8. (#26036, #26045, #26058, and #26151)
+  21.1.8. (#26036, #26045, #26058, #26151)
 - Calling pthread_create in a single-threaded build will now return ENOTSUP
   rather then EAGAIN.  (#26105)
-- compiler-rt and libunwind were updated to LLVM 21.1.8. (#26036 and #26045)
 - A new `-sEXECUTABLE` setting was added which adds a #! line to the resulting
   JavaScript and makes it executable.  This setting defaults to true when the
   output filename has no extension, or ends in `.out` (e.g. `a.out`) (#26085)
@@ -365,7 +521,7 @@ See docs/process.md for more on how version tagging works.
   example, when you run `pkg-config --list-all` or `pkg-config --cflags
   <portname>`. Bare in mind that the correct PKG_CONFIG_PATH needs to be set for
   this to work.  One way to do this is to run `emmake pkg-config`. (#24426)
-- libcxx, libcxxabi, and compiler-rt were updated to LLVM 20.1.4. (#24346 and
+- libcxx, libcxxabi, and compiler-rt were updated to LLVM 20.1.4. (#24346,
   #24357)
 - Emscripten will not longer generate trampoline functions for Wasm exports
   prior to the module being instantiated.  Storing a reference to a Wasm export
@@ -552,7 +708,7 @@ See docs/process.md for more on how version tagging works.
   new proposal by default yet. This option replaces the existing
   `-sWASM_EXNREF`, whose meaning was the opposite.
 - compiler-rt, libcxx, libcxxabi, and libunwind were updated to LLVM 19.1.6.
-  (#22937, #22994, and #23294)
+  (#22937, #22994, #23294)
 - The default Safari version targeted by Emscripten has been raised from 14.1
   to 15.0 (the `MIN_SAFARI_VERSION` setting) (#23312). This has several effects:
   - The Wasm nontrapping-fptoint feature is enabled by default. Clang will
@@ -801,7 +957,7 @@ See docs/process.md for more on how version tagging works.
 3.1.57 - 04/10/24
 -----------------
 - libcxx, libcxxabi, libunwind, and compiler-rt were updated to LLVM 18.1.2.
-  (#21607, #21638, and #21663)
+  (#21607, #21638, #21663)
 - musl libc updated from v1.2.4 to v1.2.5. (#21598)
 - In `MODULARIZE` mode we no longer export the module ready promise as `ready`.
   This was previously exposed on the Module for historical reasons even though
@@ -882,8 +1038,7 @@ See docs/process.md for more on how version tagging works.
   community and supported on a "best effort" basis. See 
   `tools/ports/contrib/README.md` for details.A first contrib port is 
   available via `--use-port=contrib.glfw3`: an emscripten port of glfw written 
-  in C++ with many features like support for multiple windows. (#21244 and 
-  #21276)
+  in C++ with many features like support for multiple windows. (#21244, #21276)
 - Added concept of external ports which live outside emscripten and are
   loaded on demand using the syntax `--use-port=/path/to/my_port.py` (#21316)
 - `embuilder` can now build ports with options as well as external ports using
@@ -991,7 +1146,7 @@ See docs/process.md for more on how version tagging works.
   For those that would rather perform transpilation separately outside of
   emscripten you can use the `-sPOLYFILL=0` setting. (#20700)
 - libcxx, libcxxabi, libunwind, and compiler-rt were updated to LLVM 17.0.4.
-  (#20705, #20707, and #20708)
+  (#20705, #20707, #20708)
 - Remove `BENCHMARK` setting. That has not been used by the benchmark suite for
   some time now (at least not by default), and is much less useful these days
   given lazy compilation in VMs (which makes it impossible to truly benchmark
@@ -1270,7 +1425,7 @@ See docs/process.md for more on how version tagging works.
 - Added new linker option `-sEXCEPTION_STACK_TRACES` which will display a stack
   trace when an uncaught exception occurs. This defaults to true when
   `ASSERTIONS` is enabled. This option is mainly for the users who want only
-  exceptions' stack traces without turning `ASSERTIONS` on. (#18642 and #18535)
+  exceptions' stack traces without turning `ASSERTIONS` on. (#18642, #18535)
 - `SUPPORT_LONGJMP`'s default value now depends on the exception mode. If Wasm
   EH (`-fwasm-exceptions`) is used, it defaults to `wasm`, and if Emscripten EH
   (`-sDISABLE_EXCEPTION_CATCHING=0`) is used or no exception support is used, it
@@ -1419,7 +1574,7 @@ See docs/process.md for more on how version tagging works.
 3.1.24 - 10/11/22
 -----------------
 - In Wasm exception mode (`-fwasm-exceptions`), when `ASSERTIONS` is enabled,
-  uncaught exceptions will display stack traces and what() message. (#17979 and
+  uncaught exceptions will display stack traces and what() message. (#17979,
   #18003)
 - It is now possible to specify indirect dependencies on JS library functions
   directly in C/C++ source code.  For example, in the case of a EM_JS or EM_ASM
@@ -1728,7 +1883,7 @@ See docs/process.md for more on how version tagging works.
   `-sDISABLE_EXCEPTION_CATCHING=0`). When using Wasm EH with Wasm SjLj, there is
   one restriction that you cannot directly call `setjmp` within a `catch`
   clause. (Calling another function that calls `setjmp` is fine.)
-  (#14976 and #16072)
+  (#14976, #16072)
 
 3.1.2 - 01/20/2022
 ------------------
@@ -3735,7 +3890,7 @@ v1.36.6: 8/8/2016
  - Fixed inconsistencies in fullscreen API signatures (#4310, #4318, #4379)
  - Changed the behavior of Emscripten WebGL createContext() to not forcibly set
    CSS style on created canvases, but let page customize the style themselves
-   (#3406, #4194 and #4350, #4355)
+   (#3406, #4194, #4350, #4355)
  - Adjusted the reported GL_VERSION field to adapt to the OpenGL ES
    specifications (#4345)
  - Added support for GLES3 GL_MAJOR/MINOR_VERSION fields. (#4368)

diff --git a/Makefile b/Makefile
@@ -1,7 +1,11 @@
 VERSION = $(shell cat emscripten-version.txt | sed s/\"//g)
-DESTDIR ?= ../emscripten-$(VERSION)
+DESTDIR ?= out/emscripten-$(VERSION)
 DISTFILE = emscripten-$(VERSION).tar.bz2
 
+no_default:
+	@echo 'Error: You must specify an explicit make target (e.g. `dist` or `install`)'
+	@exit 1
+
 dist: $(DISTFILE)
 
 install:

diff --git a/README.md b/README.md
@@ -6,8 +6,8 @@ GitHub CI status: [![CircleCI](https://circleci.com/gh/emscripten-core/emscripte
 
 Chromium builder status: [emscripten-releases](https://ci.chromium.org/p/emscripten-releases)
 
-Overview
---------
+
+# Overview
 
 Emscripten compiles C and C++ to [WebAssembly](https://webassembly.org/) using
 [LLVM](https://en.wikipedia.org/wiki/LLVM) and
@@ -26,8 +26,58 @@ While Emscripten mostly focuses on compiling C and C++ using
 compilers (for example, Rust has Emscripten integration, with the
 `wasm32-unknown-emscripten` target).
 
-License
--------
+
+# Getting Started
+
+For detailed instructions and tutorials, visit the [Emscripten Website](https://emscripten.org).
+
+## 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](https://emscripten.org/docs/getting_started/downloads.html) 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:
+    ```bash
+    ./bootstrap.py
+    ```
+    For more details, see the [developer guide](https://emscripten.org/docs/contributing/developers_guide.html).
+
+## Using the compiler
+
+Run `emcc` like you would `gcc` or `clang`:
+
+```bash
+$ 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](https://nodejs.org/) (or
+[Deno](https://deno.com/) or [Bun](https://bun.sh/)).
+
+Emscripten can also generate a sample HTML page that then loads the JavaScript:
+
+```bash
+$ 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](CONTRIBUTING.md) and the [Contributing section on the
+website](https://emscripten.org/docs/contributing/contributing.html).
+
+
+# License
 
 Emscripten is available under 2 licenses, the MIT license and the
 University of Illinois/NCSA Open Source License.

diff --git a/bootstrap b/bootstrap