Roll llvm-project from 429d3d4e9d8d to 2c82080f0964 (22 revisions)

https://chromium.googlesource.com/external/github.com/llvm/llvm-project.git/+log/429d3d4e9d8d..2c82080f0964

2022-10-20 craig.topper@sifive.com [MachineFrameInfo][RISCV] Call ensureStackAlignment for objects created with scalable vector stack id.
2022-10-20 peiming@google.com [mlir][sparse] attach bufferizableOpInterface to InsertOp
2022-10-20 sujin.park@gatech.edu [lldb][trace] Correctly treat kernel CPUs as individual threads
2022-10-20 python3kgae@outlook.com [NFC] [DirectX backend] move ResourceClass into llvm.
2022-10-20 michaelfrancis@ibm.com [clang][AIX] Fix mcount name and call arguments
2022-10-20 bixia@google.com [mlir][sparse] Fix the codegen for the convert operator to handle hidden nop convert.
2022-10-20 qiongsiwu@gmail.com [clang][AIX] Omitting Explicit Debugger Tuning Option
2022-10-20 morbo@google.com [clang][Sema] Use correct array size for diagnostic
2022-10-20 caroline.concatto@arm.com Revert "[AArch64]SME2 Multi-single vector SVE Destructive 2 and 4 Registers"
2022-10-20 caroline.concatto@arm.com Revert "[AArch64]SME2 Multi-vector - Index/Single/Multi Array Vectors FMA sources"
2022-10-20 llvm-project@meinersbur.de [Polly] Ensure -polly-detect-keep-going still eventually rejects invalid regions.
2022-10-20 caroline.concatto@arm.com [AArch64]SME2 Multi-vector - Index/Single/Multi Array Vectors FMA sources
2022-10-20 peiming@google.com [mlir][sparse] add source materizalization callback for sparse tensor codegen type converter.
2022-10-20 caroline.concatto@arm.com [AArch64]SME2 Multi-single vector SVE Destructive 2 and 4 Registers
2022-10-20 riddleriver@gmail.com [tblgen-lsp-server] Fix various ASAN issues
2022-10-20 efriedma@quicinc.com [AArch64] Fix scheduler crash in fusion code.
2022-10-20 caroline.concatto@arm.com [AArch64]SME2 Multiple vector ternary int/float 2 and 4 registers
2022-10-20 williamjhuang@google.com [InstCombine] Canonicalize GEP of GEP by swapping constant-indexed GEP to the back
2022-10-20 ravishankarm@google.com [mlir] Set pattern that resolves tensor dimensions as having bounded recursion.
2022-10-20 zhongyunde@huawei.com [AArch64][SelectionDAG] Lower multiplication by a constant to shl+add+shl+add
2022-10-20 python3kgae@outlook.com [HLSL] Add groupshare address space.
2022-10-20 jhuber6@vols.utk.edu [OpenMP] Remove `-Bsymbolic` flag for device linking in the GNU toolchain

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: I58dc40c640f9e989a89784cedf5624ca7880276b
Reviewed-on: https://chromium-review.googlesource.com/c/emscripten-releases/+/3969360
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: 6425a702cd13b5bba1b356310fcbbbae34972f54
  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.