aboutsummaryrefslogtreecommitdiff
path: root/clang/unittests/libclang/LibclangTest.cpp
diff options
context:
space:
mode:
authorBjorn Pettersson <bjorn.a.pettersson@ericsson.com>2023-06-07 17:44:37 +0200
committerBjorn Pettersson <bjorn.a.pettersson@ericsson.com>2023-06-09 15:33:35 +0200
commit263bc7f905c7f354cb80403c0b2754cf8880d1b7 (patch)
treec38c91299003c6ee3dd08f6e14ed069c358e4136 /clang/unittests/libclang/LibclangTest.cpp
parent5acac7db6e71db66d87987eaf5c91315d73ca086 (diff)
downloadllvm-263bc7f905c7f354cb80403c0b2754cf8880d1b7.zip
llvm-263bc7f905c7f354cb80403c0b2754cf8880d1b7.tar.gz
llvm-263bc7f905c7f354cb80403c0b2754cf8880d1b7.tar.bz2
[LoadStoreVectorizer] Only upgrade align for alloca
In commit 2be0abb7fe72ed453 (D149893) the load store vectorized was reimplemented. One thing that can happen with the new LSV is that it can increase the align of alloca and global objects. However, the code comments indicate that the intention only was to increase alignment of alloca. Now we will use stripPointerCasts to analyse if the load/store really is accessing an alloca (same as getOrEnforceKnownAlignment is using). And then we only try to change the align if we find an alloca instruction. This way the code will match better with code comments, and we won't change alignment of non-stack variables to use the "StackAdjustedAlignment". Differential Revision: https://reviews.llvm.org/D152386
Diffstat (limited to 'clang/unittests/libclang/LibclangTest.cpp')
0 files changed, 0 insertions, 0 deletions