aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/CodeGen/CodeGenModule.cpp
diff options
context:
space:
mode:
authorAlex Bradbury <asb@igalia.com>2023-12-05 21:26:56 +0000
committerGitHub <noreply@github.com>2023-12-05 21:26:56 +0000
commitd6fbd96e5eaf3e8acbf1b43dce7a311352907567 (patch)
tree149aa0d218dac030955e12d2dff80665f3bd39da /clang/lib/CodeGen/CodeGenModule.cpp
parent0f45e45847a5f2969b8021c787a566531fc96473 (diff)
downloadllvm-d6fbd96e5eaf3e8acbf1b43dce7a311352907567.zip
llvm-d6fbd96e5eaf3e8acbf1b43dce7a311352907567.tar.gz
llvm-d6fbd96e5eaf3e8acbf1b43dce7a311352907567.tar.bz2
[RISCV] Support FrameIndex operands in getMemOperandsWithOffsetWidth / getMemOperandWithOffsetWidth (#73802)
I noted AArch64 happily accepts a FrameIndex operand as well as a register. This doesn't cause any changes outside of my C++ unit test for the current state of in-tree, but this will cause additional test changes if #73789 is rebased on top of it. Note that the returned Offset doesn't seem at all as meaningful if you have a FrameIndex base, though the approach taken here follows AArch64 (see D54847). This change won't harm the approach taken in shouldClusterMemOps because memOpsHaveSameBasePtr will only return true if the FrameIndex operand is the same for both operations.
Diffstat (limited to 'clang/lib/CodeGen/CodeGenModule.cpp')
0 files changed, 0 insertions, 0 deletions