Roll llvm-project from 310ee08d5d45 to c2114bd8e1f0 (20 revisions)

https://chromium.googlesource.com/external/github.com/llvm/llvm-project.git/+log/310ee08d5d45..c2114bd8e1f0

2023-04-18 v.churavy@gmail.com Revert "Non-debuginfo JITLink perf jitdump support"
2023-04-18 nathan@acm.org [ELF] hash fn return type
2023-04-18 nathan@acm.org [BOLT] Don't enable runtime when not building X86
2023-04-18 goldstein.w.n@gmail.com Recommit "[ValueTracking] Apply the isKnownNonZero techniques in `ashr`/`lshl` to `shl` and vice-versa" (2nd Try)
2023-04-18 goldstein.w.n@gmail.com Recommit "[InstCombine] Add transforms for `(icmp {u|s}ge/le (xor X, Y), X)`" (2nd Try)
2023-04-18 goldstein.w.n@gmail.com [InstCombine] Fix buggy `(mul X, Y)` -> `(shl X, Log2(Y))` transform PR62175
2023-04-18 lhames@gmail.com [ExecutionEngine] Allow JIT tests to run on PowerPC.
2023-04-18 i@maskray.me [AsmPrinter] Fix placement of function entry comments
2023-04-18 caslyn@google.com [gwp_asan] Employ EXPECT_DEATH for zxtest compatibility
2023-04-18 rahmanl@google.com Refactor BasicBlockSectionsProfileReader::getBBClusterInfoForFunction.
2023-04-18 llvmgnsyncbot@gmail.com [gn build] Port 76e1521b0acf
2023-04-18 prem.chintalapudi@gmail.com Non-debuginfo JITLink perf jitdump support
2023-04-18 antiagainst@google.com [mlir][spirv][vector] Enable vector3 when converting to dot product
2023-04-18 morbo@google.com [Clang][NFC] Rename methods/vars to reflect their real usage
2023-04-18 jason@molenda.com Remove hardcoded address bits in ABIMacOS_arm64
2023-04-18 vitalybuka@google.com [NFC][lsan] Rename test function
2023-04-18 vitalybuka@google.com [lsan] Disabled D148281 test on Darwin
2023-04-18 sivachandra@google.com [libc] Add two more recipes to do a cross build.
2023-04-18 a.bataev@outlook.com [SLP]Add final resize to ShuffleCostEstimator::finalize member function and basic add member functions.
2023-04-18 sivachandra@google.com [libc][NFC] Move RoundingModeUtils to LibcFPTestHelpers.

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 dschuff@google.com,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: Ic2182503cd80dc3aa2ed911a9738f73416e5d038
Reviewed-on: https://chromium-review.googlesource.com/c/emscripten-releases/+/4444387
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: 659a954ec761a1bde95c44835fd68528b0d8caea
  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.