[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/clang/amdgpu-fix-accepting-d16-sample-builtins-gfx6-gfx7'. Changed from 0000000000000000000000000000000000000000 to 95cecaf17475bf81f10cbea88dd5cd859cfb7c6c 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 4b6a8d81da1a9eb1cee48c318b156ef2f2645c94 by GitHub (on behalf of Matt Arsenault) on 03/08/2026 at 05:24.. AMDGPU: Migrate most llvm-objdump tests to use subarch triple (#213589) https://invent.kde.org/qt/clang/llvm/-/commit/4b6a8d81da1a9eb1cee48c318b156ef2f2645c94 Git commit 04ea62bc5e2c5596866de7ee6a9c3a8b6aa54d35 by GitHub (on behalf of Arseniy Obolenskiy) on 03/08/2026 at 05:25.. [AMDGPU] Fix miscompile trimming sparse DMask on image stores (#213586) Dropping a channel from a sparse DMask removes that write entirely It does not zero-fill like a contiguous trim does Only simplify stores when DMask is a contiguous prefix https://invent.kde.org/qt/clang/llvm/-/commit/04ea62bc5e2c5596866de7ee6a9c3a8b6aa54d35 Git commit 4f607e3cd911ccc3d1aab73129aacea97d864663 by GitHub (on behalf of Matt Arsenault) on 03/08/2026 at 05:42.. AMDGPU: Migrate misc. tests to subarch triples (#213593) https://invent.kde.org/qt/clang/llvm/-/commit/4f607e3cd911ccc3d1aab73129aacea97d864663 Git commit 278b9af90c6fd32776ad3f4f4b5eab87f52587e2 by GitHub (on behalf of Sam Elliott) on 03/08/2026 at 06:02.. [RISCV][MC] Emit Better Token Diagnostics (#209700) This implements an old FIXME in the AsmMatcherEmitter, which can now emit a token-specific match error diagnostic id, and potentially a token-specific error message to go along with the diagnostic id. For RISC-V, the overall effect is to have fewer "invalid operand for instruction" diagnostics and have more "expected '<TOKEN>'" diagnostics, which, with multiple near miss support, gives the user the location that token was expected (but not found). The rejig to the order of checks in `validateOperandClass` do not prevent backends from having custom operand kinds which can accept tokens, as was available before. The TableGen parts have been implemented in an opt-in way. --- This was implemented with the assistance of AI. https://invent.kde.org/qt/clang/llvm/-/commit/278b9af90c6fd32776ad3f4f4b5eab87f52587e2 Git commit 187c39ba03cfed96c8aab9d0c951d0bea6f27b82 by GitHub (on behalf of Abhinav Gaba) on 03/08/2026 at 06:07.. [OpenMP] Propagate ALWAYS/DELETE/CLOSE map-type modifiers to mapper entries (#210210) Per OpenMP, when a map/motion clause uses a mapper, any map-type-modifying modifier on that clause applies to each map the declared mapper specifies. This change propagates the `ALWAYS`, `DELETE`, and `CLOSE` bits from the outer clause's map type into every entry emitted by emitUserDefinedMapper, except `ATTACH` entries (`ATTACH`|`ALWAYS` is reserved for `attach(always)`, and the other bits have no meaning for an `ATTACH` entry). `PRESENT` is intentionally NOT propagated here: it requires distinguishing pointee entries from the struct's own storage and is handled in a follow-up. Co-authored-by: Claude Opus 4.8 <[email protected]> https://invent.kde.org/qt/clang/llvm/-/commit/187c39ba03cfed96c8aab9d0c951d0bea6f27b82 Git commit e2c8f57f00971712c1732b137a9afc539e38ff37 by GitHub (on behalf of Robert Imschweiler) on 03/08/2026 at 06:28.. [OpenMPOpt] Null generic-mode wrappers for SPMDized kernels (#207611) If a kernel gets SPMDized, it doesn't need the wrapper function that is passed to __kmpc_parallel_60. Keeping the dead wrapper function can lead to lots of misleading "local memory global used by non-kernel function" AMDGPU backend warnings. Let OpenMPOpt null the wrapper argument such that DCE can then remove the corresponding dead functions. Claude assisted with this patch. https://invent.kde.org/qt/clang/llvm/-/commit/e2c8f57f00971712c1732b137a9afc539e38ff37 Git commit 7f161cde5751ab5ab38a5e52119f9fe867844758 by GitHub (on behalf of Kareem Ergawy) on 03/08/2026 at 06:40.. [flang-rt] enable IsNamelistNameOrSlash lookahead for scalar namelist items (#211224) Resolves https://github.com/llvm/llvm-project/issues/211747 Problem ------- An empty NAMELIST assignment on a scalar item — e.g. `l =` in &nml l= i_count=7 r_value=2.72/ — aborted at runtime with fatal Fortran runtime error: Bad character 'i' in LOGICAL input field Every EditIntegerInput / EditRealInput / EditLogicalInput / EditCharacterInput function starts its list-directed arm with if (IsNamelistNameOrSlash(io)) return false; // no value which peeks ahead (via SavedPosition, no stream consumption) for a `<name>=` / `<name>%` / `<name>(` shape or one of the terminators `/` `&` `$`, letting the reader bail cleanly for empty values and short-array ends. That helper's first line is if (!listInput || !listInput->namelistGroup()) return false; InputNamelist however called ResetForNextNamelistItem with `useDescriptor->rank() > 0 ? &group : nullptr`, so `namelistGroup_` stayed null for scalars. The peek was silently disabled and the value reader consumed the next namelist item's name as a bare token, producing the abort above. Legacy nvfortran / gfortran accept empty scalar assignments as "keep current value". Solution -------- Pass `&group` unconditionally to `ResetForNextNamelistItem`. Today `IsNamelistNameOrSlash` uses `namelistGroup_` only as a boolean gate (never as a lookup table), so widening it is a no-op for arrays and enables the same empty-value / next-name detection for scalars. NamelistTests.NanInputAmbiguity (which motivated the original pointer form) still passes; three new tests cover the empty-scalar case, the empty-array case, and an empty scalar surrounded by arrays. Co-authored-by: Claude Opus 4.7 <[email protected]> https://invent.kde.org/qt/clang/llvm/-/commit/7f161cde5751ab5ab38a5e52119f9fe867844758 Git commit f7213d839614c3103f4be28a1459e7f12c44dc77 by GitHub (on behalf of Antonio Frighetto) on 03/08/2026 at 06:57.. [MemorySSA] Clarify `getClobberingMemoryAccess(MA, Loc)` overload does not accept MemoryUse (NFC) (#212512) Outdated comment has been updated to match the implementation, which asserts on MemoryUse. https://invent.kde.org/qt/clang/llvm/-/commit/f7213d839614c3103f4be28a1459e7f12c44dc77 Git commit f901de33ab614a7f13caa66ed966d3cd6bcb6eab by GitHub (on behalf of Antonio Frighetto) on 03/08/2026 at 06:58.. [GVNHoist] Use MemorySSA, drop MemoryDependenceAnalysis (NFCI) (#212773) Finalize MemorySSA usage in GVNHoist, while transitioning away from MemoryDependenceAnalysis. https://invent.kde.org/qt/clang/llvm/-/commit/f901de33ab614a7f13caa66ed966d3cd6bcb6eab Git commit 738029a68bd265cb4e65e03f63d84c027692adaa by GitHub (on behalf of Madhur Amilkanthwar) on 03/08/2026 at 06:58.. Enforce single-operand form for llvm.loop.vectorize metadata (#210932) This patch implements Phase 2 of the RFC "Enforce Single-Operand Format for All .enable Metadata Nodes". Please refer to RFC: https://discourse.llvm.org/t/rfc-enforce-single-operand-format-for-all-enable-metadata-nodes/90571/ The two-operand boolean form !{!"llvm.loop.vectorize.enable", i1 0/1} is replaced by a single-operand enable/disable pair: !{!"llvm.loop.vectorize.enable"} ; force vectorization !{!"llvm.loop.vectorize.disable"} ; suppress vectorization The Verifier rejects the two-operand form, AutoUpgrade rewrites old bitcode (including the legacy llvm.vectorizer.enable tag), and the readers and producers across LLVM, Clang, MLIR and Polly are updated. https://invent.kde.org/qt/clang/llvm/-/commit/738029a68bd265cb4e65e03f63d84c027692adaa Git commit a7cc9516751d6c5afe35da0628083879cb52f1c0 by GitHub (on behalf of Wenju He) on 03/08/2026 at 06:58.. [llvm-calc-occupancy] Fix title underline length (#213599) Fix error: invalid header length in 'CommandGuide/llvm-calc-occupancy.rst' (does not match length of title) in our downstream Sphinx doc build. https://invent.kde.org/qt/clang/llvm/-/commit/a7cc9516751d6c5afe35da0628083879cb52f1c0 Git commit dba8bec50d5b639991726d99134ab5a4b5c0f493 by Matt Arsenault on 03/08/2026 at 07:12.. clang/AMDGPU: Require 16-bit-insts for half typed buffer format builtins Typed buffer format load/store operations with 16-bit elements require d16 support which was introduced in gfx8. These builtins previously had no required features at all, so they were accepted (and then crashed the backend) on targets without 16-bit support. Diagnose these in Sema, parallel to the image builtins. The manual verification here suprised me. The automatic builtin feature verification is enforced in codegen, which seems like a layering violation which should be fixed. Co-Authored-By: Claude (Opus 4.8) <[email protected]> https://invent.kde.org/qt/clang/llvm/-/commit/dba8bec50d5b639991726d99134ab5a4b5c0f493 Git commit ed8cb5f4d0fbd1c2c3cbd9a391411ae6c4472668 by Matt Arsenault on 03/08/2026 at 07:12.. Use default feature check in codegen instead of sema https://invent.kde.org/qt/clang/llvm/-/commit/ed8cb5f4d0fbd1c2c3cbd9a391411ae6c4472668 Git commit cd7cb48b49571582a045f629c35a68604ff237ca by Matt Arsenault on 03/08/2026 at 07:12.. clang/AMDGPU: Require 16-bit-insts for half typed image builtins Typed image load/store operations with 16-bit elements require d16 support which was introduced in gfx8. They were previously gated only on image-insts, so they were wrongly accepted on targets that have images but lack 16-bit support (e.g. gfx700), where the backend then fails to select. Co-Authored-By: Claude (Opus 4.8) <[email protected]> https://invent.kde.org/qt/clang/llvm/-/commit/cd7cb48b49571582a045f629c35a68604ff237ca Git commit 95cecaf17475bf81f10cbea88dd5cd859cfb7c6c by Matt Arsenault on 03/08/2026 at 07:12.. clang/AMDGPU: Require 16-bit-insts for half typed image sample builtins Extend the d16 feature requirement to the half typed image sample builtins. The sample variants returning 16-bit elements require d16 support (gfx8+) but were gated only on image-insts/extended-image-insts, so they were wrongly accepted on old targets. Co-Authored-By: Claude (Opus 4.8) <[email protected]> https://invent.kde.org/qt/clang/llvm/-/commit/95cecaf17475bf81f10cbea88dd5cd859cfb7c6c