Following the docs, we need at least 5 wait states between an EXEC write
and an instruction that uses DPP.
Details
Details
Diff Detail
Diff Detail
- Repository
- rL LLVM
Event Timeline
test/CodeGen/AMDGPU/inserted-wait-states.mir | ||
---|---|---|
495 ↗ | (On Diff #104793) | Should check the NOP argument is 0. Ideally these would be combined into one nop with the right value later. Also why not use VI-NEXT for all of them? |
test/CodeGen/AMDGPU/inserted-wait-states.mir | ||
---|---|---|
495 ↗ | (On Diff #104793) | Sure, I can check that it's 0. Btw, the rest of this file is inconsistent about whether it checks for a 0 argument or not. I didn't use VI-NEXT to be consistent with the rest of the file which doesn't either, but I can change that too. And yeah, all these NOP's are combined into one by a later pass; I don't remember exactly which one. |
Comment Actions
- Check for correct S_NOP argument and use VI-NEXT
- Only check for VALU EXEC write as per the docs, and update test