Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
llvm/lib/Target/RISCV/RISCVFrameLowering.cpp | ||
---|---|---|
528 | I think this might still add unflagged instructions. Not sure what is the best way to flag them (I imagine we could traverse MBBI to the end of the MBB and invoke setFlag). |
llvm/lib/Target/RISCV/RISCVFrameLowering.cpp | ||
---|---|---|
528 |
Oh no, that wouldn't work. Please ignore me. |
llvm/lib/Target/RISCV/RISCVFrameLowering.cpp | ||
---|---|---|
528 | Yeah, there is no way to distinguish the caller of copyPhysReg() comes from prologue/epilogue or not. |
llvm/lib/Target/RISCV/RISCVFrameLowering.cpp | ||
---|---|---|
528 | Can we just use BuildMI? We're not getting much from copyPhysReg here are we? It's just an ADDI with 0, I think. |
llvm/lib/Target/RISCV/RISCVFrameLowering.cpp | ||
---|---|---|
320 | This should be an explicit argument rather than inferred | |
528 | Downstream we'd have to add an if to use a capability move instruction for CHERI-RISC-V rather than getting to reuse the implementation in copyPhysReg, but that's hardly a huge burden. Ideally copyPhysReg would take an MIFlag but that's annoying to go and propagate everywhere just to avoid that. |
This looks good to me, though it would be good to get a quick LGTM from someone who works more actively with the RVV code (e.g. Craig, Roger, or Fraser).
I think this one shouldn't be labeled as '[NFC]' as it will impact e.g. debug info generation.
This should be an explicit argument rather than inferred