Roll llvm-project from 9a9827dc1185 to 389bf5d870b3 (11 revisions) https://chromium.googlesource.com/external/github.com/llvm/llvm-project.git/+log/9a9827dc1185..389bf5d870b3 2023-03-27 agrossman154@yahoo.com [llvm-exegesis] Refactor InstructionBenchmark to Benchmark 2023-03-27 tomasz.kamiński@sonarsource.com [clang] Test for AST Dumping of the template variables 2023-03-27 juamarti@amd.com [AMDGPU][printf] Run AMDGPUPrintfRuntimeBindingPass in -O0 2023-03-27 pierre.vanhoutryve@amd.com [clang] Remove legacy -m(no)-code-object-v3 options 2023-03-27 sam.mccall@gmail.com [dataflow] Delete legacy aliases 2023-03-27 me@m-sp.org [mlir][bufferize] Fix tracking of erased ops 2023-03-27 kazu@google.com [Target] Use isNullConstant (NFC) 2023-03-27 yeting.kuo@sifive.com [RISCV] Support vector type strict_fsqrt. 2023-03-27 kazu@google.com [Target] Use isAllOnesConstant (NFC) 2023-03-27 sgokhale@nvidia.com [AArch64][CodeGen] Add few more tests for fused operations (NFC) 2023-03-27 lhames@gmail.com [LLJIT] Allow multiple loadPlatformDynamicLibrary calls with the same path. 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: Id4e05a5bb47239506978099124cc93020cda6704 Reviewed-on: https://chromium-review.googlesource.com/c/emscripten-releases/+/4372232 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 pullgclient syncUpdate a DEPS entry:
cd emscripten-releasesgit checkout -b <branch>roll-dep emscripten-releases/llvm-projectgit cl uploadThe 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-configpython src/build.pyBuild.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-asmThe 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.