Merge branch 'main' into wasmfs-noderawfs-abspath

Author: kleisauke

.circleci/config.yml

@@ -363,7 +363,6 @@ commands:
       - upload-test-results
   setup-macos:
     steps:
-      - macos/install-rosetta
       - run:
           name: Install brew package dependencies
           environment:
@@ -1101,11 +1100,6 @@ jobs:
           test_targets: "browser64_4gb skip:browser64_4gb.test_mainScriptUrlOrBlob*"
   test-browser-firefox:
     executor: ubuntu-lts
-    environment:
-      # Deserializing a growable SharedArrayBuffer is currently broken in Firefox.
-      # See: https://github.com/emscripten-core/emscripten/issues/27118
-      # See: https://bugzilla.mozilla.org/show_bug.cgi?id=2021136
-      EMTEST_LACKS_GROWABLE_ARRAYBUFFERS: "1"
     steps:
       - prepare-for-tests
       - run-tests-firefox:
@@ -1270,6 +1264,7 @@ jobs:
       EMTEST_SKIP_WASM64: "1"
       EMTEST_SKIP_SCONS: "1"
       EMTEST_SKIP_RUST: "1"
+      EMTEST_SKIP_NODE_25: "1"
       # Some native clang tests assume x86 clang (e.g. -sse2)
       EMTEST_LACKS_NATIVE_CLANG: "1"
       EMCC_SKIP_SANITY_CHECK: "1"

.github/ISSUE_TEMPLATE/feature_depreaction.md

@@ -9,7 +9,8 @@ assignees: ''
 
 Tracking issue for the deprecation and removal of <FEATURE>.
 
-The process for deprecating and removing features from emscripten is laid out out in https://github.com/emscripten-core/emscripten/blob/main/docs/process.md#deprecating-settings-and-features.
+The process for deprecating and removing features from emscripten is laid out
+in https://github.com/emscripten-core/emscripten/blob/main/CONTRIBUTING.md#deprecating-settings-and-features.
 
 At any point in the process we may decide to delay or abort the deprecation and close this issue.
 

ChangeLog.md

@@ -18,8 +18,37 @@ to browse the changes between the tags.
 
 See docs/process.md for more on how version tagging works.
 
-6.0.2 (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,
@@ -73,9 +102,6 @@ See docs/process.md for more on how version tagging works.
   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)
-- The `GROWABLE_ARRAYBUFFERS` setting now support both `=1` (auto-detect and
-  use the feature) and `=2` (unconditionally use the feature). The second mode
-  is still useful for avoiding the overhead in multi-threaded builds. (#27096)
 
 6.0.0 - 06/04/26
 ----------------
@@ -101,7 +127,7 @@ See docs/process.md for more on how version tagging works.
   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 and #26983)
+- 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
@@ -248,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)
@@ -496,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
@@ -683,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
@@ -932,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
@@ -1013,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
@@ -1122,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
@@ -1401,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
@@ -1550,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
@@ -1859,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
 ------------------
@@ -3866,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)

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.