Roll v8 from 0cdb6d0c1259 to ff91daca6c2a (26 revisions)

https://chromium.googlesource.com/v8/v8.git/+log/0cdb6d0c1259..ff91daca6c2a

2023-04-06 syg@chromium.org [shared-struct] Fix elements for shared structs
2023-04-05 etiennep@chromium.org [task] Move source location and use it in v8 platform
2023-04-05 syg@chromium.org Revert "[builtins-pgo] Enable builtins PGO for Windows and gcc builds"
2023-04-05 pbos@chromium.org Guard SumFreeLists() inside FreeList::Available()
2023-04-05 verwaest@chromium.org Reland^2 "[tiering] Don't increase budgets on forward jumps"
2023-04-05 verwaest@chromium.org [ic] Only cache access to own global proxies
2023-04-05 nikolaos@chromium.org [heap] Fix CSS visitor after markbit cleanup
2023-04-05 victorgomes@chromium.org [maglev] Support maglev inlining for %OptimizeOsr
2023-04-05 mslekova@chromium.org [fastcall] Disable fast path when exception can be thrown
2023-04-05 leszeks@chromium.org Revert "[code] Allocate IStreams before Code"
2023-04-05 jgruber@chromium.org [code] Allocate IStreams before Code
2023-04-05 pthier@chromium.org Remove CanonicalHandleScope
2023-04-05 victorgomes@chromium.org [maglev] Support OSRing inlined functions
2023-04-05 mlippautz@chromium.org [heap] Spring cleaning for BasicMemoryChunk
2023-04-05 leszeks@chromium.org Revert "Reland "[tiering] Don't increase budgets on forward jumps""
2023-04-05 dinfuehr@chromium.org [heap] Add kTracedHandles to skip those roots in IterateRoots
2023-04-05 verwaest@chromium.org Reland "[tiering] Don't increase budgets on forward jumps"
2023-04-05 ishell@chromium.org [ptr-compr] Unify shared- and multi-cage modes
2023-04-05 victorgomes@chromium.org [maglev] Disable CallSelf when TF is enabled
2023-04-05 jgruber@chromium.org [code] Clarify parts of the embedded builtin setup sequence
2023-04-05 nicohartmann@chromium.org [turboshaft] Port operations from ECL to MachineLoweringReducer (24)
2023-04-05 v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update ICU (trusted)
2023-04-05 v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update V8 DEPS (trusted)
2023-04-05 mfarazma@redhat.com PPC/s390: [code] Merge kind_specific_flags with flags
2023-04-04 syg@chromium.org [cleanup] Remove unused Scope::CollectNonLocals
2023-04-04 syg@chromium.org Revert "[tiering] Don't increase budgets on forward jumps"

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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Tbr: wasm-waterfall@grotations.appspotmail.com
Change-Id: I0e9120a52a4e3506990ab647df13f0c130aed10b
Reviewed-on: https://chromium-review.googlesource.com/c/emscripten-releases/+/4405179
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: 6f5cc1a216fc1bba975c31722b1d29969775922c
  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.