This patch mainly reorganising the logic in ValidateMVEInst because it was a bit difficult to follow... The important change is that we now clear the CurrentPredicate when we find an instruction which would completely overwrite the VPR. This fix essentially means we're back to not really being able to handle VPT instructions when tail predicating.
Details
Diff Detail
Unit Tests
Event Timeline
I understood there is a NFC and non-NFC part of this patch. Is worth separating this out?
llvm/lib/Target/ARM/ARMInstrVFP.td | ||
---|---|---|
2849 | High-level question: is this worth to create a separate patch for this? Because we are adding MVEDomain, is this easily tested with assembly/disassembly tests? | |
2867 | This is redundant and we can just use the predicate on line 2848? | |
llvm/lib/Target/ARM/ARMLowOverheadLoops.cpp | ||
857 | Can you clarify here if the "this means" applies more to the second point above, or to both? | |
859 | a large VPT -> a large VPT block? | |
862 | each the predication -> each predicate? | |
886 | mve -> MVE | |
904 | Beginning -> Beginning of? | |
915 | Perhaps just a nit about the message, but we are not really creating new VPT blocks here? | |
927 | Move this where it is used. |
Cheers, I will definitely commit an NFC and rebase. I've extracted the validForTailPredication into another patch too: D87753.
Thanks for that. There was a lot going on before, but this now looks like a small, nice change.
High-level question: is this worth to create a separate patch for this? Because we are adding MVEDomain, is this easily tested with assembly/disassembly tests?