diff options
author | Sirish Pande <sirpande@amd.com> | 2025-04-28 14:02:18 -0500 |
---|---|---|
committer | GitHub <noreply@github.com> | 2025-04-28 14:02:18 -0500 |
commit | abec9ff47da4fd8b614d0338203b2e3663c36aaf (patch) | |
tree | 28d0533d114d343b5dabd8568b43df679706309f /clang/lib/Frontend/InitPreprocessor.cpp | |
parent | 043b04acff53f3c3b2dd0d6eeb8c2127a229ac72 (diff) | |
download | llvm-abec9ff47da4fd8b614d0338203b2e3663c36aaf.zip llvm-abec9ff47da4fd8b614d0338203b2e3663c36aaf.tar.gz llvm-abec9ff47da4fd8b614d0338203b2e3663c36aaf.tar.bz2 |
[AMDGPU] Correctly merge noalias scopes during lowering of LDS data. (#131664)
Currently, if there is already noalias metadata present on loads and
stores, lower module lds pass is generating a more conservative aliasing
set. This results in inhibiting scheduling intrinsics that would have
otherwise generated a better pipelined instruction.
The fix is not to always intersect already existing noalias metadata
with noalias created for lowering of LDS. But to intersect only if
noalias scopes are from the same domain, otherwise concatenate exising
noalias sets with LDS noalias.
There a few patches that have come for scopedAA in the past. Following
three should be enough background information.
https://reviews.llvm.org/D91576
https://reviews.llvm.org/D108315
https://reviews.llvm.org/D110049
Essentially, after a pass that might change aliasing info, one should
check if that pass results in change number of MayAlias or ModRef using
the following:
`opt -S -aa-pipeline=basic-aa,scoped-noalias-aa -passes=aa-eval
-evaluate-aa-metadata -print-all-alias-modref-info -disable-output`
Diffstat (limited to 'clang/lib/Frontend/InitPreprocessor.cpp')
0 files changed, 0 insertions, 0 deletions