Roll llvm-project from 1403080a1f23 to 872276de4b8c (40 revisions)

https://chromium.googlesource.com/external/github.com/llvm/llvm-project.git/+log/1403080a1f23..872276de4b8c

2023-07-05 deadalnix@gmail.com [NFC] Autogenerate CodeGen/SystemZ/int-{uadd,sub}-0*.ll
2023-07-05 preames@rivosinc.com [RISCV] Remove legacy TA/TU pseudo distinction for load instructions
2023-07-05 aaron@aaronballman.com Remove unused test file
2023-07-05 nicolasvasilache@users.noreply.github.com [mlir][Linalg] Relax restriction of Linalg passes on FuncOp
2023-07-05 jason@molenda.com Revert "Change the dyld notification function that lldb puts a breakpoint in"
2023-07-05 michaeltmaitland@gmail.com [llvm-mca][RISCV] Fix typo in test for vsetvli instruction
2023-07-05 Matthew.Arsenault@amd.com AMDGPU: Correctly lower llvm.log.f32 and llvm.log10.f32
2023-07-05 jhuber6@vols.utk.edu [libc] Support timing information in libc tests
2023-07-05 mital@mitalashok.co.uk Fix aggregate CTAD with string literals adding extra const
2023-07-05 flo@fhahn.com [LV] Update generateInstruction to return produced value (NFC).
2023-07-05 luke@igalia.com [RISCV] Fix interleave/deinterleave store test output
2023-07-05 szakharin@nvidia.com [flang][hlfir] Lower actual TARGET for dummy POINTER.
2023-07-05 rengolin@systemcall.eu [MLIR][Linalg] Add more arith named ops to linalg
2023-07-05 jonas@devlieghere.com [lldb] Fix incorrect uses of formatv specifiers in LLDB_LOG
2023-07-05 jonas@devlieghere.com [lldb] Fix incorrect uses of LLDB_LOG_ERROR
2023-07-05 krishnanarayanan132002@gmail.com [clang-repl] Improve the clang-repl documentation.
2023-07-05 luke@igalia.com [RISCV] Lower deinterleave2 intrinsics to vlseg2
2023-07-05 luke@igalia.com [RISCV] Add tests for vector.deinterleave2s of loads
2023-07-05 luke@igalia.com [RISCV] Lower interleave2 intrinsics to vsseg2
2023-07-05 luke@igalia.com [RISCV] Add tests for stores of vector.interleave2
2023-07-05 michaelrj@google.com [libc] fix MPFR rounding problems in fuzz test
2023-07-05 phosek@google.com [libc] Use the new style includes
2023-07-05 dave.pagan@amd.com [OpenMP][CodeGen] Add codegen for combined 'loop' directives.
2023-07-05 jyknight@google.com [libcxx] Migrate posix_compat.h layer to not use CRT filesystem functions.
2023-07-05 yusra.syeda@ibm.com [SystemZ][z/OS] z/OS ADA codegen and emission
2023-07-05 phosek@google.com Revert "[libc] Use LIBC_INCLUDE_DIR in CMake rules"
2023-07-05 phosek@google.com [libc] Use LIBC_INCLUDE_DIR in CMake rules
2023-07-05 flo@fhahn.com [SCEV] Add flag to control invertible check for normalization.
2023-07-05 hnrklssn@gmail.com [UTC] Adapt version matcher to glob CLANG_VENDOR
2023-07-05 phosek@google.com [libc] Check if the hermetic test target exists
2023-07-05 nawrin.sultana@intel.com [OpenMP] Minor improvement in error msg and fixes few coverity reported issues
2023-07-05 igor.kirillov@arm.com [CodeGen] Add support for Splats in ComplexDeinterleaving pass
2023-07-05 aeubanks@google.com [CMake] Add /winsysroot to lld-link when LLVM_WINSYSROOT is specified
2023-07-05 john.brawn@arm.com Fix compile error in UnresolvedSetTest.cpp, again
2023-07-05 iana@apple.com [libc++][Modules] Remove explicit exports from modules that `export *`
2023-07-05 iana@apple.com [libc++][Modules] Add missing submodules
2023-07-05 deadalnix@gmail.com [NFC] Fix indentation in addcarry.ll
2023-07-05 john.brawn@arm.com Fix compile error in UnresolvedSetTest.cpp with -Wall
2023-07-05 luke@igalia.com [RISCV] Add VFCVT pseudos with no mask
2023-07-05 koraq@xs4all.nl [libc++][format] Implements formatting pointer.

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: I666f493d41862123483d8c3a85dc4be87f0c85fb
Reviewed-on: https://chromium-review.googlesource.com/c/emscripten-releases/+/4666512
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: 15dd8a1163da760f95edb1ff0bc664fabfbfd98d
  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.