Roll llvm-project from 085845a2acbe to 4314f4ceb5c8 (45 revisions)

https://chromium.googlesource.com/external/github.com/llvm/llvm-project.git/+log/085845a2acbe..4314f4ceb5c8

2023-06-30 aaupov@fb.com Revert "[BOLT][Instrumentation] Put Allocator itslef in shared memory by default"
2023-06-30 vdonaldson@nvidia.com [flang] test update
2023-06-30 jason@molenda.com "fp" -> "flags" typeo in description of generic registers
2023-06-30 johannes@jdoerfert.de [OpenMPOpt][FIX] Internalization is an IR change too
2023-06-30 i@maskray.me [AArch64][MachO] Drop a 2015 ld64 workaround avoiding local relocations
2023-06-30 jason@molenda.com Recognize BSS-only DATA segments as sections that need to be slid
2023-06-30 vdonaldson@nvidia.com [flang] Test update
2023-06-30 Ting.Wang.SH@ibm.com [PowerPC][NFC] add SADDO/SSUBO test case
2023-06-30 Ting.Wang.SH@ibm.com [PowerPC][NFC] expose issue on absol-jump-table-enabled.ll (relocation-model=pic + ppc-use-absolute-jumptables)
2023-06-30 hankuan.chen@sifive.com [SLP] Provide an universal interface for FixedVectorType::get. NFC.
2023-06-30 jason@molenda.com Add 'target dump section-load-list' for lldb debugging
2023-06-29 vdonaldson@nvidia.com [flang] IEEE_ARITHMETIC intrinsic module procedures
2023-06-29 preames@rivosinc.com [RISCV] Rename a couple of binary vector td classes/multiclasses
2023-06-29 shafik.yaghmour@intel.com [Clang] Fix crash in isCXXDeclarationSpecifier when attempting to annotate template name
2023-06-29 iana@apple.com [libc++][Modules] Make module exports consistent with header includes
2023-06-29 yuanfang.chen@sony.com Adjust tests in 632dd6a4ca0036009f for ARM host
2023-06-29 Raghu.Maddhipatla@amd.com [Flang] [OpenMP] [Semantics] Change SIMD ALIGNED clause support from parsing a std::list<Name> to OmpObjectlist
2023-06-29 revunov.denis@huawei-partners.com [BOLT][Instrumentation] Add dumping function to instrumentation hash tables
2023-06-29 revunov.denis@huawei-partners.com [BOLT][Instrumentation] Disallow combining append-pid with sleep-time/wait-forks
2023-06-29 revunov.denis@huawei-partners.com [BOLT][Instrumentation] Put Allocator itslef in shared memory by default
2023-06-29 revunov.denis@huawei-partners.com [BOLT][Instrumentation] Don't share counters when using append-pid
2023-06-29 revunov.denis@huawei-partners.com [BOLT][Instrumentation] Add mmap return value assertions
2023-06-29 revunov.denis@huawei-partners.com [BOLT][Instrumentation][NFC] define and use mmap flags
2023-06-29 hokein.wu@gmail.com Fix -Wunused-variable in release build.
2023-06-29 brendon.cahoon@amd.com [AMDGPU] Reserve SGPR pair when long branches are present
2023-06-29 varconsteq@gmail.com [libc++] Remove the legacy debug mode.
2023-06-29 yuanfang.chen@sony.com [Clang] Implements CTAD for aggregates P1816R0 and P2082R1
2023-06-29 plassen@groq.com [mlir] Remove self-include from BytecodeOpInterface.h (NFC)
2023-06-29 ldionne.2@gmail.com [libc++] Stop using __builtin_assume in _LIBCPP_ASSERT
2023-06-29 jhuber6@vols.utk.edu [libc] Enable the 'div' routines on the GPU
2023-06-29 johannes@jdoerfert.de [Attributor][NFC] Introduce IRP helpers for Attr and Arg handling
2023-06-29 johannes@jdoerfert.de [Attributor] Remove now obsolete initialization code
2023-06-29 vdonaldson@nvidia.com [flang] Block containing an interface
2023-06-29 blangmuir@apple.com [clang][modules] Avoid serializing all diag mappings in non-deterministic order
2023-06-29 daniel.kiss@arm.com [lld][AArch64] Add BTI landing pad to PLT entries when the symbol is exported.
2023-06-29 llvmgnsyncbot@gmail.com [gn build] Port b4ff893877ff
2023-06-29 cferris@google.com [scudo] Use getMonotonicTimeFast for tryLock.
2023-06-29 crtrott@sandia.gov [libc++][mdspan] Implement layout_left
2023-06-29 i@maskray.me Revert D145226 "[mlir][Transforms][NFC] CSE: Add non-pass entry point"
2023-06-29 johannes@jdoerfert.de [Attributor][FIX] Check AA preconditions
2023-06-29 johannes@jdoerfert.de [Attributor][FIX] Ensure AAAssumptionInfo properly reports change
2023-06-29 johannes@jdoerfert.de [Attributor] Introduce helpers to judge AAs prior to creation
2023-06-29 harjohn@google.com [lldb-vscode] Adjusting CreateSource to detect compiler generated frames.
2023-06-29 me@antoniofrighetto.com [ConstraintElimination] Handle solving-only `ICMP_NE` predicates
2023-06-29 sam.mccall@gmail.com [dataflow] fix compile on gcc7

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: I8802241570be975647ce7c11e798b406fdb6bf22
Reviewed-on: https://chromium-review.googlesource.com/c/emscripten-releases/+/4658977
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
1 file changed
tree: 3d6570af993655e526075b3ddfdbf2bb551eecd3
  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.