What problem does it solve?
Converting cuTile GPU kernels (@ct.kernel) into Triton (@triton.jit) safely and efficiently is error-prone, especially when correctness breaks or performance regresses due to incorrect TMA usage, dtype handling, or layout-specific logic.
Core Features & Use Cases
- Deterministic conversion workflow with gates: enforces an analyze → convert → validate → test → benchmark sequence with explicit stop conditions before perf sign-off.
- cuTile → Triton API translation guidance: maps common constructs (ct.load/store, ct.mma, ct.Constant, indexing, and ct.launch) to Triton equivalents, including host-side launch syntax.
- Mandatory performance-critical TMA conversion: prevents 5–20× regressions by requiring TMA tensor descriptors for any 2D+ block-shaped tile loads/stores.
- Advanced handling for attention/GQA/Gemma-style kernels: applies a mandatory optimization strategy checklist (not just “TMA first”), including dual-kernel layout flags like transpose/transposes_v patterns.
Quick Start
Convert your cuTile kernel file to a Triton @triton.jit implementation by following the phase-gated workflow (analyze → convert → validate → test → benchmark) in translations/workflow.md, making sure every 2D+ tile load/store uses tl.make_tensor_descriptor TMA.