[llvm] [AMDGPU] Account for existing SDWA selections (PR #123221)

[Frederik Harwath via llvm-commits]

================
@@ -108,6 +111,42 @@ class SDWAOperand {
   MachineOperand *getReplacedOperand() const { return Replaced; }
   MachineInstr *getParentInst() const { return Target->getParent(); }
 
+  /// Combine an SDWA instruction's existing SDWA selection \p
+  /// ExistingSel with the SDWA selection \p OpSel of its operand. If
+  /// the selections are compatible, return the combined selection,
+  /// otherwise return a nullopt. For example, if we have ExistingSel
+  /// = BYTE_0 Sel and FoldedSel WORD_1 Sel:
+  ///     BYTE_0 Sel (WORD_1 Sel (%X)) -> BYTE_2 Sel (%X)
+  std::optional<SdwaSel> combineSdwaSel(SdwaSel ExistingSel,
----------------
frederik-h wrote:

> I think that implementation doesn't really have any benefit over the current proposed one.
> 
> But in `potentialToConvert` , why can't we blacklist the bad combos of the current operands sdwa sel and the corresponding sdwa sel of useMI if it is sdwa?
> 

I did not really see how it would fit in exactly at this place. But I have now changed the way in which `matchSDWAOperand` creates the SDWAOperand instances to incorporate the selection compatibility check. This seems like the earliest possible place to handle this. 

https://github.com/llvm/llvm-project/pull/123221