Roll llvm-project from ee643b706be2 to c0f5015afb45 (35 revisions)

https://chromium.googlesource.com/external/github.com/llvm/llvm-project.git/+log/ee643b706be2..c0f5015afb45

2023-09-13 35819229+klausler@users.noreply.github.com [flang] Foil attempts to put automatic objects in COMMON (#66228)
2023-09-13 augusto2112@me.com [lldb] Accept optional module in Value::ResolveValue (#66286)
2023-09-13 haowei@google.com Reland "Update GoogleTest to v1.14.0 (#65823)"
2023-09-13 d@ilvokhin.com [libc++] Fix minor warnings in libcxx benchmarks
2023-09-13 35819229+klausler@users.noreply.github.com [flang] Fix crash under -fdebug-dump-all (#66224)
2023-09-13 nickdesaulniers@users.noreply.github.com [Docs][Github] explain how to rectify gh pr merge failure (#66223)
2023-09-13 jan_svoboda@apple.com [clang] NFCI: Use `FileEntryRef` in `SrcMgr::ContentCache`
2023-09-13 michaelrj@google.com [libc] simplify printf float writing
2023-09-13 goldstein.w.n@gmail.com [InstCombine] Rename some shadow variables; NFC
2023-09-13 goldstein.w.n@gmail.com [InstCombine] Transform `(icmp ult/uge (and X, Y), X)` -> `(icmp ne/eq (and X, Y), X)`
2023-09-13 goldstein.w.n@gmail.com [InstCombine] Add tests for transforming `(icmp pred (and X, Y), X)`; NFC
2023-09-13 aeubanks@google.com [NFC][lldb] Replace usage of deprecated llvm::makeArrayRef
2023-09-13 michaelrj@google.com [libc][docs] Printf behavior doc
2023-09-13 jan_svoboda@apple.com [clang] NFCI: Use `FileEntryRef` in `ModuleMap::InferredModuleAllowedBy`
2023-09-13 nickdesaulniers@users.noreply.github.com reland [InlineAsm] wrap ConstraintCode in enum class NFC (#66264)
2023-09-13 ldionne.2@gmail.com [libc++] Remove unused CMake option LIBCXX_DISABLE_MACRO_CONFLICT_WARNINGS (#66249)
2023-09-13 maryammo@ca.ibm.com [PowerPC] Optimize VPERM and fix code order for swapping vector operands on LE
2023-09-13 jakub@nod-labs.com [mlir][spirv][gpu] Clean up wmma to coop matrix NV conversion. NFC. (#66278)
2023-09-13 jhuber6@vols.utk.edu [libc][NFC][Docs] Update some GPU testing information
2023-09-13 rupprecht@google.com [polly][www] Remove unused VideoJS
2023-09-13 paul.robinson@sony.com Add label for third-party/unittests (#66276)
2023-09-13 terry.l.wilmarth@intel.com Fix /tmp approach, and add environment variable method as third fallback during library registration
2023-09-13 36770114+PeimingLiu@users.noreply.github.com [sparse] allow unpack op to return 0-ranked tensor type. (#66269)
2023-09-13 Jeffrey.Byrnes@amd.com [AMDGPU] Precommit test for i8 vector CopyToReg handling patch
2023-09-13 mail@justinbogner.com [Driver][HLSL] Improve diagnostics for invalid shader model and stage
2023-09-13 vitalybuka@google.com [asan][ubsan] Enable testing with internal symbolizer (#66257)
2023-09-13 71531609+michaelrj-google@users.noreply.github.com [libc] Move long double table option to new config  (#66151)
2023-09-13 ch.bessonova@gmail.com [llvm-nm] Fix heap-use-after-free while executing 'llvm-nm -n --export-symbols' (#65668)
2023-09-13 preames@rivosinc.com [DAG] Remove pointless peephole from refineUniformBase [nfc]
2023-09-13 vitalybuka@google.com [sanitizer] Fail __sanitizer_symbolize_demangle instead of returning input (#66006)
2023-09-13 ymand@users.noreply.github.com [clang][dataflow] Change `diagnoseFunction` to use `llvm::SmallVector` instead of `std::vector`. (#66014)
2023-09-13 35342157+jhuber6@users.noreply.github.com [libc] Implement 'qsort' and 'bsearch' on the GPU (#66230)
2023-09-13 stefan.graenitz@gmail.com [JITLink][AArch32] Revisit descriptions for Call and Jump24 relocation types (NFC)
2023-09-13 stefan.graenitz@gmail.com [JITLink][AArch32] Remove duplicate '0x' hex prefixes from formatv strings in error messages
2023-09-13 stefan.graenitz@gmail.com [JITLink][AArch32] Don't adjust Thumb bit in fixup code; it doesn't contribute to branch ranges

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: Id15d42d61167fcb089d98d4405abfa3302f77eb3
Reviewed-on: https://chromium-review.googlesource.com/c/emscripten-releases/+/4863413
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: bc2ff6a77ab0f3ea3eebfef54cf378c0d41f3fee
  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.