Roll v8 from 6c5b752d1c02 to 4683daaf7749 (19 revisions)

https://chromium.googlesource.com/v8/v8.git/+log/6c5b752d1c02..4683daaf7749

2024-03-28 adamk@chromium.org Remove APIs that have been deprecated for more than a year
2024-03-28 v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update V8 DEPS (trusted)
2024-03-28 thibaudm@chromium.org [wasm] Set missing turboshaft wrapper node origins
2024-03-28 syg@chromium.org [api] Deprecate v8::BackingStore::Reallocate
2024-03-28 nikolaos@chromium.org [test] Fix test failing with no shared cage
2024-03-28 mlippautz@chromium.org [heap] Fix C++ heap snapshot for new JS API wrappers
2024-03-28 saelo@chromium.org [sandbox] First step towards fine-grained type tags for Foreigns
2024-03-28 mfarazma@redhat.com [turboshaft] Fix compilation with gcc
2024-03-28 saelo@chromium.org [sandbox] Turn DeoptimizationData into a ProtectedFixedArray
2024-03-28 cffsmith@google.com [fuzzilli] Clean up prints
2024-03-28 evih@chromium.org [wasm][fuzzer][cleanup] Change enum classes to enum
2024-03-28 nicohartmann@chromium.org [turboshaft] V<>ify Turboshaft
2024-03-28 mfarazma@redhat.com [turboshaft] Fix a typo on big endian
2024-03-28 v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update fuzztest (trusted)
2024-03-28 v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update V8 DEPS (trusted)
2024-03-28 yangwenming@bytedance.com [riscv] fix RISCV-build on Mac64.
2024-03-27 lpardosixtos@microsoft.com [shared-struct] Expose number of mutex waiters for testing.
2024-03-27 nikolaos@chromium.org [ro-promotion][sandbox] Fix promotion of code table entries
2024-03-27 mlippautz@chromium.org Add benchmark for bindings operations

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: Idfe919f36b6f47c4ce445017e9088acf3c9cd653
Reviewed-on: https://chromium-review.googlesource.com/c/emscripten-releases/+/5405216
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: 1861c3977ee71998f13b8f32ee15a1b94411eeec
  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.