Google Git
Sign in
chromium / emscripten-releases / 81f52ef6abaa5aecaa16362e40e045b0ac41472c
commit81f52ef6abaa5aecaa16362e40e045b0ac41472c[log] [tgz]
authorchromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>Sat Jun 03 05:21:54 2023
committerEmscripten-releases LUCI CQ <emscripten-releases-scoped@luci-project-accounts.iam.gserviceaccount.com>Sat Jun 03 08:01:27 2023
treefb69680cac8fb732bb5c67a3e587b839d0af0c0b
parent2065a5f3bf079e83677170cb9ace493f798e8afa [diff]
Roll llvm-project from d6f994acb3d5 to fb7f50a0c38a (7 revisions)

https://chromium.googlesource.com/external/github.com/llvm/llvm-project.git/+log/d6f994acb3d5..fb7f50a0c38a

2023-06-03 kazu@google.com [CodeGen] Use DenseMapBase::lookup (NFC)
2023-06-03 yeting.kuo@sifive.com [RISCV] Avoid illegal DAG combination for strict-fp nodes.
2023-06-03 peiming@google.com [mlir][sparse] fix crash when using sparse_tensor::UnaryOp and ReduceOp.
2023-06-03 lntue@google.com [libc][NFC] Add LIBC_INLINE and attribute.h header includes to targets' FMA.h.
2023-06-03 ajcbik@google.com [mlir][sparse] fixed bug with unary op, dense output
2023-06-02 caslyn@google.com [scudo] Add 'inline' to static secondary.h function
2023-06-02 thakis@chromium.org [gn] port 6b3ae49d3243

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/llvm-project-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: I713505f7c3252c45a3e498078e41ffcfd399724e
Reviewed-on: https://chromium-review.googlesource.com/c/emscripten-releases/+/4585456
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: fb69680cac8fb732bb5c67a3e587b839d0af0c0b
  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.