aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Commands/CommandObjectFrame.cpp
diff options
context:
space:
mode:
authorMichael Maitland <michaeltmaitland@gmail.com>2023-07-05 10:04:06 -0700
committerMichael Maitland <michaeltmaitland@gmail.com>2023-07-06 15:12:08 -0700
commitecf372f993fa0f1ae417a3159e5c397f36c2d48c (patch)
tree5e5b5c0af06b1aec6b8f5c082c7f826a1e51ca72 /lldb/source/Commands/CommandObjectFrame.cpp
parentaef6d4610fabf2b4c2f9e2fcfab24fce6f59cc86 (diff)
downloadllvm-ecf372f993fa0f1ae417a3159e5c397f36c2d48c.zip
llvm-ecf372f993fa0f1ae417a3159e5c397f36c2d48c.tar.gz
llvm-ecf372f993fa0f1ae417a3159e5c397f36c2d48c.tar.bz2
[llvm-mca][RISCV] vsetivli and vsetvli act as instruments
Since the LMUL data that is needed to create an instrument is avaliable statically from vsetivli and vsetvli instructions, LMUL instruments can be automatically generated so that clients of the tool do no need to manually insert instrument comments. Instrument comments may be placed after a vset{i}vli instruction, which will override instrument that was automatically inserted. As a result, clients of llvm-mca instruments do not need to update their existing instrument comments. However, if the instrument has the same LMUL as the vset{i}vli, then it is reccomended to remove the instrument comment as it becomes redundant. Differential Revision: https://reviews.llvm.org/D154526
Diffstat (limited to 'lldb/source/Commands/CommandObjectFrame.cpp')
0 files changed, 0 insertions, 0 deletions