This property was intended to indicate when RISCVAsmPrinter should
drop the tied source operand when converting to MCInst. Using it
in RISCVDAGToDAGISel distorts what it intended for.
This should remove some changes from D151850.
Differential D152039
[RISCV] Remove uses of RISCVII::hasMergeOp from RISCVDAGToDAGISel.cpp craig.topper on Jun 2 2023, 3:22 PM. Authored by
Details This property was intended to indicate when RISCVAsmPrinter should This should remove some changes from D151850.
Diff Detail
Event TimelineComment Actions Should we introduce a separate hasTiedDest utility? (With possibly a better chosen name?) I think having that might help clarify the difference between the check being performed here and the hasMergeOp routine. I have to admit I'm not completely following your semantic difference, so having a place to explain that in comments might help. Comment Actions Maybe the name hasMergeOp is the problem because the documentation did say what it meant. // Does this instruction have a merge operand that must be removed when // converting to MCInst. It will be the first explicit use operand. Used by // RVV Pseudos. HasMergeOpShift = ForceTailAgnosticShift + 1, HasMergeOpMask = 1 << HasMergeOpShift, I think I can remove it from RISCVMCInstLowering too so the distinction won't matter soon. |
clang-format not found in user’s local PATH; not linting file.