Roll v8 from 8dc65ee0a4e0 to 1c7d3a94fc05 (25 revisions)

https://chromium.googlesource.com/v8/v8.git/+log/8dc65ee0a4e0..1c7d3a94fc05

2023-11-10 lpardosixtos@microsoft.com [shared-struct] Add Atomics.Mutex.lockWithTimeout API
2023-11-10 lpardosixtos@microsoft.com [shared-struct] Don't coerce Atomics.Condition.wait timeout into number.
2023-11-10 lpardosixtos@microsoft.com [shared-struct] Support timeout for sync locks in Atomics.Mutex.
2023-11-10 olivf@chromium.org [maglev] Fix another phi untagging skipping smi check
2023-11-10 olivf@chromium.org [static-roots] Use SR in GetSharedFunctionInfoBytecodeOrBaseline
2023-11-10 v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update V8 DEPS (trusted)
2023-11-10 machenbach@chromium.org Revert "[wasm] Introduce caching timeout"
2023-11-10 machenbach@chromium.org Revert "Reland "[wasm][x64] Run JS imports on the central stack""
2023-11-10 thibaudm@chromium.org Reland "[wasm][x64] Run JS imports on the central stack"
2023-11-10 evih@chromium.org [wasm][turboshaft] Refactor DataView related imports
2023-11-10 bikineev@chromium.org cppgc: Never free normal pages on memory-reducing GCs
2023-11-10 olivf@chromium.org [maglev] Hoist some phi input untagging out of loops
2023-11-10 clemensb@chromium.org [wasm] Introduce caching timeout
2023-11-10 clemensb@chromium.org Reland "[wasm] Drop mostly-unused argument to BrOrRet"
2023-11-10 clemensb@chromium.org Revert "[wasm] Drop mostly-unused argument to BrOrRet"
2023-11-10 clemensb@chromium.org [wasm] Drop mostly-unused argument to BrOrRet
2023-11-10 thibaudm@chromium.org [wasm][exnref] Implement try-table in Liftoff
2023-11-10 mliedtke@chromium.org [turboshaft][arm64] Port InstructionSelector part 4
2023-11-10 yahan@iscas.ac.cn [riscv] Enable some SIMD test cases and enable turboshaft/instruction-selection on riscv64
2023-11-10 dinfuehr@chromium.org [heap] Remove TryExpandImpl methods
2023-11-10 manoskouk@chromium.org [turboshaft][wasm] Inlining improvements
2023-11-10 liviurau@chromium.org [test262] Clean-up staging folder on import.
2023-11-10 dmercadier@chromium.org [turboshaft] Do not clone branches that Branch on a single Constant
2023-11-10 ahaas@chromium.org [wasm] Handle calls to imports in wrapper inlining
2023-11-10 machenbach@chromium.org [infra] Remove mac-arm64 simulator bots

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: I95980e3bda61a3de7211ba8bd0fd65a12163b2b4
Reviewed-on: https://chromium-review.googlesource.com/c/emscripten-releases/+/5022174
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
1 file changed
tree: 42a9b725dad81acb8fe56d31290ffce5e33af7f0
  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 and 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.