diff options
author | Alexandros Lamprineas <alexandros.lamprineas@arm.com> | 2023-10-31 15:01:28 +0000 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-10-31 15:01:28 +0000 |
commit | 7d21d7395ccc8613e5a4144a1b9735e5c719cda3 (patch) | |
tree | a905ff4629da8939f3974aad1f1feb9d9c0ce5b7 /clang/lib/ExtractAPI/DeclarationFragments.cpp | |
parent | 34362c6ec6635a22910d5dce339b0934c799ebf6 (diff) | |
download | llvm-7d21d7395ccc8613e5a4144a1b9735e5c719cda3.zip llvm-7d21d7395ccc8613e5a4144a1b9735e5c719cda3.tar.gz llvm-7d21d7395ccc8613e5a4144a1b9735e5c719cda3.tar.bz2 |
[LAA] Add a test case to show incorrect dependency classification (NFC). (#70473)
Currently the loop access analysis classifies this loop as unsafe to
vectorize because the memory dependencies are
'ForwardButPreventsForwarding'. However, the access pattern is
'write-after-read' with no subsequent read accessing the written memory
locations. I can't see how store-to-load forwarding is applicable here.
void vectorizable_Read_Write(int *A) {
for (unsigned i = 1022; i >= 0; i--)
A[i+1] = A[i] + 1;
}
Diffstat (limited to 'clang/lib/ExtractAPI/DeclarationFragments.cpp')
0 files changed, 0 insertions, 0 deletions