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

Git repository change summary for qt/clang/llvm
Pushed by mirror-service into branch 'upstream/users/ojhunt/undeduced-deleted-overload-result'.
Changed from 0000000000000000000000000000000000000000 to f8357566dde882ef967c7cf5383ecd2785e08859
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 89b84291ffc0b7d35f86bfc687f0528e44998a42 by GitHub (on behalf of Jannick Kremer) on 23/07/2026 at 23:28..
[libclang/python] Remove global SPELLING_CACHE alias (#210677)

This completes the second step of
https://github.com/llvm/llvm-project/issues/156680
This change is a follow-up to
https://github.com/llvm/llvm-project/pull/177586, following the release
branching, to ensure a one release-cycle deprecation period.

---------

Co-authored-by: Vlad Serebrennikov <[email protected]>
https://invent.kde.org/qt/clang/llvm/-/commit/89b84291ffc0b7d35f86bfc687f0528e44998a42

Git commit bee0671fa8fa2f0f49e0a6c549240ac2da7e8067 by GitHub (on behalf of Jiahao Guo) on 23/07/2026 at 23:37..
[CIR][AArch64] Lower Vector saturating shift and narrow intrinsics (#209389)

### summary

part of : https://github.com/llvm/llvm-project/issues/185382

lower all intrinsics in :
https://arm-software.github.io/acle/neon_intrinsics/advsimd.html#vector-saturating-shift-right-and-narrow
https://invent.kde.org/qt/clang/llvm/-/commit/bee0671fa8fa2f0f49e0a6c549240ac2da7e8067

Git commit 490b49fa2bf09948de3967fa6b89d46cf82afe01 by GitHub (on behalf of Jason Molenda) on 23/07/2026 at 23:44..
[lldb] Fix qSpeedTest radix mistake, make number parsings explicit (#211495)

The documentation for qSpeedTest says

```
send packet: qSpeedTest:response_size:response-size;
read packet: data:<response data>

response-size is a hex encoded unsigned number up to 64 bits in size.
```

debugserver implements qSpeedTest as per this documentation, but lldb
sends the number in decimal (base 10), and lldb-server parses it as base
10. I changed lldb and lldb-server to base 16. This is a maintenance
command used by lldb developers exclusivley, so IMO I'm not handling a
migration for old/new servers or defining a new packet or key. I was
running some packet transmission tests with debugserver and noticed
debugserver was sending much larger packets than requested; that's the
kind of failure you see when there is a mismatch.

I audited all uses of `getAsInteger()` that pass a 0 for the radix,
meaning auto-detect the radix, in the gdb-remote dir and changed nearly
all of them to specify either base 10 or base 16. There were two places
where we were using auto-sensing on a base 16 number (and no "0x"
prefix), which would parse incorrectly if an [a-f] letter did not occur.

There is one use of `getAsInteger(0,...)` that is still in place, for
pasing the `qRegisterInfo` eh-frame/dwarf register numbers. Our
documentation for these keys specifies that they may be base 10 or base
16 if prefixed with 0x. This is unlike anywhere else in gdb remote
serial protocol, and smells like something I probably stuck in there 15+
years ago because I've never liked the ambiguity about number bases in
the protocol and I made this half-hearted stab at encouraging use of
"0x".

It is always fun to see the inconsistencies as you review multiple
packets. qProcessInfo returns keys like pid/gid/ppid in base 16.
qfProcessInfo returns the same keys in base 10. qHostInfo returns
cputype/cpusubtype (a Mach-O way of specifying a target cpu) in base 10,
qProcessInfo returns the same keys in base 16. There's so many of these
kinds of little inconsistencies :/
https://invent.kde.org/qt/clang/llvm/-/commit/490b49fa2bf09948de3967fa6b89d46cf82afe01

Git commit 1ec7a13fb238f17afd89886071a13f7210ef3583 by GitHub (on behalf of arrowten) on 23/07/2026 at 23:50..
[Sema] Fix assertion in TreeTransform when rebuilding CXXParenListInitExpr (#203715)
https://invent.kde.org/qt/clang/llvm/-/commit/1ec7a13fb238f17afd89886071a13f7210ef3583

Git commit 31b6ee93ed0db072a62b4365aeb7c32705c52596 by GitHub (on behalf of Jon Roelofs) on 24/07/2026 at 00:10..
[llvm][AArch64] Enable .cfi_set_ra_state by default for PAuth_LR (#211698)
https://invent.kde.org/qt/clang/llvm/-/commit/31b6ee93ed0db072a62b4365aeb7c32705c52596

Git commit 257e81f2e9a67cb857bd6f801e1708c96bee99e4 by GitHub (on behalf of Vitaly Buka) on 24/07/2026 at 00:36..
Revert "[mlir][tosa] Combine unranked/ranked tensor types into single type" (#211701)

Reverts llvm/llvm-project#209737

Breaks bots, see
https://github.com/llvm/llvm-project/pull/209737#issuecomment-5064857765
https://invent.kde.org/qt/clang/llvm/-/commit/257e81f2e9a67cb857bd6f801e1708c96bee99e4

Git commit 725737bf88b8219d32e1723ceb653a0e706cc204 by GitHub (on behalf of Karim Alweheshy) on 24/07/2026 at 01:12..
[LLVM] Auto-upgrade legacy coro.end results (#211081)

When `llvm.coro.end` and `llvm.coro.end.async` changed from returning
`i1`
to returning `void` in #159278, the bitcode auto-upgrader continued to
handle
only the older two-argument `llvm.coro.end` form.

As a result, valid bitcode produced before that transition fails
verification
when a current LLVM ThinLTO backend materializes a module containing
either:

* the three-argument, `i1`-returning `llvm.coro.end`; or
* the `i1`-returning `llvm.coro.end.async`.

Teach `AutoUpgrade` to recognize both legacy declarations and rebuild
their
calls with the current `void`-returning intrinsics. If the legacy result
is
used, replace it with `!llvm.coro.is_in_ramp()`, which preserves the old
`true in a resume function, false in the ramp function` behavior. Unused
results require no replacement.

The new assembler test covers used and unused results for both
synchronous
and async coroutine ends.

Tested with:

```console
$ cmake --build build --target opt FileCheck -j8
$ build/bin/opt -S llvm/test/Assembler/auto_upgrade_coro_end_result.ll | \
    build/bin/FileCheck llvm/test/Assembler/auto_upgrade_coro_end_result.ll
```
https://invent.kde.org/qt/clang/llvm/-/commit/725737bf88b8219d32e1723ceb653a0e706cc204

Git commit f8357566dde882ef967c7cf5383ecd2785e08859 by Oliver Hunt on 24/07/2026 at 04:01..
[clang][sema] Call expressions are constructed for undeduced deleted functions (#208488)

The deleted function path of overload resolution always constructed a CallExpr node
for the called function even if the function could not be deduced.
This case is handled in other paths by DiagnoseUseOfDecl which does perform that
test. The delete path cannot use that path though, as DiagnoseUseOfDecl rejects
deleted functions, and the entire point of this code is to permit the continued
evaluation of code even if the resolved function was deleted.

To fix this we now manually check for a complete type before continuing to construct
a potentially bogus CallExpr.
https://invent.kde.org/qt/clang/llvm/-/commit/f8357566dde882ef967c7cf5383ecd2785e08859