commit | 6158fa99a670c6d7e0ea3823c588bae6ee46abf8 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Wed Feb 22 21:04:54 2023 |
committer | Emscripten-releases LUCI CQ <emscripten-releases-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Feb 22 23:26:01 2023 |
tree | b079dd536ca6a3789f4c804d5105ba972276a2e1 | |
parent | d78fb18400812761f5036d16863a6fba11fc61c8 [diff] |
Roll llvm-project from c9f4df57caea to bbaa5685b2c3 (27 revisions) https://chromium.googlesource.com/external/github.com/llvm/llvm-project.git/+log/c9f4df57caea..bbaa5685b2c3 2023-02-22 nitin.raj@sifive.com [RISCV] Replaced !subst chain with !foldl 2023-02-22 peiming@google.com [mlir][sparse] unconditionally use IndexType for sparse_tensor.specifier 2023-02-22 markus.boeck02@gmail.com [mlir] Complety remove old `fold` API 2023-02-22 aaupov@fb.com [BOLT][NFC] Return struct from evaluateX86MemoryOperand 2023-02-22 cyndy_ishida@apple.com Reland "[TextAPI] Implement TBDv5 Writer" 2023-02-22 craig.topper@sifive.com [RISCV] Expand tab characters. NFC 2023-02-22 quinn@nod-labs.com [mlir][tensor] Fix transpose permutation in tensor.pack generalization pattern 2023-02-22 kstoimenov@google.com [LSAN] Make sure HWASAN tests are linked with lld 2023-02-22 cyndy_ishida@apple.com Revert "[TextAPI] Implement TBDv5 Writer" 2023-02-22 cyndy_ishida@apple.com [TextAPI] Implement TBDv5 Writer 2023-02-22 ayermolo@meta.com [LLDB] Enable 64 bit debug/type offset 2023-02-22 andrzej.warzynski@arm.com [mlir][linalg] Vectorize tensor.extract using contiguous loads 2023-02-22 jhuber6@vols.utk.edu [libc] Partially implement 'quick_exit' for the GPU 2023-02-22 vsapsai@apple.com [Serialization] Don't warn when a deserialized category is equivalent to an existing one. 2023-02-22 cmcinally@nvidia.com [DAGCombine] Fix an ICE in combineMinNumMaxNum(...) 2023-02-22 manolis.tsamis@vrull.eu [RISCV] XTHeadMemPair: Fix invalid mempair combine for types other than i32/i64 2023-02-22 rtenneti@google.com [libc] Implement ntohl and ntohs 2023-02-22 vitalybuka@google.com [clang-format] Fix format of my last patch 2023-02-22 nawrin.sultana@intel.com [OpenMP] Target memory allocator fallback to default when no device available 2023-02-22 preames@rivosinc.com [RISCV] Reorganize deinterleave lowering for reuse [nfc] 2023-02-22 aeubanks@google.com Revert "[IRMover] Remove UB implying parameter attributes when necessary" 2023-02-22 jhuber6@vols.utk.edu [libc] Fix amdgpu startup code flags 2023-02-22 phosek@google.com Revert "[CMake] Unify llvm_check_linker_flag and llvm_check_compiler_linker_flag" 2023-02-22 Konstantina.Mitropoulou@amd.com [AMDGPU] Improve the lowering of raw_buffer_load_{i8,i16} and struct_buffer_load_{i8,i16} intrinsics 2023-02-22 orlando.hyams@sony.com [Assignment Tracking] Only set module flag if pass modifies a function 2023-02-22 Joseph.Nash@amd.com [AMDGPU] Don't set src mods on permlane16 2023-02-22 orlando.hyams@sony.com [Assignment Tracking] Choose better passes for RemoveRedundantDbgInstrs call 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: I336186e6ec3811e0af2e1962d723934617f9543b Reviewed-on: https://chromium-review.googlesource.com/c/emscripten-releases/+/4283963 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.