aboutsummaryrefslogtreecommitdiff
path: root/llvm/docs/CommandGuide
diff options
context:
space:
mode:
authorBenjamin Kramer <benny.kra@googlemail.com>2022-07-19 12:35:47 +0200
committerBenjamin Kramer <benny.kra@googlemail.com>2022-07-19 13:13:55 +0200
commit8aff88fd3a5f6f974f4ce62923981764fafbb820 (patch)
tree4b7b74d12e627ffa1b34d2612b2dcffbdce358ec /llvm/docs/CommandGuide
parent6cb9529001ba8677751862a9e969315182b7094d (diff)
downloadllvm-8aff88fd3a5f6f974f4ce62923981764fafbb820.zip
llvm-8aff88fd3a5f6f974f4ce62923981764fafbb820.tar.gz
llvm-8aff88fd3a5f6f974f4ce62923981764fafbb820.tar.bz2
[LegalizeDAG] Propagate alignment in ExpandExtractFromVectorThroughStack
Unlike the name suggests this can reuse any store as a base for a memory-based vector extract. If that store is underaligned the loads created to extract will have an invalid alignment. Since most CPUs are forgiving wrt alignment this is almost never an issue, on x86 this is only reproducible by extracting a 128 bit vector out of a wider vector. I tried making a test case in the context of https://reviews.llvm.org/D127982 but it's really really fragile, as the output pretty much looks like a missed optimization.
Diffstat (limited to 'llvm/docs/CommandGuide')
0 files changed, 0 insertions, 0 deletions