aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Commands/CommandObjectProcess.cpp
diff options
context:
space:
mode:
authorPhilip Reames <preames@rivosinc.com>2023-11-27 08:33:03 -0800
committerGitHub <noreply@github.com>2023-11-27 08:33:03 -0800
commit129440728ce3e688969ed253a6709a5d50c5e850 (patch)
tree57e816f2053938c7621cc99094ced167ad64e0eb /lldb/source/Commands/CommandObjectProcess.cpp
parentdd09221a29506031415cad8a1308998358633d48 (diff)
downloadllvm-129440728ce3e688969ed253a6709a5d50c5e850.zip
llvm-129440728ce3e688969ed253a6709a5d50c5e850.tar.gz
llvm-129440728ce3e688969ed253a6709a5d50c5e850.tar.bz2
[RISCV] Partially move doPeepholeMaskedRVV into RISCVFoldMasks (#72441)
This change is motived by a point of confusion on https://github.com/llvm/llvm-project/pull/71764. I hadn't fully understood why doPeepholeMaskedRVV needed to be part of the same change. As indicated in the fixme in this patch, the reason is that performCombineVMergeAndVOps doesn't know how to deal with the true side of the merge being a all-ones masked instruction. This change removes one of two calls to the routine in RISCVISELDAGToDAG, and adds a clarifying comment on the precondition for the remaining call. The post-ISEL code is tested by the cases where we can form a unmasked instruction after folding the vmerge back into true. I don't really care if we actually land this patch, or leave it roled into https://github.com/llvm/llvm-project/pull/71764. I'm posting it mostly to clarify the confusion.
Diffstat (limited to 'lldb/source/Commands/CommandObjectProcess.cpp')
0 files changed, 0 insertions, 0 deletions