Google Git
Sign in
chromium / emscripten-releases / 6718becbd4a1e23519538242b3e45b6ce0d55207
commit6718becbd4a1e23519538242b3e45b6ce0d55207[log] [tgz]
authorchromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>Sat Jul 30 20:10:39 2022
committerEmscripten-releases LUCI CQ <emscripten-releases-scoped@luci-project-accounts.iam.gserviceaccount.com>Sat Jul 30 22:24:33 2022
treeaf08286bb9a2965d726d669880e1f93880d067be
parent4ed578174cebdfbe7e5f3b8e86e470d2bfbcc74c [diff]
Roll llvm-project from 7073ec530e55 to 1d03b2efcd40 (19 revisions)

https://chromium.googlesource.com/external/github.com/llvm/llvm-project.git/+log/7073ec530e55..1d03b2efcd40

2022-07-30 jhuber6@vols.utk.edu [Libomptarget] Disable testing map_back_race.cpp
2022-07-30 craig.topper@sifive.com [RISCV] Remove vmerges from vector ceil, floor, trunc lowering.
2022-07-30 llvm-dev@redking.me.uk [X86] Use std::tie so we can have more meaningful variable names for demanded bits/elts pairs. NFCI.
2022-07-30 i@maskray.me [ELF] Support missing relocations in RISCV::getImplicitAddend()
2022-07-30 i@maskray.me [ELF] Support missing relocations in PPC64::getImplicitAddend()
2022-07-30 aaupov@fb.com Revert "[BOLT] Ignore functions accessing false positive jump tables"
2022-07-30 kazu@google.com Use any_of (NFC)
2022-07-30 kazu@google.com Use is_contained (NFC)
2022-07-30 kazu@google.com Convert for_each to range-based for loops (NFC)
2022-07-30 kazu@google.com [bolt] Remove redundaunt virtual specifiers (NFC)
2022-07-30 kazu@google.com [bolt] Remove redundaunt control-flow statements (NFC)
2022-07-30 kazu@google.com Use nullptr instead of 0 (NFC)
2022-07-30 kazu@google.com [lld] Remove unused forward declarations (NFC)
2022-07-30 kazu@google.com [IR] Fix a header guard (NFC)
2022-07-30 kazu@google.com [ExecutionEngine] Ensure a newline at the end of a file (NFC)
2022-07-30 craig.topper@sifive.com [RISCV] Add merge operands to more RISCVISD::*_VL opcodes.
2022-07-30 craig.topper@sifive.com [RISCV] Swap the merge and mask operand order for VRGATHER*_VL and FCOPYSIGN_VL nodes.
2022-07-30 llvm-dev@redking.me.uk [X86] computeKnownBitsForTargetNode - out of range X86ISD::VSRAI doesn't fold to zero
2022-07-30 dvassiliev@accesssoftek.com [CodeGen] Fixed undeclared MISchedCutoff in case of NDEBUG and LLVM_ENABLE_ABI_BREAKING_CHECKS

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: Id6201197391a64164b4a7f82617a876880c18792
Reviewed-on: https://chromium-review.googlesource.com/c/emscripten-releases/+/3798266
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: af08286bb9a2965d726d669880e1f93880d067be
  1. src/
  2. tools/
  3. .gitignore
  4. bots.json
  5. codereview.settings
  6. DEPS
  7. DEPS.tagged-release
  8. PRESUBMIT.py
  9. 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.