Google Git
Sign in
chromium / emscripten-releases / 03f4995199b8158de9820c07d1e376389141611e
commit03f4995199b8158de9820c07d1e376389141611e[log] [tgz]
authorchromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>Wed Jun 14 00:14:51 2023
committerEmscripten-releases LUCI CQ <emscripten-releases-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jun 14 02:03:41 2023
tree41628cb9ec59d563adcbccdccd250e8e9ca48849
parent0ca1c298f69fb65969bac8dc345d61451270b54f [diff]
Roll emscripten from eae227d9cd99 to 325ae7cceefc (12 revisions)

https://chromium.googlesource.com/external/github.com/emscripten-core/emscripten.git/+log/eae227d9cd99..325ae7cceefc

2023-06-14 sbc@chromium.org Move #include's out of jsifier.js and into postamble.js. NFC (#19613)
2023-06-13 55058507+jameshu15869@users.noreply.github.com WasmFS JS API: Implement truncate (#19543)
2023-06-13 sbc@chromium.org Move `atob` (ascii-to-base64) polyfill into its own file. NFC (#19606)
2023-06-13 azakai@google.com Fix SDL1 deps (#19610)
2023-06-13 azakai@google.com Don't run FS.createLazyFile tests in WasmFS mode (#19609)
2023-06-13 azakai@google.com Fix browser.test_binaryen_async for WasmFS (#19607)
2023-06-13 55058507+jameshu15869@users.noreply.github.com WasmFS JS API: Implement llseek (#19601)
2023-06-13 sbc@chromium.org Cleanup proxyWorker.js and use arrow functions. NFC (#19604)
2023-06-13 55058507+jameshu15869@users.noreply.github.com WasmFS JS API: Clean up API Wrappers (#19605)
2023-06-13 sbc@chromium.org Use shorthand object notation where possible. NFC (#19594)
2023-06-13 sbc@chromium.org Cleanup python code in tools/js_optimizer.py. NFC (#19591)
2023-06-13 132437722+mboc-qt@users.noreply.github.com Handle wildcards in ASYNCIFY_EXPORTS when intrumenting exports (#19298)

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/emscripten-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: I3c5ce0e7252ec3803b155e764918ffebb8fb070b
Reviewed-on: https://chromium-review.googlesource.com/c/emscripten-releases/+/4612106
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: 41628cb9ec59d563adcbccdccd250e8e9ca48849
  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.