SuccessChanges

Summary

  1. Remove #llvm buildbot as it doesn't scale to the size of the project anymore (details)
Commit 8f6915eab109b1f91ef3579c05da843b37268048 by dblaikie
Remove #llvm buildbot as it doesn't scale to the size of the project anymore

Broadcasting all breakage to all IRC users isn't effective - more
buildbots, more failure modes, means that there's almost always some
noise & a single breakage can result in many redundant mails from
distinct buildbots, making the channel difficult to use.

Differential Revision: https://reviews.llvm.org/D87100
The file was modifiedbuildbot/osuosl/master/config/status.py (diff)

Summary

  1. fix typos; improve a couple of descriptions; (details)
  2. Sema: extract a check for `isCFError` (NFC) (details)
  3. [HIP] Add gfx1031 and gfx1030 (details)
  4. Revert "Retry of D84974" (details)
  5. [Asan] Don't crash if metadata is not initialized (details)
  6. [NFC][Asan] Remove Debug code (details)
  7. [Hexagon] Handle widening of truncation's operand with legal result (details)
  8. [MLIR] Change Operation::create() methods to use Value/Type/Block ranges. (details)
Commit 66310aafa0da47dd4664a1200afc7e22cab15b65 by paul
fix typos; improve a couple of descriptions;
add release note
The file was modifiedllvm/docs/ReleaseNotes.rst
The file was modifiedllvm/docs/TableGen/ProgRef.rst
Commit f4ac79a364f2de7270a3238b176e17b40b036305 by Saleem Abdulrasool
Sema: extract a check for `isCFError` (NFC)

Extract a simple check to check if a `RecordDecl` is a `CFError` Decl.
This is a simple refactoring to prepare for an upcoming change.  NFC.

Patch is extracted from
https://github.com/llvm/llvm-project-staging/commit/8afaf3aad2af43cfedca7a24cd817848c4e95c0c.
The file was modifiedclang/lib/Sema/SemaType.cpp
The file was modifiedclang/include/clang/Sema/Sema.h
Commit 041da0d828e39d849c99adf1391aaa9291f4310f by Yaxun.Liu
[HIP] Add gfx1031 and gfx1030

Differential Revision: https://reviews.llvm.org/D87324
The file was addedclang/test/Driver/hip-offload-arch.hip
The file was modifiedclang/lib/Basic/Cuda.cpp
Commit 5c463d107d3c26fc5573f31b838a8a3a1e4b5065 by walter erquinigo
Revert "Retry of D84974"

This reverts commit 5b2b4f331d78f326e5e29166bec5ad92c864343d.

This caused a link error in
http://lab.llvm.org:8011/builders/lldb-x64-windows-ninja/builds/18794/steps/build/logs/stdio
The file was modifiedlldb/tools/lldb-vscode/lldb-vscode.cpp
The file was modifiedlldb/tools/lldb-vscode/package.json
The file was removedlldb/test/API/tools/lldb-vscode/runInTerminal/main.c
The file was modifiedlldb/tools/lldb-vscode/JSONUtils.h
The file was modifiedlldb/tools/lldb-vscode/VSCode.h
The file was modifiedlldb/packages/Python/lldbsuite/test/tools/lldb-vscode/vscode.py
The file was modifiedlldb/tools/lldb-vscode/JSONUtils.cpp
The file was removedlldb/test/API/tools/lldb-vscode/runInTerminal/TestVSCode_runInTerminal.py
The file was modifiedlldb/packages/Python/lldbsuite/test/tools/lldb-vscode/lldbvscode_testcase.py
The file was removedlldb/test/API/tools/lldb-vscode/runInTerminal/Makefile
The file was modifiedlldb/tools/lldb-vscode/VSCode.cpp
Commit c05095cd6865a95ee848cd95d11643969a81a241 by Vitaly Buka
[Asan] Don't crash if metadata is not initialized

Fixes https://github.com/google/sanitizers/issues/1193.

AsanChunk can be uninitialized yet just after return from the secondary
allocator. If lsan starts scan just before metadata assignment it can
fail to find corresponding AsanChunk.

It should be safe to ignore this and let lsan to assume that
AsanChunk is in the beginning of the block. This block is from the
secondary allocator and created with mmap, so it should not contain
any pointers and will make lsan to miss some leaks.

Similar already happens for primary allocator. If it can't find real
AsanChunk it falls back and assume that block starts with AsanChunk.
Then if the block is already returned to allocator we have  garbage in
AsanChunk and may scan dead memory hiding some leaks.
I'll fix this in D87135.

Reviewed By: morehouse

Differential Revision: https://reviews.llvm.org/D86931
The file was addedcompiler-rt/test/asan/TestCases/lsan_crash.cpp
The file was modifiedcompiler-rt/lib/asan/asan_allocator.cpp
Commit 27650a5fed14a99b5c3640444abb0012ca28f3fb by Vitaly Buka
[NFC][Asan] Remove Debug code

Used for https://github.com/google/sanitizers/issues/1193

Reviewed By: morehouse

Differential Revision: https://reviews.llvm.org/D86933
The file was modifiedcompiler-rt/lib/sanitizer_common/sanitizer_allocator_combined.h
The file was modifiedcompiler-rt/lib/sanitizer_common/sanitizer_allocator_primary32.h
The file was modifiedcompiler-rt/lib/asan/asan_allocator.cpp
The file was modifiedcompiler-rt/lib/lsan/lsan_common.cpp
The file was modifiedcompiler-rt/lib/sanitizer_common/sanitizer_allocator_primary64.h
Commit d183f472617dfedf23381be90612d713d0f439af by kparzysz
[Hexagon] Handle widening of truncation's operand with legal result

Failing example: v8i8 = truncate v8i32. v8i8 is legal, but v8i32 was
widened to HVX. Make sure that v8i8 does not get altered (even if it's
changed to another legal type).
The file was modifiedllvm/lib/Target/Hexagon/HexagonISelLowering.h
The file was addedllvm/test/CodeGen/Hexagon/autohvx/isel-truncate-legal.ll
The file was modifiedllvm/lib/Target/Hexagon/HexagonISelLoweringHVX.cpp
Commit 8893d0816ccdf8998d2e21b5430e9d6abe7ef465 by jurahul
[MLIR] Change Operation::create() methods to use Value/Type/Block ranges.

- Introduce a new BlockRange class to represent range of blocks (constructible from
  an ArrayRef<Block *> or a SuccessorRange);
- Change Operation::create() methods to use TypeRange for result types, ValueRange for
  operands and BlockRange for successors.

Differential Revision: https://reviews.llvm.org/D86985
The file was modifiedmlir/include/mlir/IR/BlockSupport.h
The file was modifiedmlir/include/mlir/IR/Operation.h
The file was modifiedmlir/lib/IR/OperationSupport.cpp
The file was modifiedmlir/lib/IR/Block.cpp
The file was modifiedmlir/lib/IR/Operation.cpp
The file was modifiedmlir/include/mlir/IR/OperationSupport.h

Summary

  1. Remove #llvm buildbot as it doesn't scale to the size of the project anymore (details)
Commit 8f6915eab109b1f91ef3579c05da843b37268048 by dblaikie
Remove #llvm buildbot as it doesn't scale to the size of the project anymore

Broadcasting all breakage to all IRC users isn't effective - more
buildbots, more failure modes, means that there's almost always some
noise & a single breakage can result in many redundant mails from
distinct buildbots, making the channel difficult to use.

Differential Revision: https://reviews.llvm.org/D87100
The file was modifiedbuildbot/osuosl/master/config/status.py