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

KDE Git Services - Bulk Change <[email protected]>
Newsgroups gmane.comp.kde.cvs
Message-ID <[email protected]>
Git repository change summary for qt/clang/llvm-project
Pushed by mirror-service into branch 'upstream/users/makslevental/mlir-c-operation-equivalence'.
Changed from a54a83750aeb5d7da55d69dcc21108edee10620c to a2756bd3087ef6310cca3d4e5f24428815259262
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 e89830da7f4e6656b9ff54ea7695c31435a53ee4 by GitHub (on behalf of eoineoineoin) on 01/08/2026 at 05:22..
Add option to format a whole file using git-clang-format (#204336)

Today, git-clang-format will only format lines which have been modified.
However, in some cases, that's not sufficient to get a "clean" file
which would be unmodified by running `clang-format` manually.

I've got a minimal repro using the default clang-format rules. Setup a
new git repository and create a commit with an empty file:

```
mkdir /tmp/bla
cd /tmp/bla
git init
touch t.cpp
git add t.cpp
git commit -m "V1"
```

Add a line to that file containing a comment:
```
echo "int x = 0; // Comment describing x" > t.cpp
git add t.cpp
git clang-format --staged # Reports "clang-format did not modify any files"
git commit -m "V2"
```

There's nothing wrong with this file yet, and it's working as expected.
Problem arises when we add a new line with a comment which is not
aligned with the comment we've already added:

```
echo "int longerThanX = 0; // Should cause above to become aligned" >> t.cpp
git add t.cpp
git clang-format --staged # Reports "clang-format did not modify any files"
```

git-clang-format didn't change the staged file here as it's only
inspecting the modified lines, but according to the default formatting
rules, this new line actually has an effect on the preceding line. i.e.,
if you run `clang-format t.cpp`, you'll see that whitespace is added
before the "Comment describing x" to align with the "Should cause..."

It's not limited to _just_ the preceding line (e.g. in the case where we
have multiple lines like the first with comments which become
unaligned,) so can't just add more lines of context to the diff. This PR
just adds an option to format the whole file, instead of just the
modified sections.
https://invent.kde.org/qt/clang/llvm-project/-/commit/e89830da7f4e6656b9ff54ea7695c31435a53ee4

Git commit 9a15298e9664f723c9379c7972735f3c2292829d by GitHub (on behalf of Jonas Devlieghere) on 01/08/2026 at 05:22..
[lldb][test] Skip the JSON symbol file test on WebAssembly (#213407)

A JSON symbol file requires the UUID of the module it describes, and a
WebAssembly module carries no UUID.
https://invent.kde.org/qt/clang/llvm-project/-/commit/9a15298e9664f723c9379c7972735f3c2292829d

Git commit d9e699957d02e8bbf332943b38579909bb8d1005 by GitHub (on behalf of Fangrui Song) on 01/08/2026 at 05:35..
[X86AsmBackend] Define reset() hook (#213409)

Noticed when reviewing #175830: MCObjectStreamer::reset frees the
fragments PendingBA and PrevInstPosition point into, but X86AsmBackend
keeps them. Define the hook.
https://invent.kde.org/qt/clang/llvm-project/-/commit/d9e699957d02e8bbf332943b38579909bb8d1005

Git commit b94b699857a5de41b0def1cffca6908e584be27f by GitHub (on behalf of Alexander Richardson) on 01/08/2026 at 05:45..
[RISCV] Fix ISCVISAInfo::computeDefaultABI() result for xcheriot (#212129)

XCheriot was not considered in this function, so RV32E+XCheriot
defaulted
to ilp32e instead of cheriot when no -target-abi was given.

Since this function does not have unit test coverage, this adds new
tests
for the ABI inference functions: RISCVISAInfo::computeDefaultABI() and
RISCVABI::computeTargetABI.

This change was created with the help of AI tools
https://invent.kde.org/qt/clang/llvm-project/-/commit/b94b699857a5de41b0def1cffca6908e584be27f

Git commit 3c3a18e239fcb79ad780cc95ac7554046876da2a by GitHub (on behalf of Matt Arsenault) on 01/08/2026 at 06:14..
clang: Store vendor GPU kinds in OffloadArch instead of re-listing GPUs (#213362)

OffloadArch was a flat enum that hand-duplicated every AMDGPU and NVPTX
target, plus a few edge cases. This was yet another place that needed
updating every time a new target is added, which should now be avoided.
Replace with a tagged union-like scheme.

Co-authored-by: Claude (Claude-Opus-4.8) <[email protected]>
https://invent.kde.org/qt/clang/llvm-project/-/commit/3c3a18e239fcb79ad780cc95ac7554046876da2a

Git commit c27bee245fc0cbc1881632c1546a946fd96d305e by GitHub (on behalf of K.Roy) on 01/08/2026 at 06:15..
[AMDGPU] Generalize MFMA VGPR->AGPR opcode mapping (NFC) (#213274)

Move the VGPR/AGPR pairing out of MFMATable into a generalized
AGPRFormTable class and rename getMFMASrcCVDstAGPROp to getAGPRFormOp.
MFMATable inherits AGPRFormTable, so the instantiation sites and the
generated table are unchanged.

Other instruction families with paired VGPR/AGPR pseudos, such as DS,
can now be tagged with AGPRFormTable.

Related to #168983
https://invent.kde.org/qt/clang/llvm-project/-/commit/c27bee245fc0cbc1881632c1546a946fd96d305e

Git commit 6b98f82fe93ff6a0b83677e19f3672bbb7aef79f by GitHub (on behalf of Matt Arsenault) on 01/08/2026 at 07:41..
cmake: Derive CMake system name from a triple via new mechanism (#208773)
https://invent.kde.org/qt/clang/llvm-project/-/commit/6b98f82fe93ff6a0b83677e19f3672bbb7aef79f

Git commit 50b15d698817f7089a9b3ecda71c20f3ee450de2 by makslevental on 01/08/2026 at 08:26..
[mlir-c] Add structural operation equivalence
https://invent.kde.org/qt/clang/llvm-project/-/commit/50b15d698817f7089a9b3ecda71c20f3ee450de2

Git commit a2756bd3087ef6310cca3d4e5f24428815259262 by makslevental on 01/08/2026 at 08:26..
Address review: fix -Wenum-compare build failure, add structural hash, expand flag coverage
https://invent.kde.org/qt/clang/llvm-project/-/commit/a2756bd3087ef6310cca3d4e5f24428815259262
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.