Roll v8 from 32d3f8c07ee3 to 3c06a07680f8 (32 revisions) https://chromium.googlesource.com/v8/v8.git/+log/32d3f8c07ee3..3c06a07680f8 2026-08-05 hao.a.xu@intel.com Reland "[sparkplug+] Add ConstantFromStringPrototype handler" 2026-08-05 yuheng.wei@intel.com [sparkplug+] Support sparkplug+ for unary operations 2026-08-04 sam.parker@arm.com [compiler] Reduce I32x4DotI8x16S 2026-08-04 dmercadier@chromium.org [turbolev] Cleanup CheckLoopPhiInvalidation 2026-08-04 olivf@chromium.org [array-buffer] Fix serializing immutable buffers with no backing store 2026-08-04 dmercadier@chromium.org [maglev] Fix bailouts during TryReduceArrayIteratingBuiltin loop 2026-08-04 sam.parker@arm.com [compiler] Run WasmShuffleAnalyzer once. 2026-08-04 guybedford@gmail.com [wasm] Generalize WasmModuleObject::Compile options with source URL 2026-08-04 etiennep@chromium.org [inspector] Fix crash on interleaved debug breaks with scheduled OOM 2026-08-04 jgruber@chromium.org [regexp] Reset flags between negative lookaround branches 2026-08-04 dlehmann@chromium.org [wasm][sandbox] Fix call_indirect feedback and module lookup 2026-08-04 machenbach@chromium.org [jetstream3] Fix benchmark skip parameter 2026-08-04 arashk@chromium.org [sandbox] Add SwissTable* and InstallBaselineCode to verifier blocklist 2026-08-04 olivf@chromium.org [tiering] Stretch OSR interrupt budget while tiering is in progress 2026-08-04 jgruber@chromium.org [test] Add a quiet mode, auto-enabled for AI agents 2026-08-04 thibaudm@chromium.org [wasm] Skip minor GC stack iteration for suspended stacks without young pointers 2026-08-04 jgruber@chromium.org [regexp] Don't share named-capture groups objects via the results cache 2026-08-04 olivf@chromium.org [array-buffer] Zero-copy immutable ArrayBuffer serialization 2026-08-04 ahaas@chromium.org [gn] Fix v8_use_perfetto 2026-08-04 olivf@chromium.org [maglev] Cleanup loop interrupts 2026-08-04 sam.parker@arm.com [compiler][arm64] Instruction latencies. 2026-08-04 leese@chromium.org Support debugging top level exceptions in modules 2026-08-04 dmercadier@chromium.org [test] Fix flaky assertOptimized in mjsunit/turbolev/typed-arrays 2026-08-04 jgruber@chromium.org [bigint] Add a fold fast path to CachedMod for near-power-of-two 2026-08-04 leszeks@chromium.org [compiler] Clean up LiveRange bitfields and widen AssignedRegisterField to 8 bits 2026-08-04 dmercadier@chromium.org [test] Skip regress-539984773 for isolates and stress background compile 2026-08-04 dmercadier@chromium.org [turboshaft] Less effects for MajorGCForCompilerTesting 2026-08-04 olivf@chromium.org [base] Optimize Relaxed_Memset with word-sized atomic stores 2026-08-04 dmercadier@chromium.org [turboshaft] Add another test for issue 527385397 2026-08-04 olivf@chromium.org [maglev] Ensure from_index is a Smi in TryWithArrayIterationArgs 2026-08-04 v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update V8 DEPS (trusted) 2026-08-04 v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update fuzztest (trusted) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/v8-emscripten-releases Please CC dschuff@google.com,wasm-waterfall@grotations.appspotmail.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Tbr: wasm-waterfall@grotations.appspotmail.com Change-Id: Ida02f74139e4f371d27b30bfd6ad5e7853628aec Reviewed-on: https://chromium-review.googlesource.com/c/emscripten-releases/+/8199135 Bot-Commit: chromium-autoroll@skia-public.iam.gserviceaccount.com <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll@skia-public.iam.gserviceaccount.com <chromium-autoroll@skia-public.iam.gserviceaccount.com>
This is meta-repository which brings together all the repositories needed to produce an emscripten release. The revisions used in each release are tracked in a DEPS file (See depot_tools for more information). This file contains a history of revisions that have been built and tested together and represent a known good state.
Each release is automatically built and uploaded to to Google Cloud Storage and can be used standalone or with emsdk.
The build status for the automated builds can be seen here
Install depot_tools and then check out: gclient config https://chromium.googlesource.com/emscripten-releases (Do this only once)
Update working trees:
git pullgclient syncUpdate a DEPS entry:
cd emscripten-releasesgit checkout -b <branch>roll-dep emscripten-releases/llvm-projectgit cl uploadThe argument to roll-dep must match one of the keys in the ‘deps’ dictionary in the DEPS file. See roll-dep -h for more options.
src/This directory was forked from the WebAssembly waterfall repo That repo was retired because it was only used by emscripten-releases.
depot_tools. Follow the instructionspkg-config if you don't have it installed already, e.g. # apt install pkg-configpython src/build.pyBuild.py has 3 types of actions:
Each of these types has multiple steps (e.g. a build step for each component). If you run build.py with no arguments, it will run all the sync, build, and test steps. If you make a change and only want to run a subset of steps, you can apply filters from the command line, via exclusions (to prevent specified steps from running) or inclusions (to run only the specified steps). Sync, build, and test exclusions are specified separately. For example:
$ src/build.py --no-sync --build-exclude=llvm$ src/build.py --sync-include=binaryen --build-include=llvm,binaryen --test-exclude=emtest,emtest-asmThe script should throw an error if you specify nonexistent steps or if you specify both includes and excludes for the same type of action.
When run, the script creates a directory src/work inside the waterfall‘s git checkout. All modifications are made inside this directory (checking and out and building the sources, as well as the test builds and execution results). You can also use the git checkouts (e.g. src/work/llvm) with your own branches; the sync steps will check out the latest revision from the script’s remote repositories but will not overwrite or destroy any local work.