Roll llvm-project from 925be4e7de84 to 114ba722c1e5 (25 revisions)

https://chromium.googlesource.com/external/github.com/llvm/llvm-project.git/+log/925be4e7de84..114ba722c1e5

2022-10-20 manigupta@google.com [mlir][NVGPU] Handle native mma.sync and ldmatrix(x4) sizes
2022-10-19 aeubanks@google.com [test][asan][Darwin] Pass -mlinker-version=133 to linker invocation in odr-lto.cpp
2022-10-19 yeting.kuo@sifive.com [VP] Teach isVPBinaryOp to recognize vp.smin/smax/umin/umax/minnum/maxnum.
2022-10-19 preames@rivosinc.com [clang][RISCV] Set vscale_range attribute based on VLEN
2022-10-19 Jam) Marukawa [VE] Change the way to lower selectcc
2022-10-19 sivachandra@google.com [libc][Obvious] Add termios.h to the list of x86_64 linux headers.
2022-10-19 craig.topper@sifive.com [RISCV] Remove -enable-unsafe-fp-math from machine combiner tests. NFC
2022-10-19 jonas@devlieghere.com [clang] Disable assertion that can "easily happen"
2022-10-19 lhames@gmail.com [examples][ORC] Make sure eh-frame registration code is linked into an example.
2022-10-19 efriedma@quicinc.com [Sema] Don't treat a non-null template argument as if it were null.
2022-10-19 kparzysz@quicinc.com [Hexagon] Fix insertion point for pointer difference calculation
2022-10-19 2998727+wrengr@users.noreply.github.com [mlir][sparse] Fix breakage on older versions of cmake
2022-10-19 augusto2112@me.com [lldb] Allow SymbolFileDWARFDebugMap to register multiple compile units
2022-10-19 mtrofin@google.com [mlgo] Fix one test post-D135934
2022-10-19 thomasraoux@google.com [mlir][linalg] Add back split reduction tests dropped by previous commit
2022-10-19 tejohnson@google.com [BitcodeReader] Convert pair to triple in preparation for MemProf (NFC)
2022-10-19 michal.paszkowski@outlook.com [SPIR-V] Add get_image_num_mip_levels implementation
2022-10-19 michal.paszkowski@outlook.com [SPIR-V] Add atomic_init and fix atomic explicit lowering
2022-10-19 jgorbe@google.com [lldb] Add matching based on Python callbacks for data formatters.
2022-10-19 a.bataev@outlook.com [SLP][NFC]Remove unused variable, NFC.
2022-10-19 Jolanta.Jensen@arm.com [NFC][CostModel] Added floating point frem test for SVE
2022-10-19 ajcbik@google.com [mlir][sparse] end-to-end sparse vector insertion codegen
2022-10-19 trass3r@gmail.com [clang][modules] Add time traces for AST serialization
2022-10-19 craig.topper@sifive.com [RISCV] Add more check prefixes to extractelt-fp.ll to fix a conflicting case.
2022-10-19 rafaelauler@fb.com [BOLT] Ignore duplicate global symbols

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: If62d31c318edd942d3a674d937e09c157da09bcc
Reviewed-on: https://chromium-review.googlesource.com/c/emscripten-releases/+/3967333
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: 4662fbf9995ce1849638fbd490973c7dadef92ab
  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.