[qt/clang/llvm]: 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
Pushed by mirror-service into branch 'upstream/users/arsenm/nvptx-target-parser'.
Changed from 0000000000000000000000000000000000000000 to d036f0aaf636aad8aef2be53d08b136352a5f49b
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 ab993800519301853d4dfebcf4aa454d95938ee4 by GitHub (on behalf of AZero13) on 29/07/2026 at 05:17..
[X86] Fix redundant zeroing operations when casting ints to FP vectors (#212065)
https://invent.kde.org/qt/clang/llvm/-/commit/ab993800519301853d4dfebcf4aa454d95938ee4

Git commit 4e326b492aadea4b65f19b5581b0b3e52e8aaed3 by GitHub (on behalf of Fangrui Song) on 29/07/2026 at 05:18..
[BFI] Remove redundant getHeaderIndex lookup in adjustLoopHeaderMass. NFC (#212679)

getHeaderIndex(Loop.Nodes[H]) is H.
https://invent.kde.org/qt/clang/llvm/-/commit/4e326b492aadea4b65f19b5581b0b3e52e8aaed3

Git commit cf8b0ad96a57570695fba02013590939ffe36af9 by GitHub (on behalf of Anutosh Bhat) on 29/07/2026 at 05:24..
[WebAssembly] Fix v8i16-to-v8f32 uitofp cost (#212501)

I think there was a wrong duplication here. The WebAssembly SIMD
conversion cost table accidentally duplicated the
`UINT_TO_FP` entry for `v8i8` to `v8f32`. As a result, the unsigned
`v8i16` to `v8f32` conversion missed the target-specific table entry and
fell back to the generic cost of 5 instead of the intended cost of 10.

I've added ` llvm/test/Analysis/CostModel/WebAssembly/cast.ll` which I
think is good here as it would help test other casting errors in the
future too.
https://invent.kde.org/qt/clang/llvm/-/commit/cf8b0ad96a57570695fba02013590939ffe36af9

Git commit 40f95afe42db06e2f4226353039de96d66b5d18e by GitHub (on behalf of forking-google-bazel-bot[bot]) on 29/07/2026 at 06:11..
[Bazel] Fixes c2fa412 (#212688)

This fixes c2fa4128681863d92b2fe1615beb73e2ed62876f (#212353).

Buildkite error link:
https://buildkite.com/llvm-project/upstream-bazel/builds?commit=c2fa4128681863d92b2fe1615beb73e2ed62876f

Co-authored-by: Google Bazel Bot <[email protected]>
https://invent.kde.org/qt/clang/llvm/-/commit/40f95afe42db06e2f4226353039de96d66b5d18e

Git commit f4382bedc245a22ea7c354d08eb13543166a5f0d by GitHub (on behalf of dong jianqiang) on 29/07/2026 at 06:16..
[ARM] Exclude TLS symbols from the .reloc/R_ARM_REL32 path (#212549)

The .reloc branch in emitMachineConstantPoolValue fired for any
isWeakForLinker() + isDSOLocal() symbol, including TLS (thread_local)
weak symbols. R_ARM_REL32 is wrong for TLS: TLS symbols need
TLS-specific relocations (R_ARM_TLS_GD32 etc.). Using R_ARM_REL32 for a
TLS symbol produces a wrong address at runtime.

This broke the 2-stage ARM 32-bit buildbots: stage 1 (with the .reloc
branch) miscompiled stage 2's BPF codegen (BTFDebug.cpp references
llvm::sys::sandbox::Enabled, an inline thread_local weak variable),
causing a SIGSEGV in the BPF Assembly Printer.

Add a regression test (tls_weak_var in elf-preemption.ll) verifying that
TLS weak symbols get TLSGD/TPOFF, not R_ARM_REL32.

Fix #212545
https://invent.kde.org/qt/clang/llvm/-/commit/f4382bedc245a22ea7c354d08eb13543166a5f0d

Git commit ad300a7712f3506e702501097ddfe6b322cfa0fb by GitHub (on behalf of Marc Auberer) on 29/07/2026 at 06:34..
[IR] Remove deprecated InsertPosition(Instruction*) constructor (#212640)

This implicit constructor has been marked deprecated since almost 2
years in favor of constructing an InsertPosition from a
BasicBlock::iterator.
Remove it now that in-tree users no longer rely on it.

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

Git commit 9cdb4219e8edb617076a8c1a118cce119179e288 by GitHub (on behalf of lorenzo chelini) on 29/07/2026 at 06:34..
[MLIR] Validate directly parsed optional operand types (#212493)

Commit 6c51938067fa ([MLIR] Guard optional operand resolution in
generated op parsers) guarded resolution of every optional operand to
avoid indexing an empty inferred type range. The guard also skipped
resolveOperands when an optional operand was absent but an independently
optional type directive was present. This accepted malformed assembly
and silently discarded the orphan type when printing the operation.

Keep the guard for inferred type resolutions, which may access an empty
optional type vector, but always resolve directly parsed type ranges so
resolveOperands validates operand/type cardinality. Add coverage for
both valid forms and a type-only negative reproducer.
https://invent.kde.org/qt/clang/llvm/-/commit/9cdb4219e8edb617076a8c1a118cce119179e288

Git commit 52f6c88c2c1b6f0c10b9c8fb09ec35e147c593e3 by GitHub (on behalf of David Green) on 29/07/2026 at 06:40..
[Codegen] Replace any_of with is_contained. NFC (#212289)

A new operator== for SVT and EVT was apparently needed with reverse
operands.
https://invent.kde.org/qt/clang/llvm/-/commit/52f6c88c2c1b6f0c10b9c8fb09ec35e147c593e3

Git commit 3df3102da5c0ebb5d32a9146f6b0aec925bc4742 by GitHub (on behalf of Fangrui Song) on 29/07/2026 at 07:01..
[test] Migrate Hexagon/PowerPC thunk tests to the default thunk order (#212693)

Drop -z nosort-thunks (added by #211721 to keep creation order) and
update expectations to the default order: forward thunks sorted by
descending destination.
https://invent.kde.org/qt/clang/llvm/-/commit/3df3102da5c0ebb5d32a9146f6b0aec925bc4742

Git commit a7b2a20f01681186bb6872c077a52e22632db9ad by GitHub (on behalf of Timm Baeder) on 29/07/2026 at 07:03..
[clang] Improve diagnostics around constexpr limits (#212091)

1) Mention the limit in the "constexpr evaluation hit maximum step
limit" diagnostic as well
2) Move the "use -fconstexpr-steps" instruction to its own note so we
can reuse it for two different diagnostics

For
```c++
struct S {
  constexpr S() {}
};
constexpr S foo[1'500'000] = {};
```
we used to emit
```console
array.cpp:1028:13: error: constexpr variable 'foo' must be initialized by a constant expression
 1028 | constexpr S foo[1'500'000] = {};
      |             ^                ~~
array.cpp:1026:17: note: constexpr evaluation hit maximum step limit; possible infinite loop?
 1026 |   constexpr S() {}
      |                 ^
array.cpp:1028:31: note: in call to 'S()'
 1028 | constexpr S foo[1'500'000] = {};
      |                               ^
```

and now we emit
```console
array.cpp:1028:13: error: constexpr variable 'foo' must be initialized by a constant expression
 1028 | constexpr S foo[1'500'000] = {};
      |             ^                ~~
array.cpp:1026:17: note: constexpr evaluation hit maximum step limit of 1048576; possible infinite loop?
 1026 |   constexpr S() {}
      |                 ^
array.cpp:1028:31: note: in call to 'S()'
 1028 | constexpr S foo[1'500'000] = {};
      |                               ^
array.cpp:1026:17: note: use -fconstexpr-steps= to increase this limit (=0 will remove the limit)
 1026 |   constexpr S() {}
```
https://invent.kde.org/qt/clang/llvm/-/commit/a7b2a20f01681186bb6872c077a52e22632db9ad

Git commit 8c5193b41f2f1f5fb704a70e1f4bb7c0153d2d9d by GitHub (on behalf of Raul Tambre) on 29/07/2026 at 07:08..
[lldb][test] Use C++ frontend for building C++ test file (#212611)
https://invent.kde.org/qt/clang/llvm/-/commit/8c5193b41f2f1f5fb704a70e1f4bb7c0153d2d9d

Git commit d036f0aaf636aad8aef2be53d08b136352a5f49b by Matt Arsenault on 29/07/2026 at 10:48..
NVPTX: Add target names in TargetParser

Track the canonical sm name and other target information.
This will eventually be used to reduce the pain of maintaining
OffloadArch in clang; all of the dijoint targets share an
enum which makes target specific covered switches annoying.

Co-authored-by: Claude (Claude-Opus-4.8) <[email protected]>
https://invent.kde.org/qt/clang/llvm/-/commit/d036f0aaf636aad8aef2be53d08b136352a5f49b
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.