[Mlir-commits] [mlir] [MLIR][XeGPU] Introduce `xegpu::uArch` usage in target-sensitive passes (PR #163801)
Jianhui Li
llvmlistbot at llvm.org
Thu Oct 16 19:17:49 PDT 2025
================
@@ -557,23 +599,54 @@ void LayoutInfoPropagation::visitDpasOp(
ArrayRef<const LayoutInfoLattice *> results) {
VectorType aTy = dpas.getLhsType();
VectorType bTy = dpas.getRhsType();
- propagateIfChanged(
- operands[0], operands[0]->meet(getSIMTLayoutInfoForDPASOperand(aTy, 0)));
- propagateIfChanged(
- operands[1], operands[1]->meet(getSIMTLayoutInfoForDPASOperand(bTy, 1)));
+
+ auto uArch = getUArch(getChipStr(dpas).value_or(""));
+ const int subgroupSize = uArch->getSubgroupSize();
+ auto uArchInstruction =
+ std::static_pointer_cast<xegpu::uArch::DPASInstruction>(
+ uArch->getInstruction(xegpu::uArch::InstructionKind::DPAS));
+ const int maxALen =
+ uArchInstruction->getSupportedM(aTy.getElementType()).back();
+ const int maxBLen =
+ uArchInstruction->getSupportedK(bTy.getElementType()).back();
+ SmallVector<int> instDataA = {maxALen, subgroupSize};
----------------
Jianhui-Li wrote:
maxAlen and maxBlen need to compare with input operands' size since they need to be multiple of inst_data? It also applied to other places.
https://github.com/llvm/llvm-project/pull/163801
More information about the Mlir-commits
mailing list