commit | 6c85bdf2e3d076f4663361cba01ea59c7a3d0c71 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Fri Aug 04 13:41:55 2023 |
committer | Emscripten-releases LUCI CQ <emscripten-releases-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Aug 04 15:43:22 2023 |
tree | c2887cf59a80098a5698a4636b196464da0b4af9 | |
parent | 106eea526eed6936a1166b55c00dbd2c7ee84eb1 [diff] |
Roll llvm-project from 734da23e21eb to 28fef902fc9f (25 revisions) https://chromium.googlesource.com/external/github.com/llvm/llvm-project.git/+log/734da23e21eb..28fef902fc9f 2023-08-04 benjamin.maxwell@arm.com [mlir][VectorOps] Fix folding of vector.extract from stretch vector.broadcast 2023-08-04 zinenko@google.com Revert "[mlir][conversion] NFC - Relax convert-cf-to-llvm and finalize-memref-to-llvm to also work on non-builtin module ops" 2023-08-04 zinenko@google.com Revert "Foo" 2023-08-04 vyng@google.com [lld-macho] Fixed crashes when linking with incompatible-arch archives/ 2023-08-04 aaron@aaronballman.com Add my Discord, IRC, and Discourse handles 2023-08-04 aaron@aaronballman.com Reword the intro to the code owners file 2023-08-04 martin@martin.st [libcxx] Respect CMAKE_MSVC_RUNTIME_LIBRARY wrt whether to use the debug CRT 2023-08-04 martin@martin.st [libcxx] [test] Deduplicate setting parameters for clangcl test configs. NFC. 2023-08-04 a.bataev@outlook.com Revert "[SLP]Improve stores vectorization." 2023-08-04 flo@fhahn.com [LV] Split off code to optimize initial VPlan (NFC). 2023-08-04 pierre.vanhoutryve@amd.com [TableGen] Do not compile CombineRuleBuilder::verify in release builds 2023-08-04 david.green@arm.com [AArch64][GISel] Expand G_DUP and G_DUPLANE to v8s8 and v4s16 2023-08-04 vdzhidzhoev@accesssoftek.com [GlobalISel] Handle sequences of trunc(sext/zext/anyext...) in artifact combiner 2023-08-04 nicolasvasilache@users.noreply.github.com [mlir][transform] Expose vector patterns useful for cleaning up masked vectorization and add test to showcase composition 2023-08-04 nicolasvasilache@users.noreply.github.com Foo 2023-08-04 nicolasvasilache@users.noreply.github.com [mlir][conversion] NFC - Relax convert-cf-to-llvm and finalize-memref-to-llvm to also work on non-builtin module ops 2023-08-04 flo@fhahn.com [LV] Remove unnecessary std::move from tryToBuildVPlanWith.. (NFC). 2023-08-04 flo@fhahn.com [LV] Return null VPlanPtr instead of std::optional for tryToBuild (NFC) 2023-08-04 jryans@gmail.com [LLDB][CMake][NFC] Remove unused LLDB_LINKER_SUPPORTS_GROUPS variable 2023-08-04 david.spickett@linaro.org [LLVM][TableGen][Jupyter] Add first tutorial notebook 2023-08-04 david.spickett@linaro.org [llvm][TableGen][Jupyter] Add configurable default reset behaviour 2023-08-04 jay.foad@amd.com [AMDGPU] Fix typo in comment in test 2023-08-04 safonsof@amd.com [Flang][OpenMP] Improve support for `if` clause on combined constructs 2023-08-04 david.spickett@linaro.org Revert "[lldb][lldb-vscode] Skip disassembler test on Arm" 2023-08-04 kadircet@google.com [include-cleaner] Handle files with unnamed buffers 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: I6dae75a7743dde4b4aca1c95fe19d2126638e07e Reviewed-on: https://chromium-review.googlesource.com/c/emscripten-releases/+/4750918 Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
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
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.
src/
This directory was forked from the WebAssembly waterfall repo That repo was retired because it was only used by emscripten-releases.
depot_tools
. Follow the instructionspkg-config
if you don't have it installed already, e.g. # apt install pkg-config
python src/build.py
Build.py has 3 types of actions:
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:
$ src/build.py --no-sync --build-exclude=llvm
$ 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.