Roll llvm-project from 08e5a1de8227 to 84aa02d3fa1f (14 revisions)

https://chromium.googlesource.com/external/github.com/llvm/llvm-project.git/+log/08e5a1de8227..84aa02d3fa1f

2024-08-23 macdue@dueutil.tech [memref] Handle edge case in subview of full static size fold (#105635)
2024-08-23 vitalybuka@google.com Revert "[SLP]Improve/fix subvectors in gather/buildvector nodes handling" (#105780)
2024-08-23 kazu@google.com [LTO] Turn ImportMapTy into a proper class (NFC) (#105748)
2024-08-23 pottagetom@gmail.com [clang-format] Change BinPackParameters to enum and add AlwaysOnePerLine (#101882)
2024-08-23 kazu@google.com [Scalar] Remove an unused variable (#105767)
2024-08-23 vitalybuka@google.com Reland "[Vectorize] Fix warnings"" (#105772)
2024-08-23 lhames@gmail.com [ORC] Add an identifier-override argument to loadRelocatableObject and friends.
2024-08-23 bertrand.wlodarczyk@intel.com [SPIRV] Emitting DebugSource, DebugCompileUnit (#97558)
2024-08-23 vitalybuka@google.com Revert "[Vectorize] Fix warnings" (#105771)
2024-08-23 owenpiano@gmail.com [clang-format] Don't insert a space between :: and * (#105043)
2024-08-23 carl.ritson@amd.com [AMDGPU] Refactor code for GETPC bundle updates in hazards (NFCI)
2024-08-23 rjoshi@nvidia.com [NFC][TableGen] Emit more readable builtin string table (#105445)
2024-08-23 yunfei.song@intel.com [mlir][tensor] Add consumer fusion for `tensor.pack` op. (#103715)
2024-08-23 keithbsmiley@gmail.com [bazel] Move lldb-dap cc_binary to lldb/BUILD.bazel (#105733)

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://issues.skia.org/issues/new?component=1389291&template=1850622

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Tbr: wasm-waterfall@grotations.appspotmail.com
Change-Id: I3e5d3448870e53bd0a261394e856e818b017485e
Reviewed-on: https://chromium-review.googlesource.com/c/emscripten-releases/+/5808023
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: 1635b5e7070c6c4eb7a4f98b2a05d65e71a8d8cf
  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 an 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.