Roll llvm-project from 4314f4ceb5c8 to 7a101798b753 (30 revisions)

https://chromium.googlesource.com/external/github.com/llvm/llvm-project.git/+log/4314f4ceb5c8..7a101798b753

2023-06-30 sameer.sahasrabuddhe@amd.com Revert "[AMDGPU] Mark mbcnt as convergent"
2023-06-30 its.overmighty@gmail.com [AArch64] Add patterns for scalar FMUL, FMULX
2023-06-30 jperier@nvidia.com [flang][hlfir] Codegen of hlfir.region_assign where LHS conflicts
2023-06-30 hokein.wu@gmail.com [Support] Don't set "all_exe" mode by default for file written by llvm::writeToOutput
2023-06-30 freddy.ye@intel.com [NFC][X86] Add missing CPUID related changes for AMX-COMPLEX.
2023-06-30 ajcbik@google.com [mlir][affinexpr] add parseAffineExpr to parser API
2023-06-30 yedeng.yd@linux.alibaba.com [Coroutines] Don't transform cmpinst prematurely in simplifyTerminatorLeadingToRet
2023-06-30 hankuan.chen@sifive.com Reland [SLP] Provide an universal interface for FixedVectorType::get. NFC.
2023-06-30 freddy.ye@intel.com [NFC][X86] Correct tests with wrong locations before.
2023-06-30 johannes@jdoerfert.de [Attributor][NFCI] Remove the (already "unused") ModuleSlice
2023-06-30 johannes@jdoerfert.de [Attributor][NFCI] Avoid creating unnecessary AAs
2023-06-30 gkistanova@gmail.com lit::max-failures.py is flaky and hangs randomly on multi-core systems.
2023-06-30 aaupov@fb.com [BOLT][NFC] Simplify postProcessJumpTables
2023-06-30 carlos.alberto.enciso@gmail.com [loop-deletion] Overly defensive with undef-ing dbg.values.
2023-06-30 freddy.ye@intel.com [x86] Add missing FeatureCMOV in frontend targets.
2023-06-30 amir.aupov@gmail.com Revert "[BOLT][Instrumentation][NFC] define and use mmap flags"
2023-06-30 amir.aupov@gmail.com Revert "[BOLT][Instrumentation] Add mmap return value assertions"
2023-06-30 ajcbik@google.com [NFC] cleanup of parser
2023-06-30 aeubanks@google.com Revert "[SLP] Provide an universal interface for FixedVectorType::get. NFC."
2023-06-30 ian@iandouglasscott.com [M68k][MC] Add support for 32 bit register-register multiply/divide
2023-06-30 aeubanks@google.com [gn build] Port b5270ba20dc3
2023-06-30 aeubanks@google.com [gn build] Port 853b2a84cb99
2023-06-30 aeubanks@google.com Revert "[MC,x86-32] Remove a gold<2.34 workaround"
2023-06-30 craig.topper@sifive.com [RISCV] Mark zvkn* and zvks* extensions as enabled when all their subextensions are.
2023-06-30 2283975856@qq.com [CSKY] Optimize subtraction with SUBI32/SUBI16
2023-06-30 vdonaldson@nvidia.com [flang] Reinstate class query test
2023-06-30 wanglei@loongson.cn [LoongArch] Reuse LoongArchRegWithSubRegs class to shorten some code in LoongArchRegisterInfo.td. NFC
2023-06-30 wangpengcheng.pp@bytedance.com [RISCV][NFC] Replace Join with !interleave
2023-06-30 wangpengcheng.pp@bytedance.com [RISCV][NFC] Format TableGen files and remove unused defs
2023-06-30 aaupov@fb.com Revert "[BOLT][Instrumentation] Don't share counters when using append-pid"

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: Id566f89fc3e7af5affd6ddbf69d7e1bd84b4977a
Reviewed-on: https://chromium-review.googlesource.com/c/emscripten-releases/+/4658602
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: 6c5a88172103a7ae4dd432c072172762a45e8072
  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.