TMUL

Instruction Diagram

Introduction

Performs element-wise multiplication of two tiles.

Mathematical Semantics

For each element (i, j) in the valid region:

dsti,j=src0i,j⋅src1i,j\mathrm{dst}_{i,j} = \mathrm{src0}_{i,j} \cdot \mathrm{src1}_{i,j}

Assembly Syntax

Synchronous form:

%dst = tmul %src0, %src1 : !pto.tile<...>

AS Level 1 (SSA)

%dst = pto.tmul %src0, %src1 : (!pto.tile<...>, !pto.tile<...>) -> !pto.tile<...>

AS Level 2 (DPS)

pto.tmul ins(%src0, %src1 : !pto.tile_buf<...>, !pto.tile_buf<...>) outs(%dst : !pto.tile_buf<...>)

C++ Built-in APIs

Declared in include/pto/common/pto_instr.hpp:

The public include header is <pto/pto-inst.hpp>, and the internal declaration is located in pto/common/pto_instr.hpp.

template <typename TileDataDst, typename TileDataSrc0, typename TileDataSrc1, typename... WaitEvents>
PTO_INST RecordEvent TMUL(TileDataDst &dst, TileDataSrc0 &src0, TileDataSrc1 &src1, WaitEvents&&... events);

Constraints

  • Implementation check (Atlas A2/A3 training products/Atlas A2/A3 inference products):
    • TileData::DType must be one of the following: int32_t, int16_t, half, float.
    • The tile position must be a vector (TileData::Loc == TileType::Vec).
    • Static valid boundary: TileData::ValidRow <= TileData::Rows and TileData::ValidCol <= TileData::Cols.
    • The tile layout must be row-major (TileData::isRowMajor).
    • Runtime: the src0, src1, and dst tiles should have the same validRow/validCol.
  • Implementation check (Ascend 950PR/Ascend 950DT):
    • TileData::DType must be one of the following: int32_t, uint32_t, float, int16_t, uint16_t, half, bfloat16.
    • The tile position must be a vector (TileData::Loc == TileType::Vec).
    • Static valid boundary: TileData::ValidRow <= TileData::Rows and TileData::ValidCol <= TileData::Cols.
    • The tile layout must be row-major (TileData::isRowMajor).
    • Runtime: the src0, src1, and dst tiles must have the same validRow/validCol.
  • Valid region:
    • This operation uses dst.GetValidRow()/dst.GetValidCol() as the iteration domain.

Examples

Automatic

#include <pto/pto-inst.hpp>

using namespace pto;

void example_auto() {
  using TileT = Tile<TileType::Vec, float, 16, 16>;
  TileT src0, src1, dst;
  TMUL(dst, src0, src1);
}

Manual

#include <pto/pto-inst.hpp>

using namespace pto;

void example_manual() {
  using TileT = Tile<TileType::Vec, float, 16, 16>;
  TileT src0, src1, dst;
  TASSIGN(src0, 0x1000);
  TASSIGN(src1, 0x2000);
  TASSIGN(dst,  0x3000);
  TMUL(dst, src0, src1);
}

ASM Examples

Automatic Mode

# Automatic mode: the compiler/runtime handles resource placement and scheduling.
%dst = pto.tmul %src0, %src1 : (!pto.tile<...>, !pto.tile<...>) -> !pto.tile<...>

Manual Mode

# Manual mode: explicitly bind resources first, then issue the instruction.
# Optional (when the instruction contains tile operands):
# pto.tassign %arg0, @tile(0x1000)
# pto.tassign %arg1, @tile(0x2000)
%dst = pto.tmul %src0, %src1 : (!pto.tile<...>, !pto.tile<...>) -> !pto.tile<...>

PTO Assembly Form

%dst = tmul %src0, %src1 : !pto.tile<...>
# AS Level 2 (DPS)
pto.tmul ins(%src0, %src1 : !pto.tile_buf<...>, !pto.tile_buf<...>) outs(%dst : !pto.tile_buf<...>)