aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Commands/CommandObjectMemory.cpp
diff options
context:
space:
mode:
authorPhilip Reames <preames@rivosinc.com>2025-03-05 08:56:09 -0800
committerGitHub <noreply@github.com>2025-03-05 08:56:09 -0800
commit6e749f597f7bcea8de80e78d0161f4efc2c14ded (patch)
tree1673211811f79723489197c21bb1963dfe0cf38f /lldb/source/Commands/CommandObjectMemory.cpp
parentf39e81e4db9276f13bc3066be6bf27c55f958b7e (diff)
downloadllvm-6e749f597f7bcea8de80e78d0161f4efc2c14ded.zip
llvm-6e749f597f7bcea8de80e78d0161f4efc2c14ded.tar.gz
llvm-6e749f597f7bcea8de80e78d0161f4efc2c14ded.tar.bz2
[RISCV] Adjust RISCVVectorMaskDAGMutation to look for copy to V0 (#129296)
This mutation was introduced in 01a15dca0 with the goal of avoiding many copies from V1-v31 to v0 immediately before a mask consuming instruction. I noticed in a workload that this was not applying to vmv.s.x (which we use for short vector masks). We'd had a whitelist of instructions. Instead, we can directly inspect the user of the current node to see if it's a copy to V0. This isn't quite precise (as the mask producing instruction could already be scheduled fairly far from it's single use), but is probably good enough. As with all schedule changes, results are mixed. Some significant improvements, some regressions.
Diffstat (limited to 'lldb/source/Commands/CommandObjectMemory.cpp')
0 files changed, 0 insertions, 0 deletions