Google Git
Sign in
chromium / emscripten-releases / 4a75ef62830472db6d641abd24962bc32a389884
commit4a75ef62830472db6d641abd24962bc32a389884[log] [tgz]
authorchromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>Thu Apr 27 03:47:37 2023
committerEmscripten-releases LUCI CQ <emscripten-releases-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Apr 27 05:39:04 2023
treebf9193327a532c2f504d97bb10c654895dfc932b
parent5f155ab8a87510390130a1b664c53266aa2e1c5a [diff]
Roll llvm-project from 919382004f4e to 71cb689661ab (23 revisions)

https://chromium.googlesource.com/external/github.com/llvm/llvm-project.git/+log/919382004f4e..71cb689661ab

2023-04-27 i@maskray.me [LTO] Change getThinLTOOutputFile to take StringRef
2023-04-27 yeting.kuo@sifive.com [RISCV] Support vector strict rounding operations.
2023-04-27 luxufan@iscas.ac.cn [ValueTracking] Guaranteed not to be undef if has dereferenceable attribute
2023-04-27 vitalybuka@google.com [NFC][HWASAN] Move InTaggableRegion
2023-04-27 vitalybuka@google.com Revert "[SPARC][MC] Fix encoding of backwards BPr branches"
2023-04-27 vitalybuka@google.com [HWASAN] Support tagged stack pointer
2023-04-27 vitalybuka@google.com [hwasan] Implement __sanitizer_purge_allocator
2023-04-27 yingcong.wu@intel.com [libfuzzer] avoid unneccessary auto-copy
2023-04-27 yingcong.wu@intel.com [sanitizer] move a pointer dereference after its null check
2023-04-27 vitalybuka@google.com [HWASAN] Fix __sanitizer_get_allocated_{begin,size}
2023-04-27 dianqk@dianqk.net [GlobalOpt] Don't replace the aliasee if it has other references.
2023-04-27 vitalybuka@google.com [HWASAN] Fix HwasanReallocate in aliasing mode
2023-04-27 haohai.wen@intel.com Always emit symbol table when dwarf section exists in COFF
2023-04-27 hjl.tools@gmail.com [sanitizer] Correct alignment of x32 __sanitizer_siginfo
2023-04-27 Raghu.Maddhipatla@amd.com [OpenMP][Flang][Semantics] Add semantics support for USE_DEVICE_PTR clause on OMP TARGET DATA directive.
2023-04-27 walter@modular.com [lldb] Create a way to force remove commands
2023-04-27 gulfem@google.com [clang] Apply -fcoverage-prefix-map reverse order
2023-04-27 craig.topper@sifive.com [RISCV] Remove the uret instruction.
2023-04-27 chiahungduan@google.com [scudo] Fix missing pushing 1 block to BatchClassId
2023-04-27 jgorbe@google.com [bazel][NFC] Run buildifier on libc/libc_build_rules.bzl.
2023-04-26 vitalybuka@google.com [NFC][sanitizer] Fix typo
2023-04-26 vitalybuka@google.com [test][HWASAN] XFAIL broken test on aarch64
2023-04-26 richard@metafoo.co.uk Pass the found declaration to DiagnoseUseOfDecl.

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: I91f36361ad38657d947853751c0b875d9a08c197
Reviewed-on: https://chromium-review.googlesource.com/c/emscripten-releases/+/4482253
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: bf9193327a532c2f504d97bb10c654895dfc932b
  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.