Google Git
Sign in
chromium / emscripten-releases / a0f8358719d4b1ccbdb8ce9d42c3ced79a4cbd9d
commita0f8358719d4b1ccbdb8ce9d42c3ced79a4cbd9d[log] [tgz]
authorchromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>Sat Feb 08 17:47:05 2025
committerEmscripten-releases LUCI CQ <emscripten-releases-scoped@luci-project-accounts.iam.gserviceaccount.com>Sat Feb 08 19:53:22 2025
tree494cf61129d4765978d66eeda5b734d502b10a71
parent822acaf2d6735eed3be9f6194d0dac77b03764b6 [diff]
Roll llvm-project from 6ff8a06de9ce to 7f2f90536155 (8 revisions)

https://chromium.googlesource.com/external/github.com/llvm/llvm-project.git/+log/6ff8a06de9ce..7f2f90536155

2025-02-08 vporpodas@google.com [SandboxVec] Fix: Add missing lit.local.cfg for target test
2025-02-08 llvm-project@meinersbur.de [Flang] Rename libFortranRuntime.a to libflang_rt.runtime.a (#122341)
2025-02-08 llvmgnsyncbot@gmail.com [gn build] Port 69b8cf4f0621
2025-02-08 vporpodas@google.com [SandboxVec][BottomUpVec] Add cost estimation and tr-accept-or-revert pass (#126325)
2025-02-08 durgadossr@nvidia.com [MLIR][NVVM] Add tcgen05 wait/fence Ops (#126265)
2025-02-08 quic_aelliott@quicinc.com [RISCV][NFC] Adopt DiagnosticString interface (#126290)
2025-02-08 mats@jun.codes [CodeGen][Hexagon] Replace PointerType::getUnqual(Type) with opaque version (NFC) (#126274)
2025-02-08 mats@jun.codes [CodeGen] Replace of PointerType::get(Type) with opaque version (NFC) (#124771)

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://issues.skia.org/issues/new?component=1389291&template=1850622

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Tbr: wasm-waterfall@grotations.appspotmail.com
Change-Id: Id643b679f33f6e5a9e96175ab9272c2c70a12d20
Reviewed-on: https://chromium-review.googlesource.com/c/emscripten-releases/+/6246061
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: 494cf61129d4765978d66eeda5b734d502b10a71
  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 an 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.