[qt/clang/llvm-project]: Summary of bulk changes made

Git repository change summary for qt/clang/llvm-project
Pushed by mirror-service into branch 'upstream/users/arsenm/amdgpu-export-feature-bitset'.
Changed from eef072d597fa0f1b30aa818c812a6acf46175fde to 2e14bedeb5966e352e49356fec56be591c7783c6
Acknowledgement was received that this change introduces only existing code that has been pushed to another public open source repository.

This change contains the following new commits:

Git commit c5b02a931385d197ef634ae0c21102ea52626e18 by GitHub (on behalf of Dave Lee) on 03/08/2026 at 17:15..
[lldb][bytecode] Improve testing of bytecode section loading (#212568)

Add tests for loading embedded bytecode formatters from binaries.

Assisted-by: claude
https://invent.kde.org/qt/clang/llvm-project/-/commit/c5b02a931385d197ef634ae0c21102ea52626e18

Git commit dd9eb9a5c397d4e5f39a31b38013dc8731c5b64b by GitHub (on behalf of Justin Fargnoli) on 03/08/2026 at 17:20..
[LTO][CodeMetrics] Count indirect calls as inline candidates when `PrepareForLTO` is set (#192154)

Indirect calls may be resolved during the post-link LLVM pipeline. Thus, count them as potential inline candidates during the pre-link LTO phase.
https://invent.kde.org/qt/clang/llvm-project/-/commit/dd9eb9a5c397d4e5f39a31b38013dc8731c5b64b

Git commit 27cc956b00682b5e9162e7325edde51f264d69d6 by GitHub (on behalf of Alexey Bataev) on 03/08/2026 at 17:26..
[SLP]Keep tree-claimed peeled reassociated scalars alive

Peeled scalars are erased unconditionally, but a gather node may still
reference one in its generated buildvector. Keep such scalars (and the
peeled scalars in their operand chains) as plain scalar code.

Fixes #213674

Reviewers: 

Pull Request: https://github.com/llvm/llvm-project/pull/213724
https://invent.kde.org/qt/clang/llvm-project/-/commit/27cc956b00682b5e9162e7325edde51f264d69d6

Git commit 2ff5099be4ea2f88609c23037fdbe4e355739a04 by GitHub (on behalf of Florian Hahn) on 03/08/2026 at 17:34..
[ConstraintElim] Set NSW on sub when simplifying ssub.with.overflow. (#213532)

When simplifying ssub.with.overflow to a plain sub, we already proven
that the sub does not sign wrap. Replace it with `sub nsw`.

No changes on
https://github.com/dtcxzyw/llvm-opt-benchmark-nightly/pull/842, but
there is very little usage of ssub.with.overflow in default C/C++
builds.

It improves optimizations for code where ssub.with.overflow is used more
widely, like Clang + UBSan or Swift where checked arithmetic is the
default.

A simple C example is https://clang.godbolt.org/z/cv5MbYsrz

PR: https://github.com/llvm/llvm-project/pull/213532
https://invent.kde.org/qt/clang/llvm-project/-/commit/2ff5099be4ea2f88609c23037fdbe4e355739a04

Git commit fc1f3e7a26f202a3928daa4102027e4c31746513 by GitHub (on behalf of Arseniy Obolenskiy) on 03/08/2026 at 17:49..
Revert "Reland "[AMDGPU] Fix llvm.amdgcn.ballot with return width != wavefront size"" (#213713)

Reverts llvm/llvm-project#213635

buildbot failures are reported here:
https://github.com/llvm/llvm-project/pull/213635#issuecomment-5169081277
https://invent.kde.org/qt/clang/llvm-project/-/commit/fc1f3e7a26f202a3928daa4102027e4c31746513

Git commit 57965996196ca9caf62784392caf478a9d4133b3 by GitHub (on behalf of Alexey Bataev) on 03/08/2026 at 17:50..
[SLP]Allow unordered fadd reductions with reassoc only

The unordered reduction matcher required isAssociative() for fadd,
i.e. reassoc + nsz, a condition inherited from InstCombine-style
reassociation that also cancels and folds terms. Pure regrouping of
additions cannot change the sign of a zero result, so nsz is not
needed here: the reduction is seeded with the exact -0.0 identity,
the repeated-value multiplier preserves the sign of zero, and
constant folding is IEEE-exact. Brings the fadd requirement in line
with RecurrenceDescriptor, LV and with fmul, which accept reassoc
alone.

Reviewers: hiraditya, bababuck, RKSimon

Pull Request: https://github.com/llvm/llvm-project/pull/213261
https://invent.kde.org/qt/clang/llvm-project/-/commit/57965996196ca9caf62784392caf478a9d4133b3

Git commit d8952cde88ae46e2824dc12fefa2eb87c49686ca by GitHub (on behalf of Gábor Horváth) on 03/08/2026 at 18:02..
[clang][APINotes] Do not duplicate Escapable and Copyable attributes (#213716)

Applying them when they already present is a wasted allocation and can
also cause trouble in the Swift compiler that can complain about
duplicated attributes.

rdar://174868727
https://invent.kde.org/qt/clang/llvm-project/-/commit/d8952cde88ae46e2824dc12fefa2eb87c49686ca

Git commit 01935196807a3e816580d36616f5ec02ad8e50ef by GitHub (on behalf of Ramkumar Ramachandra) on 03/08/2026 at 18:04..
Partial-revert "[IR] Make semantics of strictfp consistent v2" (#213723)

This partially reverts 15bb4a97a7 ([IR] Make semantics of strictfp
consistent v2, #211769) due to a verifier failure in real-world code,
disabling just the verifier-check with a FIXME. The reason for a partial
manual-revert is because a clean revert doesn't apply cleanly: in
particular, the LangRef is untouched by this patch.

Ref:
https://github.com/llvm/llvm-project/pull/211769#issuecomment-5169150682
https://invent.kde.org/qt/clang/llvm-project/-/commit/01935196807a3e816580d36616f5ec02ad8e50ef

Git commit 79beb26b22e15932bfe85c91fcac3ce96ccc7c19 by GitHub (on behalf of Reid Kleckner) on 03/08/2026 at 18:17..
[clang-tidy][docs] Rename static analyzer check docs to Markdown (#211448)

Tracking issue: #201242
See the [migration guide] for more information. 

[migration guide]:
https://llvm.org/docs/SphinxQuickstartTemplate.html#markdown-migration-guidelines

This is the initial straight rename commit. It will probably break the
docs build, but it has to be a separate PR for blame preservation
purposes.
https://invent.kde.org/qt/clang/llvm-project/-/commit/79beb26b22e15932bfe85c91fcac3ce96ccc7c19

Git commit d2bfc1b9d50552533a099e4d5b6501068ec8b8d8 by GitHub (on behalf of Reid Kleckner) on 03/08/2026 at 18:34..
[clang-tidy][docs] Generate static analyzer check docs as Markdown (#211449)

Tracking issue: #201242
See the [migration guide] for more information. 

[migration guide]:
https://llvm.org/docs/SphinxQuickstartTemplate.html#markdown-migration-guidelines
This is a stacked PR based on #211448 , which will be a standalone
commit that
renames *.rst -> *.md before this PR lands for history preservation
purposes.

Unlike the other changes in this series, most of these changes are from
the generator script. Ignore all files under checks/ except `list.md`,
that is hand-modified. I confirmed that running the generator script
produces no changes.

Notably, the generator script *added new files*, since it seems there
are new checks since the script was run.
https://invent.kde.org/qt/clang/llvm-project/-/commit/d2bfc1b9d50552533a099e4d5b6501068ec8b8d8

Git commit 4296c142ee473b640fac9c8f0af0012e8496d039 by GitHub (on behalf of Aidan Lam) on 03/08/2026 at 18:40..
[libc++][docs] Mark LWG3116 as Complete (#209916)

We can mark this issue as completed because the fix for LWG 3116 is
already implemented in <scoped_allocator>, and no further tests are
needed.

Why no further tests are needed: The existing test suite in
libcxx/test/std/utilities/allocator.adaptor/allocator.adaptor.members/construct.pass.cpp
already provides full coverage for the scenario explained in lwg3116.

This test suite instantiates nested scoped allocators (using A1 and A2)
and calls .construct(). Because std::allocator_traits cannot be
instantiated with a reference type (e.g., A1&), this test suite would
fail to compile if the reference-stripping fix were missing.

Closes #100244
https://invent.kde.org/qt/clang/llvm-project/-/commit/4296c142ee473b640fac9c8f0af0012e8496d039

Git commit f338032ff6f5c4d082cde3d9e89c95afc3b6982a by GitHub (on behalf of Alexey Bataev) on 03/08/2026 at 18:47..
[SLP]Support copyable fmuls in fmuladd, modeled as fmuladd(a, b, -0.0)

A copyable lane holding a single-use fmul a, b is modeled as
fmuladd(a, b, -0.0), which equals fmul a, b (the add of -0.0 is exact
and preserves signed zeros), so the multiply dies instead of being
computed and gathered. Applied only when every copyable lane is such
an fmul; multi-use fmuls and mixed copyables keep the
addend/multiplicand modeling. On a tie between fmuladd and fmul main
ops, fmuladd is preferred only when the fmuls are absorbed profitably:
single-use, operands not part of the list and vectorizable as
multiplicand operands.

Reviewers: bababuck, hiraditya, RKSimon

Pull Request: https://github.com/llvm/llvm-project/pull/213369
https://invent.kde.org/qt/clang/llvm-project/-/commit/f338032ff6f5c4d082cde3d9e89c95afc3b6982a

Git commit 2ca22b6fe252f84e2c80528258446d609aa814fe by GitHub (on behalf of anoopkg6) on 03/08/2026 at 18:54..
[SystemZ] Fix crash in EmitTargetCodeForMemmove with i32 size operand (#213726)

SystemZISD::MEMMOVE requires an i64 length operand, but Size was passed
raw. A constant size literal can be represented as i32, causing a
SelectionDAG verifier crash observed when compiling SPEC CPU benchmarks
wrf, cam4 and fotonik3d with -march=z17 -O3.

Fix by zero-extending Size to i64 before building the node.

Co-authored-by: [email protected] <[email protected]>
https://invent.kde.org/qt/clang/llvm-project/-/commit/2ca22b6fe252f84e2c80528258446d609aa814fe

Git commit d5a6124259b55789bc49489632efa7c168a4f6cb by GitHub (on behalf of Andy Kaylor) on 03/08/2026 at 18:55..
[CIR] Fix cleanup of temporaries with null-checked new expr (#213376)

We had a problem where a new expression that required both a null check
of the allocated pointer and a cleanup of temporaries values created for
the initializer was causing us to generate an unterminated cleanup
scope. This was happening because we weren't pre-creating a cleanup
scope around the entire expression for the temporary and ended up
emitting it in an unexpected location.

This change adds a check for the null-checked new expression in
`ConditionalEvaluationFinder` and wraps the call to emit the initializer
with `ConditionEvalulation::begin/endEvaluation` calls.

Note that I have sunk the `begin/endEvaluation` into the `emitInit`
lambda so that it can surround just the `emitNewInitializer` call and
not the `enterNewDeleteCleanup` call, which creates a local cleanup
scope for the case where the allocation succeeded but the constructor
throws an exception. Classic codegen calls `begin/endEvaluation` at a
higher level and ends up using an active flag for the allocation delete
cleanup even though the flag is always true when that cleanup is
reached.

Assisted-by: Cursor / various models
https://invent.kde.org/qt/clang/llvm-project/-/commit/d5a6124259b55789bc49489632efa7c168a4f6cb

Git commit 8f94ddb3e730a613885ef36384ebc50c9146ed85 by GitHub (on behalf of Raul Tambre) on 03/08/2026 at 19:12..
[lldb][test] Pick correct frontend depending on test language (#212848)

Clang configuration files may contain frontend-specific options.
So building Objective C files with the clang++ may fail due to an option not being available for the C frontend.
Clean up the code slightly and pick the correct compiler based on the file extension.
https://invent.kde.org/qt/clang/llvm-project/-/commit/8f94ddb3e730a613885ef36384ebc50c9146ed85

Git commit 9e8e0d454a4c6d9aafc36c566fe831947facee0c by GitHub (on behalf of Alexey Bataev) on 03/08/2026 at 19:15..
Revert "[SLP]Support copyable fmuls in fmuladd, modeled as fmuladd(a, b, -0.0)"

This reverts commit f338032ff6f5c4d082cde3d9e89c95afc3b6982a to fix
https://lab.llvm.org/buildbot/#/builders/227/builds/3894.

Reviewers: 

Pull Request: https://github.com/llvm/llvm-project/pull/213741
https://invent.kde.org/qt/clang/llvm-project/-/commit/9e8e0d454a4c6d9aafc36c566fe831947facee0c

Git commit d3184bc6c6a8129f5b53cbce939dc197883e71b6 by GitHub (on behalf of Usama Hameed) on 03/08/2026 at 19:17..
[clang] Don't warn on stack_protector_ignore in system macros (#213167)

Under -fstack-protector-all, stack_protector_ignore on a local is inert.
The warning is therefore accurate, and it stays useful in user code --
an opt-out that silently does nothing is worth knowing about.

The warning is not actionable when the attribute comes from a system
header macro and so this change disables it in system macros. Behavior
is otherwise unchanged. The attribute was already being ignored, so
suppressing the diagnostic hides nothing.

Also extend stack-protector-metadata.ll to cover the remaining
protection levels: test3/test4 for sspreq, where the opt-out metadata is
ignored, and test5/test6 for sspstrong, where it is honored. Only ssp
was covered before.

rdar://173529401
https://invent.kde.org/qt/clang/llvm-project/-/commit/d3184bc6c6a8129f5b53cbce939dc197883e71b6

Git commit 7167f5b066f9bb91913293b4ddb8ac9b2cb29db3 by GitHub (on behalf of Artem Belevich) on 03/08/2026 at 19:24..
[clang][CUDA] Add support for CUDA 13.3, CUDA 13.4, and sm_107 (Rubin) (#211677)

Clang counterpart to the changes in #210646
- add Clang support for CUDA versions 13.3 and 13.4 (with PTX 9.3 and PTX 9.4)
- add support for targeting sm_107 / sm_107a / sm_107f (Rubin) GPU architecture.
https://invent.kde.org/qt/clang/llvm-project/-/commit/7167f5b066f9bb91913293b4ddb8ac9b2cb29db3

Git commit 895c744404962166c3d46f628ac38622fb47ea10 by GitHub (on behalf of Sam Clegg) on 03/08/2026 at 19:43..
[OpenMP] Remove Wasm limitation from openmp/runtime/cmake/config-ix.cmake (#213742)

This was originally added #71297, but this limitation no longer applies
to emscripten, and wasi-sdk will surly support this once threading is
ready there.
https://invent.kde.org/qt/clang/llvm-project/-/commit/895c744404962166c3d46f628ac38622fb47ea10

Git commit 0a8ded578e787a3296ed9895cad78293e92eeef1 by GitHub (on behalf of Andy Kaylor) on 03/08/2026 at 19:58..
[CIR] Attach FenvAttr when strictfp mode is in effect (#213368)

This change adds tracking of floating-point constraints via the
CIRGenFPOptionsRAII object, deriving the state from the FP features in
effect tracking in the Clang AST. When we are about to generate an
operation that may require floating point constraints, a
CIRGenFPOptionsRAII object is used to get the effective floating-point
state from the expression for which we are generating the operations.
This object in turn sets the floating-point state of the CIRGenBuilder
which uses these settings to determine whether a cir::FenvAttr should be
attached to generated objects and, if so, what its state should be.

This does not cover complex operations, AArch64 builtins, or global
constructors. Those will be updated in follow-up changes.

Assisted-by: Cursor / various models
https://invent.kde.org/qt/clang/llvm-project/-/commit/0a8ded578e787a3296ed9895cad78293e92eeef1

Git commit f96829fc3530cd598855bf56118727be9ae467ac by GitHub (on behalf of Anshil Gandhi) on 03/08/2026 at 20:08..
[SandboxVec] Rename BottomUpVec to BundleVec (#213197)

Use `bundle-vec(bottom-up)` or `bundle-vec(top-down)` to run the
bottom-up or top-down bundle vectorizer, respectively. For example:
```
opt -passes=sandbox-vectorizer \
-sbvec-collect-seeds=loads \
-sbvec-passes="seed-collection<tr-save,bundle-vec(top-down),tr-accept>" \
input.ll -S -o out.ll

opt -passes=sandbox-vectorizer \
-sbvec-collect-seeds=stores \
-sbvec-passes="seed-collection<tr-save,bundle-vec(bottom-up),tr-accept>" \
input.ll -S -o out.ll
```

This commit is NFC, except the BundleVec requiring the user to specify
the direction upon invocation.
https://invent.kde.org/qt/clang/llvm-project/-/commit/f96829fc3530cd598855bf56118727be9ae467ac

Git commit 4222f1a295638c8c9d2eecf8dd29a0df6da5ad88 by GitHub (on behalf of Artem Belevich) on 03/08/2026 at 20:08..
[llvm][NVPTX] Add EF_CUDA_SM107 to ELF CUDA architectures (#213747)
https://invent.kde.org/qt/clang/llvm-project/-/commit/4222f1a295638c8c9d2eecf8dd29a0df6da5ad88

Git commit 0f068e7ba2ddfeaf078f87d53a33c6d662d4ce10 by GitHub (on behalf of Jonas Devlieghere) on 03/08/2026 at 20:24..
[lldb] Identify a WebAssembly module by its build id (#213554)

A Wasm module carries the identifier its linker gave it in a `build_id`
custom section, whose payload is the length of the identifier followed
by its bytes. That identifier is the only thing that tells one build of
a module from another.

`wasm-ld` emits the section only when asked, so the API test build asks
for it. A module linked without one still has no UUID.
https://invent.kde.org/qt/clang/llvm-project/-/commit/0f068e7ba2ddfeaf078f87d53a33c6d662d4ce10

Git commit 2254bccea87cce9bdb568608d27440c2c1651eb3 by GitHub (on behalf of Alexey Bataev) on 03/08/2026 at 20:35..
[SLP]Support copyable fmuls in fmuladd, modeled as fmuladd(a, b, -0.0)

A copyable lane holding a single-use fmul a, b is modeled as
fmuladd(a, b, -0.0), which equals fmul a, b (the add of -0.0 is exact
and preserves signed zeros), so the multiply dies instead of being
computed and gathered. Applied only when every copyable lane is such
an fmul; multi-use fmuls and mixed copyables keep the
addend/multiplicand modeling. On a tie between fmuladd and fmul main
ops, fmuladd is preferred only when the fmuls are absorbed profitably:
single-use, operands not part of the list and vectorizable as
multiplicand operands.

Original Pull Request: https://github.com/llvm/llvm-project/pull/213369

Recommit after the fix for the revert in 9e8e0d454a4c6d9aafc36c566fe831947facee0c

Reviewers: 

Pull Request: https://github.com/llvm/llvm-project/pull/213757
https://invent.kde.org/qt/clang/llvm-project/-/commit/2254bccea87cce9bdb568608d27440c2c1651eb3

Git commit 4b8274f741aee8298c3a3b5c2f3910b361b55d73 by GitHub (on behalf of Matt Arsenault) on 03/08/2026 at 20:52..
AMDGPU: Remove cvt-pknorm-vop3-insts from feature map (#213615)

This isn't used in clang for any builtin, so don't leak this.
https://invent.kde.org/qt/clang/llvm-project/-/commit/4b8274f741aee8298c3a3b5c2f3910b361b55d73

Git commit 2df0db6952fb5e059b14470c96a922683dc95a66 by GitHub (on behalf of Adam Magier) on 03/08/2026 at 21:21..
[UBSan] Fix assertion failure in EmitCheckedInBoundsGEP for constant-… (#191278)

…folded overflowing offsets

EmitGEPOffsetInBytes has two paths: for fully constant GEPs it subtracts
pointer values and always returns OffsetOverflows=false, but for
non-constant GEPs it iterates operands using checked arithmetic. The
assertion in EmitCheckedInBoundsGEP assumed a constant TotalOffset
implies no overflow, conflating the two paths.

In the non-constant path, the offset can be entirely constant-folded
(constant index * constant element size) while the GEP itself remains
non-constant (runtime base pointer). If that arithmetic overflows
intptr_t, we get a constant TotalOffset with OffsetOverflows=true,
triggering the assertion. This is easily hit on 16-bit targets like
MSP430 with realistic struct array indices.

Remove the assertion. The existing codegen already handles this
correctly: the constant OffsetOverflows=true propagates into the check
condition, making the sanitizer always fire at runtime.

Fixes: https://github.com/llvm/llvm-project/issues/48168

Assisted-by: Kiro CLI / Claude Opus 4.6 (1M context)
https://invent.kde.org/qt/clang/llvm-project/-/commit/2df0db6952fb5e059b14470c96a922683dc95a66

Git commit ece39fd91f57e943a50c3d67873b75b90c933a7d by GitHub (on behalf of Erich Keane) on 03/08/2026 at 21:22..
[CIR]Add RecordType to our dense-array optimization in lowering (#213725)

This is an issue in AMDGPUAsmParser.cpp self-build, we have a lot of
record elements (~360k+!) in an array that causes us to have this TU be
near-never-ending(hour+). Classic codegen compiles this sub-minute on my
machine. With this patch, we are only about a 30% increase in time.

Note: Claude wrote much of the tests after I got through every exception
I could think of. I think this covers everything, and I hope there is no
missing coverage.
https://invent.kde.org/qt/clang/llvm-project/-/commit/ece39fd91f57e943a50c3d67873b75b90c933a7d

Git commit 1e30ad88359b91be611e11fe49434440ae446799 by GitHub (on behalf of Alex MacLean) on 03/08/2026 at 21:39..
[NVPTX] Remove redundant state from TargetMachine and Subtarget (NFC) (#213715)
https://invent.kde.org/qt/clang/llvm-project/-/commit/1e30ad88359b91be611e11fe49434440ae446799

Git commit 7f04a40a220e2c741d4ae88a39ed9d4c7c87ff25 by GitHub (on behalf of satyanarayana reddy janga) on 03/08/2026 at 21:41..
[lldb][minidump] write the memory after an unreadable page when saving minidump (#212641)

**Issue**
An internal failing test found a latent bug in lldb's save-core
(minidump writer). When it saved a memory range that had an unreadable
page in it, it:
  - stopped at that page and threw away the readable memory after it, 

Result: We couldnot get the stack traces from the minidump. in the below
example the **current logic is bailing out at the 6th region and not
writing other 70 regions.**

```
[[email protected] ~/fbsource/fbcode (eacbfddefa|remote/master)]$ lldb
(lldb) file /data/users/satyajanga/fbsource/buck-out/v2/art/fbcode/55005549ebc49982/sand/tests/__Coro__/Coro
Current executable set to '/data/users/satyajanga/fbsource/buck-out/v2/art/fbcode/55005549ebc49982/sand/tests/__Coro__/Coro' (x86_64).
(lldb) b coro.cpp:44                                                                                                                              Breakpoint 1: where = Coro`::co_main() + 197 at coro.cpp:44, address = 0x00000000002335a5
(lldb) r
Process 3374177 launched: '/data/users/satyajanga/fbsource/buck-out/v2/art/fbcode/55005549ebc49982/sand/tests/__Coro__/Coro' (x86_64)
warning: (x86_64) /data/users/satyajanga/fbsource/buck-out/v2/art/fbcode/55005549ebc49982/sand/tests/__Coro__/__Coro__shared_libs_symlink_tree/libfolly_futures_tree.so unable to locate separate debug file (dwo, dwp). Debugging will be degraded (troubleshoot with https://fburl.com/missing_dwo)
Process 3374177 stopped
* thread #9, name = 'GlobalCPUThread', stop reason = breakpoint 1.1
       frame #0: 0x00000000002335a5 Coro`::co_main() at coro.cpp:44
(lldb) script
Python Interactive Interpreter. To exit, type 'quit()', 'exit()' or Ctrl-D.
>>> target = lldb.debugger.GetSelectedTarget()
>>> process = target.GetProcess()
>>> regions = process.GetMemoryRegions()
>>> len(regions)
76
>>> for i in range(len(regions)):
...   region = regions[i]
...   if not region.IsReadable():
...     continue
...   base, end = region.GetRegionBase(), region.GetRegionEnd()
...   size = end - base
...   name = region.GetName() or ""
...   error = lldb.SBError()
...   data = process.ReadMemory(base, size, error)
...   bytes_read = len(data) if data else 0
...   if error.Success() and bytes_read == size:
...     continue
...   print(f" FAILED to read  region {i}, {name}  ")
...
 FAILED to read  region 6,
 FAILED to read  region 8,
 FAILED to read  region 10,
 FAILED to read  region 12,
 FAILED to read  region 15,
 FAILED to read  region 65, [vvar]
 FAILED to read  region 66, [vvar_vclock]
>>>
```

  

**Fix**

Rewrote ReadWriteMemoryInChunks in MinidumpFileBuilder.cpp to: save the
readable bytes, zero-fill the unreadable page, keep going, and record
the exact number of bytes actually written. That keeps the dump aligned
and preserves memory after a hole.

 **Test**
Added an lldb API test that builds a memory region with a readable page
followed by an unreadable tail, saves a core of it, and checks the
readable data comes back intact
https://invent.kde.org/qt/clang/llvm-project/-/commit/7f04a40a220e2c741d4ae88a39ed9d4c7c87ff25

Git commit 7d9580d588df77aa5128055b006a90de9442a994 by GitHub (on behalf of Michael Jones) on 03/08/2026 at 21:43..
[libc] Fix elf_proxy header generation (#213737)

Followup to fix the generated proxy header after #211428.

Assisted-by: Automated tooling, human reviewed.
https://invent.kde.org/qt/clang/llvm-project/-/commit/7d9580d588df77aa5128055b006a90de9442a994

Git commit 97b34d6d63381bcd8bf36b6859bd2d9d0f5d1b76 by GitHub (on behalf of Matt Arsenault) on 03/08/2026 at 21:54..
AMDGPU: Tablegenerate TargetParser feature sets (#212945)

Traditionally we maintained 2 parallel feature mechanisms,
one in clang (later moved to TargetParser), with largely
mirrored subtarget features defined in the backend. Start
directly taking feature information from the backend and putting
it into TargetParser. This is still in a compromise mid-migration
state. We still have both the legacy "ArchAttr" bitfield integer,
plus a new AMDGPUFeatureBitset field stored in the table, which
isn't yet exported.

For the moment, the new bitset is only used to populate the
feature string name map, which is the big maintainability win.
This also lists an explicit subset of exported features to
avoid churn.

Co-authored-by: Claude (Claude-Opus-4.8)
https://invent.kde.org/qt/clang/llvm-project/-/commit/97b34d6d63381bcd8bf36b6859bd2d9d0f5d1b76

Git commit 2e14bedeb5966e352e49356fec56be591c7783c6 by Matt Arsenault on 03/08/2026 at 21:57..
AMDGPU: Export the TargetParser feature bitset

Previously this bitset was only used to populate the feature
name string map used by clang. Eventually this will replace
the current bitmask integer. AArch64 already has a similar
interface.

Co-authored-by: Claude (Claude-Opus-4.8)
https://invent.kde.org/qt/clang/llvm-project/-/commit/2e14bedeb5966e352e49356fec56be591c7783c6