SuccessChanges

Summary

  1. [SimplifyCFG] Precommit test for preserving !annotation. (details)
  2. [lldb][NFC] Apply performance-faster-string-find (`str.find("X")` -> `str.find('x')`) (details)
  3. [flang] Handle undeclared names in EQUIVALENCE statements (details)
  4. [mlir] AsyncRuntime: mode runtime declarations to mlir::runtime namespace (details)
  5. [mlir] Async: re-enable tests after fixing fkakines (details)
Commit 70bd75426e5c06b36ab19c3650ed6bc157f8ce13 by flo
[SimplifyCFG] Precommit test for preserving !annotation.
The file was addedllvm/test/Transforms/SimplifyCFG/annotations.ll
Commit 869f8363c424592e5f8c258492f46d5fcbc90c83 by rupprecht
[lldb][NFC] Apply performance-faster-string-find (`str.find("X")` -> `str.find('x')`)
The file was modifiedlldb/tools/lldb-vscode/JSONUtils.cpp
The file was modifiedlldb/source/Plugins/InstrumentationRuntime/MainThreadChecker/InstrumentationRuntimeMainThreadChecker.cpp
Commit 4e90cad6a6b5504f11b7876e26e80c2a079e04b0 by psteinfeld
[flang] Handle undeclared names in EQUIVALENCE statements

Names in EQUIVALENCE statements are only allowed to indicate local
objects as per 19.5.1.4, paragraph 2, item (10).  Thus, a name appearing
in an EQUIVALENCE statement with no corresponding declaration in the
same scope is an implicit declaration of the name.  If that scope
contains an IMPLICIT NONE, it's an error.

I implemented this by adding a state variable to ScopeHandler to
indicate if we're resolving the names in an EQUIVALENCE statement and
then checked this state when resolving names.  I also added a test to
the existing tests for EQUIVALENCE statements.

Differential Revision: https://reviews.llvm.org/D93345
The file was modifiedflang/lib/Semantics/resolve-names.cpp
The file was modifiedflang/test/Semantics/equivalence01.f90
Commit 11f1027b4d8d851c94497330bb901bd5753188f3 by ezhulenev
[mlir] AsyncRuntime: mode runtime declarations to mlir::runtime namespace

Define Async runtime related typedefs in the `mlir::runtime` namespace.

Reviewed By: mehdi_amini

Differential Revision: https://reviews.llvm.org/D93391
The file was modifiedmlir/include/mlir/ExecutionEngine/AsyncRuntime.h
The file was modifiedmlir/lib/ExecutionEngine/AsyncRuntime.cpp
Commit 900d71a851db5d50a52906c0146451b4b71cd85f by ezhulenev
[mlir] Async: re-enable tests after fixing fkakines

Test flakiness was fixed by: https://github.com/llvm/llvm-project/commit/9edcedf7f222ce7c893d1e3bf19b3a7a1f0f2218

Runs these tests to verify that all parts of the lowering work correctly.

Reviewed By: mehdi_amini

Differential Revision: https://reviews.llvm.org/D93384
The file was modifiedmlir/test/mlir-cpu-runner/async.mlir
The file was modifiedmlir/test/mlir-cpu-runner/async-group.mlir

Summary

  1. [jenkins] Fix typo in the host-compiler path used by lldb-cmake-matrix (details)
  2. Start Docker-izing sanitizer-windows (details)
Commit 264d1a72fcc7ce2c996790877a22d715821c034f by Jonas Devlieghere
[jenkins] Fix typo in the host-compiler path used by lldb-cmake-matrix
The file was modifiedzorg/jenkins/jobs/jobs/lldb-cmake-matrix
Commit ccffa7a21c8d6d2f32373add1aa368ff23b3a188 by rnk
Start Docker-izing sanitizer-windows

This defines a new docker image for sanitizer-windows based on the
existing docker image. I chose to dockerize sanitizer-windows first,
because it cycles quickly and doesn't do a two-stage build.

My plan is to have both the existing sanitizer-windows bot and the new
one run concurrently, but the new one will connect to the silent,
staging buildmaster (lab.llvm.org:9994). Once we are ready to cut over,
I will turn off the old sanitizer-windows VM and update this port in the
docker image and redeploy.

I am chosing to stick with the buildbot annotation script approach,
because it allows for much faster iteration: I can adjust paths for the
VS installation for example simply by committing to zorg. However, both
the live and staging bot will use the same script, so the same script
must work for both sanitizer-windows bots at the same time!

Differential Revision: https://reviews.llvm.org/D93340
The file was addedbuildbot/google/docker/buildbot-sanitizer-windows/VERSION
The file was modifiedzorg/buildbot/builders/annotated/annotated_builder.py
The file was addedbuildbot/google/docker/buildbot-sanitizer-windows/Dockerfile
The file was addedbuildbot/google/docker/buildbot-sanitizer-windows/fix_buildbot_tac_paths.py
The file was addedbuildbot/google/docker/buildbot-sanitizer-windows/run.ps1
The file was addedbuildbot/google/docker/buildbot-sanitizer-windows/admin