[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/jerryyin/amdgpu-isreallyaclobber-aa'. Changed from 0000000000000000000000000000000000000000 to 5023ca18471337d8977604002db3d6acb385b2e2 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 5023ca18471337d8977604002db3d6acb385b2e2 by Jerry Yin on 23/07/2026 at 15:09.. [AMDGPU] Consult AA for non-atomic clobbers in isReallyAClobber isReallyAClobber (used by AMDGPUAnnotateUniformValues to decide whether a uniform load may be marked !amdgpu.noclobber) only queried alias analysis for atomics; every other memory-writing MemoryDef (plain stores, memory intrinsics, calls) fell through to an unconditional "return true", declaring it a clobber without asking AA. As a result a uniform, read-only load is denied !amdgpu.noclobber whenever MemorySSA's clobber walk surfaces such a def through a loop MemoryPhi, even when AA can trivially prove NoAlias (e.g. an LDS/addrspace(3) write vs a global/addrspace(1) load). Without noclobber the load is selected as a vector GLOBAL_LOAD instead of a scalar s_load, adding a v_readfirstlane round-trip when the value feeds a scalar operand. Query AA generally via getModRefInfo for the fall-through case, while keeping the fence/barrier whitelist and the pointer-level atomic special case (getModRefInfo over-reports Mod for an atomic's ordering effects). The load's MemoryLocation is threaded through so addressing/size precision applies. https://invent.kde.org/qt/clang/llvm/-/commit/5023ca18471337d8977604002db3d6acb385b2e2