Roll llvm-project from afaa56df7a93 to 1d6430b9e2b8 (23 revisions)

https://chromium.googlesource.com/external/github.com/llvm/llvm-project.git/+log/afaa56df7a93..1d6430b9e2b8

2022-05-04 craig.topper@sifive.com [RISCV] Update isLegalAddressingMode for RVV.
2022-05-04 craig.topper@sifive.com [RISCV] Make use of SHXADD instructions in RVV spill/reload code.
2022-05-04 craig.topper@sifive.com [RISCV] Don't lookup TII in RISCVInstrInfo::getVLENFactoredAmount. NFCI
2022-05-04 aaupov@fb.com [BOLT] Fix ICPJumpTablesTopN option use
2022-05-04 aaupov@fb.com [BOLT][NFC] Make ICP options naming uniform
2022-05-04 aaupov@fb.com [BOLT][NFC] ICP: simplify findTargetsIndex
2022-05-04 aaupov@fb.com [BOLT][NFC] Refactor ICP::findCallTargetSymbols
2022-05-04 aaupov@fb.com [BOLT][CMAKE] Fix llvm-bolt-fuzzer build
2022-05-04 rtrieu@google.com [riscv] Mark function as used to avoid unused warning.
2022-05-04 hoy@fb.com [CSSPGO] Relax size limitation for priority inlining with preinlined profile
2022-05-04 hoy@fb.com [CSSPGO][NFC] Replace SampleProfileLoader::ProfileIsCS with FunctionSamples::ProfileIsCS.
2022-05-04 alexborcan@fb.com [lld] Implement safe icf for MachO
2022-05-04 jhuber6@vols.utk.edu [OpenMP] Fix save-temps name in linker wrapper
2022-05-04 preames@rivosinc.com [riscv] Add vsetvli tests involving moves to/from scalar regs
2022-05-03 preames@rivosinc.com [riscv] Add a couple more vsetvli tests
2022-05-03 rtrieu@google.com [psuedo] Fix for unused warning by moving code into debug macro.
2022-05-03 rtrieu@google.com [trace][intelpt] Fix out-of-bounds access.
2022-05-03 Matthew.Arsenault@amd.com ARM: Fix using undefined virtual registers in test
2022-05-03 Matthew.Arsenault@amd.com ARM: Cleanup MIR test
2022-05-03 Matthew.Arsenault@amd.com AMDGPU: Remove some invalid kill flags in tests
2022-05-03 Matthew.Arsenault@amd.com AMDGPU: Regenerate test checks
2022-05-03 Matthew.Arsenault@amd.com llvm-reduce: Reduce includes
2022-05-03 aaupov@fb.com [BOLT][TEST] Fix test failures on AArch64 builder

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: I5d960a2615f227064b87393e5c83efa91e144380
Reviewed-on: https://chromium-review.googlesource.com/c/emscripten-releases/+/3626364
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: 1aff5301a29c4544731938e2712016d989819841
  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](https://dev.chromium.org/developers/how-tos/depottools 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.