Roll llvm-project from 58def623ca46 to ee3f8d4a595b (40 revisions)

https://chromium.googlesource.com/external/github.com/llvm/llvm-project.git/+log/58def623ca46..ee3f8d4a595b

2023-01-12 i@maskray.me [CodeGen] Remove #include "llvm/ADT/None.h"
2023-01-12 thakis@chromium.org [gn] port c268f850a299
2023-01-12 wanglei@loongson.cn [LoongArch] Implement mayBeEmittedAsTailCall for tail call optimization
2023-01-12 i@tianshilei.me [OpenMP] Implement `omp_get_mapped_ptr`
2023-01-12 craig.topper@sifive.com [RISCV] Move FP store of extractelt pattern to DAGCombine.
2023-01-12 craig.topper@sifive.com [RISCV] Use ISD::EXTRACT_VECTOR_ELT for Intrinsic::riscv_vfmv_f_s lowering.
2023-01-12 nikolasklauser@berlin.de [libc++] Fix ranges::uninitialized_move{, _n} for move-only types
2023-01-12 vitalybuka@google.com [tsan] Remove rtl-old
2023-01-12 nikolasklauser@berlin.de [libc++][NFC] Fix endif comments in cmath
2023-01-12 zhongyunde@huawei.com [MergeICmps] Adapt to non-eq comparisons
2023-01-12 varconst@apple.com [libc++][ranges] Fix incorrect integer type in `view_interface` tests.
2023-01-12 vvereschaka@accesssoftek.com Fixed Clang::Driver 'netbsd.c' test on Windows/Cross builders. NFC.
2023-01-12 i@maskray.me [bazel] Enable layering_check for llvm and clang
2023-01-12 i@maskray.me [bazel] Fix all remaining --features=layering_check issues for @llvm-project//clang:all
2023-01-12 fmayer@google.com [NFC] fix more type conversion issues
2023-01-12 i@maskray.me [bazel] Fix all remaining --features=layering_check issues for @llvm-project//llvm:all
2023-01-12 fmayer@google.com [NFC] fix type conversion issue
2023-01-12 fmayer@google.com Dynamically allocate scudo allocation buffer.
2023-01-12 rafaelauler@fb.com [BOLT] Add test case triggering JT assertion
2023-01-12 williamjhuang@google.com Fix to D139603(reverted) - moved size check to unit test so that it is cross-platform
2023-01-12 bixia@google.com [mlir][sparse] Avoid values buffer reallocation for annotated all dense tensors.
2023-01-12 craig.topper@sifive.com [RISCV] Make sure we use LMUL=1 for scalar reduction input in combineBinOpToReduce
2023-01-12 bixia@google.com [mlir][sparse] Refactor the code that reshapes the values buffer for annotated all dense tensors.
2023-01-11 samitolvanen@google.com [ModuleUtils][KCFI] Set patchable-function-prefix for synthesized functions
2023-01-11 abrachet@google.com [GWP-ASan] Fix 6413872
2023-01-11 Sam) Liu [HIP] Use .hipi as preprocessor output extension
2023-01-11 i@maskray.me [llvm-lto2] Remove unused include after D123126
2023-01-11 i@maskray.me [bazel] Fix some --features=layering_check issues
2023-01-11 francisvm@yahoo.com [Matrix] Optimize matrix transposes around additions
2023-01-11 i@maskray.me [llvm-profdata] Remove an unused include after D115915
2023-01-11 abrachet@google.com [GWP-ASan] Fix test to work with Fuchsia's zxtest
2023-01-11 ayermolo@fb.com [llvm][dwwarf] Change CU/TU index to 64-bit
2023-01-11 samitolvanen@google.com [GCOV] Set !kcfi_type metadata for indirectly called functions
2023-01-11 ayermolo@fb.com Revert "[llvm][dwwarf] Change CU/TU index to 64-bit"
2023-01-11 spupyrev@fb.com [BOLT] using jump weights in profi
2023-01-11 Stanislav.Mekhanoshin@amd.com [AMDGPU] Mark wmma intrinsics as source of divergence
2023-01-11 jezng@fb.com [lld-macho][nfc] Use alignToPowerOf2 instead of alignTo when possible
2023-01-11 arthur.j.odwyer@gmail.com [libc++] Hold mutex lock while notify_all is called at notify_all_at_thread_exit
2023-01-11 paulkirth@google.com "Reland "[pgo] Avoid introducing relocations by using private alias"
2023-01-11 hanchung@google.com [mlir][tensor] Add patterns that fold ops into pack and unpack ops.

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: I1dbd7cb4bfc2da901d8f78b5cc0ad0005891e18d
Reviewed-on: https://chromium-review.googlesource.com/c/emscripten-releases/+/4160095
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: 692c2cdc57f90962c417557f673547a676820248
  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.