Roll llvm-project from 463a4f15044c to 0e3476605f06 (22 revisions)

https://chromium.googlesource.com/external/github.com/llvm/llvm-project.git/+log/463a4f15044c..0e3476605f06

2024-10-01 vyacheslav.levytskyy@intel.com [SPIR-V] Implement support of the SPV_EXT_arithmetic_fence SPIRV extension (#110500)
2024-10-01 vyacheslav.levytskyy@intel.com [SPIR-V] Discard some llvm intrinsics which we do not expect to actually represent code after lowering (#110233)
2024-10-01 vyacheslav.levytskyy@intel.com [SPIR-V] Implement OpSpecConstantOp with ptr-cast operation (#109979)
2024-10-01 vyacheslav.levytskyy@intel.com [SPIR-V] Fix inconsistency between previously deduced element type of a pointer and function's return type (#109660)
2024-10-01 fabian.ritter@amd.com [AMDGPU] Check vector sizes for physical register constraints in inline asm (#109955)
2024-10-01 martin@martin.st Revert "[clang] Fix FIXME in dynamic initializer emission, NFCI"
2024-10-01 jperier@nvidia.com [flang][NFC] simplify dispatching of reduction runtime calls (#110479)
2024-10-01 zyn7109@gmail.com [Clang][NFC] Add a test for CWG 2913 (#110614)
2024-10-01 hokein.wu@gmail.com Add a testcase for the -Wdangling-assignment-gsl warning, NFC.
2024-10-01 kazu@google.com [MCA] Avoid repeated hash lookups (NFC) (#110622)
2024-10-01 kazu@google.com [ProfileData] Avoid repeated hash lookups (NFC) (#110619)
2024-10-01 stephenchouca@users.noreply.github.com [LLVM][TableGen] Support type casts of nodes with multiple results (#109728)
2024-10-01 me@m-sp.org [mlir][GPU] gpu.printf: Do not emit duplicate format strings (#110504)
2024-10-01 me@m-sp.org [mlir][Transforms][NFC] Dialect Conversion: Simplify `finalize` signature (#110419)
2024-10-01 raul@tambre.ee [compiler-rt] Fix C and C++ compilers being switched when compiling tests (#110552)
2024-10-01 brandon.wu@sifive.com [RISCV][VCIX] Add vcix_state to GNU inline assembly register set (#106914)
2024-10-01 luke@igalia.com [RISCV] Update stack-folding.ll test
2024-10-01 craig.topper@sifive.com [RISCV][GISel] Remove unused isel patterns for s32 shifts with s64 shift amount.
2024-10-01 luke@igalia.com [RISCV] Fold vfmv.f.s of f16 into load from stack (#110214)
2024-10-01 dklimkin@google.com [bazel] Fix build past 00128a20eec27246719d73ba427bf821883b00b4 (#110629)
2024-10-01 i@maskray.me [X86] Don't convert local function foo in the same section to foo(%rip) when the offset is near INT32_MIN
2024-10-01 vitalybuka@google.com [libc++][string] Add regression test for sized new/delete bug (#110210)

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: I9aec22bb79dbbe4e5c7da19091ad55c7986ab63a
Reviewed-on: https://chromium-review.googlesource.com/c/emscripten-releases/+/5901304
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: a5e7b00f2b060493b2a35d7c0578e292d57fe6d0
  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.