6.0.8

Gerstep/HumanCompiler6.0.8Aug 20, 2026by emscripten-bot

Upgrading?

AI Summary

Emscripten update stabilizing JSPI, adding epoll support, and removing legacy settings.

Key Highlights

  • `JSPI` setting is no longer considered experimental.
  • Added support for `epoll` on the legacy JS filesystem, including edge-triggered modes.
  • Removed the deprecated `LEGALIZE_JS_FFI` setting and the `SOCKET_WEBRTC` setting.
  • `WASM_BIGINT` is now deprecated.

Breaking Changes

  • Removed `LEGALIZE_JS_FFI` setting
  • Removed `SOCKET_WEBRTC` setting

New Features

  • epoll support for legacy JS filesystem
  • JSPI stabilization

Full Release Notes

## What's Changed
- The `JSPI` setting is no longer considered experimental, and the compiler
  diagnostic warning has been removed. (#27559)
- Added support for `epoll` (`epoll_create1`/`epoll_ctl`/`epoll_wait`/
  `epoll_pwait`) on the legacy (non-WASMFS) JS filesystem, including
  level- and edge-triggered modes, `EPOLLONESHOT`, `EPOLLEXCLUSIVE`,
  `EPOLLRDHUP`, nesting, and blocking waits under `PROXY_TO_PTHREAD`,
  `ASYNCIFY`, and `JSPI`. (#27207)
- The deprecated `LEGALIZE_JS_FFI` setting was completely removed and moved to
  legacy settings.  This behaviour of lowering away i64 values at the
  Wasm bounary is still used when `WASM_BIGINT` is disabled.  However
  disabling of `WASM_BIGINT` itself should only be needed under `-sWASM=0`
  (where it is automatically disabled). (#27568)
- The `SOCKET_WEBRTC` setting was removed (#27367)
- `WASM_BIGINT` was deprecated. BigInt integration is standard and enabled by
  default across all supported engines; it should now only ever be disabled
  implicitly when targeting JavaScript via `-sWASM=0`. (#27558)


## Contributors
Thanks to the following contributors: @sbc100 (10) @guybedford (2) @brendandahl (1)

**Full Changelog**: https://github.com/emscripten-core/emscripten/compare/6.0.7...6.0.8

Related Repositories