Google Git
Sign in
chromium / emscripten-releases / 6dad22efe19f68793d2fb201de31913af42316a0
commit6dad22efe19f68793d2fb201de31913af42316a0[log] [tgz]
authorchromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>Mon Jan 16 23:19:24 2023
committerEmscripten-releases LUCI CQ <emscripten-releases-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jan 17 01:46:52 2023
tree216072de34e9b25259255c264d9bd0adc6d64b87
parentd3350fdbd695bccad2e15863166993ed8aba0d2e [diff]
Roll llvm-project from dc21ce44047a to 52f6ed099cba (17 revisions)

https://chromium.googlesource.com/external/github.com/llvm/llvm-project.git/+log/dc21ce44047a..52f6ed099cba

2023-01-16 jyknight@google.com Move Personalities array from MachineModuleInfo to DwarfCFIException.
2023-01-16 jyknight@google.com FastISel: remove EH_LABEL skipping code.
2023-01-16 joker.eph@gmail.com Revert "Refactor OperationName to use virtual tables for dispatch (NFC)"
2023-01-16 martin@martin.st [clang] [MinGW] Avoid adding <base>/include and <base>/lib when cross compiling
2023-01-16 joeloser@fastmail.com [llvm][ADT] Replace uses of `makeMutableArrayRef` with deduction guides
2023-01-16 joker.eph@gmail.com Fix crash in Spirv -lower-host-to-llvm pass
2023-01-16 ravishankarm@google.com [mlir][TilingInterface] Fix use after free error from D141028.
2023-01-16 szakharin@nvidia.com [mlir][llvmir] Fixed MDNode uniquing during TBAA translation.
2023-01-16 hgreving@google.com [mlir:LLVM] Fix minor bug, missing cconv translation
2023-01-16 lei@ca.ibm.com [P10] Fix the implementation for BRH
2023-01-16 ramkrishnan.nk@huawei.com [LoopInterchange] Correcting the profitability check
2023-01-16 zinenko@google.com [mlir] accept values with result numbers in gpu.launch_func
2023-01-16 jhuber6@vols.utk.edu [nvptx-arch] Dynamically load the CUDA runtime if not found during the build
2023-01-16 jhuber6@vols.utk.edu [amdgpu-arch] Dynamically load the HSA runtime if not found during the build
2023-01-16 kli@ca.ibm.com [flang][NFC] Fix typo in Cray pointee error message
2023-01-16 david.green@arm.com [AArch64] Add tests for forming abd from wrap flags and min/max. NFC
2023-01-16 llvm-dev@redking.me.uk Silence signed/unsigned comparison warnings. NFC.

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 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: I12f23b173610f3b14c0687636211f821d89647b5
Reviewed-on: https://chromium-review.googlesource.com/c/emscripten-releases/+/4169613
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: 216072de34e9b25259255c264d9bd0adc6d64b87
  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.