aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/CodeGen/BasicBlockSections.cpp
diff options
context:
space:
mode:
authorPhilip Reames <preames@rivosinc.com>2022-05-26 15:24:41 -0700
committerPhilip Reames <listmail@philipreames.com>2022-05-26 15:25:47 -0700
commit8a3b6ba7569e80782dbd1893902bd6134bd6ff01 (patch)
tree3c81636789d53aa866363cfbb31edb3900425ddc /llvm/lib/CodeGen/BasicBlockSections.cpp
parentc09cd64e5c6dea6e97ef7d6cee5f689df2b408d7 (diff)
downloadllvm-8a3b6ba7569e80782dbd1893902bd6134bd6ff01.zip
llvm-8a3b6ba7569e80782dbd1893902bd6134bd6ff01.tar.gz
llvm-8a3b6ba7569e80782dbd1893902bd6134bd6ff01.tar.bz2
[RISCV] Add a subtarget feature to enable unaligned scalar loads and stores
A RISCV implementation can choose to implement unaligned load/store support. We currently don't have a way for such a processor to indicate a preference for unaligned load/stores, so add a subtarget feature. There doesn't appear to be a formal extension for unaligned support. The RISCV Profiles (https://github.com/riscv/riscv-profiles/blob/main/profiles.adoc#rva20u64-profile) docs use the name Zicclsm, but a) that doesn't appear to actually been standardized, and b) isn't quite what we want here anyway due to the perf comment. Instead, we can follow precedent from other backends and have a feature flag for the existence of misaligned load/stores with sufficient performance that user code should actually use them. Differential Revision: https://reviews.llvm.org/D126085
Diffstat (limited to 'llvm/lib/CodeGen/BasicBlockSections.cpp')
0 files changed, 0 insertions, 0 deletions