Roll v8 from 1760d68df48f to 3b3de10eaf9b (21 revisions)

https://chromium.googlesource.com/v8/v8.git/+log/1760d68df48f..3b3de10eaf9b

2024-10-15 etiennep@chromium.org [gc] Fix allocation sample
2024-10-15 nikolaos@chromium.org [handles] Migrate out-of-stack handles, part 1
2024-10-15 v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update V8 DEPS (trusted)
2024-10-15 saelo@chromium.org Ignore expose_async_hooks during fuzzing
2024-10-15 syg@chromium.org [parser] Fix 'await'-as-ident handling in eval
2024-10-15 paolosev@microsoft.com [wasm] Enable trap handling on ARM64 Windows
2024-10-15 leszeks@chromium.org Revert "[wasm] F32x4Add is not commutative"
2024-10-15 jkummerow@chromium.org [wami] mjsunit mode: fix duplicate function export
2024-10-15 ahaas@chromium.org [wasm] F32x4Add is not commutative
2024-10-15 jkummerow@chromium.org [wasm] "ValueType" now is module-specific
2024-10-15 clemensb@chromium.org [wasm] Rename --wasm-native-module-cache-enabled flag
2024-10-15 clemensb@chromium.org [wasm][streaming] Fix --no-wasm-native-module-cache-enabled
2024-10-15 saelo@chromium.org [string] Use an unsigned integer for String::length
2024-10-15 clemensb@chromium.org [wasm] Serialize detected features
2024-10-15 olivf@chromium.org [maglev] Fix for: "Constantfold `bool == const`"
2024-10-15 ishell@chromium.org [d8] Fix handling of termination in onmessage from Workers
2024-10-15 verwaest@chromium.org [parser] Simplify variable lookup caching
2024-10-15 dima00782@gmail.com [isolate-groups][sandbox] Replace CPT global with a per isolate group.
2024-10-15 v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update ICU (trusted)
2024-10-15 v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update V8 DEPS (trusted)
2024-10-15 jie.pan@intel.com [wasm-simd][x64] Optimize F32x4UConvertI32x4

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: Id13a7f19b100c8bc37d92141d6d1baad881760b5
Reviewed-on: https://chromium-review.googlesource.com/c/emscripten-releases/+/5935887
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
1 file changed
tree: ea87ac8f39f15fd2535d9fc75422c3b3ea8f6043
  1. src/
  2. third_party/
  3. tools/
  4. .gitignore
  5. bots.json
  6. codereview.settings
  7. DEPS
  8. DEPS.tagged-release
  9. PRESUBMIT.py
  10. README.md
README.md

Emscripten Releases

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

Updating DEPS entries

Install depot_tools and then check out: gclient config https://chromium.googlesource.com/emscripten-releases (Do this only once)

Update working trees:

  • git pull
  • gclient sync

Update a DEPS entry:

  • cd emscripten-releases
  • git checkout -b <branch>
  • roll-dep emscripten-releases/llvm-project
  • git cl upload

The 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.

༼ ༎ຶ ෴ ༎ຶ༽ Build and test scripts in src/

This directory was forked from the WebAssembly waterfall repo That repo was retired because it was only used by emscripten-releases.

How do I run it?

  1. Get the sources
  2. Install depot_tools. Follow the instructions
  3. Install pkg-config if you don't have it installed already, e.g. # apt install pkg-config
  4. Run build.py python src/build.py

Build.py has 3 types of actions:

  • downloading/updating sources for tools and engines (sync)
  • building those sources (build)
  • running tests against them (test).

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:

  1. Do not sync any sources, build everything except LLVM, and run all tests: $ src/build.py --no-sync --build-exclude=llvm
  2. Sync only binaryen, build LLVM and Binaryen, run everything other than the emscripten testsuites: $ src/build.py --sync-include=binaryen --build-include=llvm,binaryen --test-exclude=emtest,emtest-asm

The 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.