Roll v8 from 5f1342c20b59 to 05fb4036251c (36 revisions)

https://chromium.googlesource.com/v8/v8.git/+log/5f1342c20b59..05fb4036251c

2024-03-19 dmercadier@chromium.org [turboshaft][x64] Port/enable ISEL unittests part 1
2024-03-19 victorgomes@chromium.org [maglev] Use a DisjointSet for allocation dependencies
2024-03-19 leszeks@chromium.org [interpreter] Microoptimise for-in bytecodes
2024-03-19 nicohartmann@chromium.org [turbofan] Remove unused parts of the TurboFan backend
2024-03-19 leszeks@chromium.org Revert "[heap] Minor cleanups around HeapController"
2024-03-19 zequanwu@google.com Add .att_syntax for inline asm under windows x64.
2024-03-19 ishell@chromium.org [api][tests] Update tests for new interceptors Api, pt.2
2024-03-19 omerkatz@chromium.org [heap] Minor cleanups around HeapController
2024-03-19 evih@chromium.org [wasm-compile-fuzzer] Refactor GenerateRandomWasmModule (PART 7)
2024-03-19 evih@chromium.org [wasm-compile-fuzzer] Rename WasmGenerator class to BodyGen (PART 6)
2024-03-19 seokho@chromium.org Optimize Math.hypot for arguments length <= 3
2024-03-19 joyee@igalia.com [snapshot] allow NativeContext serialization to be deferred
2024-03-19 mliedtke@chromium.org [turboshaft] DeoptimizeIfOp: pretty print options
2024-03-19 jkummerow@chromium.org [test][asm.js] Robustify mjsunit/asm/log-lazy-code
2024-03-19 leszeks@chromium.org Reland "[object] Fast path for adding props with existing transition"
2024-03-19 ishell@chromium.org [api][wasm] Update Wasm for new interceptors Api
2024-03-19 ahaas@chromium.org [profiler] Avoid data race in test by increasing sampling interval
2024-03-19 ishell@chromium.org [api][tests] Update tests for new interceptors Api, pt.1
2024-03-19 pthier@chromium.org [regexp] Check for stackoverflow in RegExpLookaround::ToNode
2024-03-18 victorgomes@chromium.org Revert "[maglev] Enable escape analysis"
2024-03-18 victorgomes@chromium.org Revert "[maglev] Support arguments object in inlined function"
2024-03-18 jkummerow@chromium.org [wasm] Fix ClearWeakScriptHandleTask shutdown issue
2024-03-18 leszeks@chromium.org Revert "[maglev] Inline allocation of arguments object inside inlined functions"
2024-03-18 ishell@chromium.org [zone-stats] Enable resource integrity check for pako_inflate.js
2024-03-18 jkummerow@chromium.org [wasm-gc][liftoff] Fix off-by-one in RefAsNonNull
2024-03-18 ahaas@chromium.org [wasm][gc] Scan the code field of the WasmInternalFunction
2024-03-18 jkummerow@chromium.org Fix building x64 with GCC-12
2024-03-18 jdapena@igalia.com [heap] Add method GetLineEnds
2024-03-18 olivf@chromium.org [tiering] Prioritize already queued turbofan compilation jobs
2024-03-18 clemensb@chromium.org [BUILD] Add templates for v8 and wasm fuzzers
2024-03-18 szuend@chromium.org [inspector] Change command line API allow list to deny list
2024-03-18 nicohartmann@chromium.org [turboshaft] Ship instruction selection on remaining platforms
2024-03-18 olivf@chromium.org [tiering] Back-off profile guided tiering
2024-03-18 victorgomes@chromium.org [maglev] Inline allocation of arguments object inside inlined functions
2024-03-18 pierre.langlois@arm.com [arm64][cfi] Add "cc" to clobber list in authentication inline asm
2024-03-18 mfarazma@redhat.com [turboshaft] Fix optimization on big endian platforms

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: I2f4f6aac19a6ffb20ff3eff660eed617823da12b
Reviewed-on: https://chromium-review.googlesource.com/c/emscripten-releases/+/5380729
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: e1dd12ab1918f03751d01fb47dba511fa2043e82
  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.