How do I install the Ir Debugging skill?

Run npx skillmds@latest add facebookexperimental/ir-debugging in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ir Debugging safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ir Debugging?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ir Debugging free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ir Debugging?

facebookexperimental (@facebookexperimental) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ir Debugging by facebookexperimental

Name: Ir Debugging
Author: facebookexperimental

Ir Debugging

Debug Triton compilation by dumping IR at each stage (TTIR, TTGIR, LLVM, PTX). Use when investigating compilation failures, kernel performance, register spills, or when user asks to inspect IR output. Covers TRITON_KERNEL_DUMP, MLIR_ENABLE_DUMP, LLVM_IR_ENABLE_DUMP, TRITON_DUMP_PTXAS_LOG, and related env vars.

File contents

IR Debugging

Environment variables

Env var	What it does
`TRITON_KERNEL_DUMP=1`	Dump IR at every compilation stage to `~/.triton/dump/`
`TRITON_PRINT_AUTOTUNING=1`	Use human-readable per-config subdirectories instead of hashes (combine with KERNEL_DUMP)
`TRITON_KERNEL_DUMP_BEST_CONFIG=1`	Dump IR only for the winning autotuned config (re-compiles with dumping, avoids noise)
`MLIR_ENABLE_DUMP=1`	Dump MLIR IR during pass execution (filter by kernel: `MLIR_ENABLE_DUMP=_kernel`)
`LLVM_IR_ENABLE_DUMP=1`	Dump LLVM IR (print-after-all)
`NVPTX_ENABLE_DUMP=1`	Dump NVPTX backend IR
`TRITON_DUMP_PTXAS_LOG=1`	Dump ptxas assembler logs (register usage, spills)
`TRITON_INTERPRET=1`	Run kernels in interpreter mode (no GPU needed)
`TRITON_ALWAYS_COMPILE=1`	Bypass cache, force recompilation
`TRITON_DUMP_TTGIR_TO_TLX=1`	Dump TTGIR back to TLX Python (reverse-engineer IR)

Decision tree: what are you debugging?

"Kernel produces wrong results" → TRITON_INTERPRET=1 to run on CPU, or TRITON_KERNEL_DUMP=1 to inspect IR at each stage
"Kernel is slow / register spills" → TRITON_DUMP_PTXAS_LOG=1 to check register usage and spills
"Which autotuned config won and why?" → TRITON_KERNEL_DUMP_BEST_CONFIG=1 TRITON_PRINT_AUTOTUNING=1
"Need to see MLIR passes" → MLIR_ENABLE_DUMP=1 (optionally filter: MLIR_ENABLE_DUMP=_my_kernel)
"Need to see final PTX/LLVM" → LLVM_IR_ENABLE_DUMP=1 and/or NVPTX_ENABLE_DUMP=1
"Cached result is stale" → TRITON_ALWAYS_COMPILE=1 to force recompilation

Common combos

# Full dump of best config with readable directory names
TRITON_KERNEL_DUMP_BEST_CONFIG=1 TRITON_PRINT_AUTOTUNING=1 python my_kernel.py

# Debug register pressure
TRITON_DUMP_PTXAS_LOG=1 TRITON_ALWAYS_COMPILE=1 python my_kernel.py

# Inspect MLIR passes for a specific kernel
MLIR_ENABLE_DUMP=_my_kernel TRITON_ALWAYS_COMPILE=1 python my_kernel.py

# Full IR pipeline dump
TRITON_KERNEL_DUMP=1 TRITON_ALWAYS_COMPILE=1 python my_kernel.py

Reference files

Full Python knobs: python/triton/knobs.py
C++ env vars: include/triton/Tools/Sys/GetEnv.hpp

---name: ir-debuggingdescription: Debug Triton compilation by dumping IR at each stage (TTIR, TTGIR, LLVM, PTX). Use when investigating compilation failures, kernel performance, register spills, or when user asks to inspect IR output. Covers TRITON_KERNEL_DUMP, MLIR_ENABLE_DUMP, LLVM_IR_ENABLE_DUMP, TRITON_DUMP_PTXAS_LOG, and related env vars.---# IR Debugging## Environment variables| Env var | What it does ||---|---|| `TRITON_KERNEL_DUMP=1` | Dump IR at every compilation stage to `~/.triton/dump/` || `TRITON_PRINT_AUTOTUNING=1` | Use human-readable per-config subdirectories instead of hashes (combine with KERNEL_DUMP) || `TRITON_KERNEL_DUMP_BEST_CONFIG=1` | Dump IR only for the winning autotuned config (re-compiles with dumping, avoids noise) || `MLIR_ENABLE_DUMP=1` | Dump MLIR IR during pass execution (filter by kernel: `MLIR_ENABLE_DUMP=_kernel`) || `LLVM_IR_ENABLE_DUMP=1` | Dump LLVM IR (print-after-all) || `NVPTX_ENABLE_DUMP=1` | Dump NVPTX backend IR || `TRITON_DUMP_PTXAS_LOG=1` | Dump ptxas assembler logs (register usage, spills) || `TRITON_INTERPRET=1` | Run kernels in interpreter mode (no GPU needed) || `TRITON_ALWAYS_COMPILE=1` | Bypass cache, force recompilation || `TRITON_DUMP_TTGIR_TO_TLX=1` | Dump TTGIR back to TLX Python (reverse-engineer IR) |## Decision tree: what are you debugging?- **"Kernel produces wrong results"** → `TRITON_INTERPRET=1` to run on CPU, or `TRITON_KERNEL_DUMP=1` to inspect IR at each stage- **"Kernel is slow / register spills"** → `TRITON_DUMP_PTXAS_LOG=1` to check register usage and spills- **"Which autotuned config won and why?"** → `TRITON_KERNEL_DUMP_BEST_CONFIG=1 TRITON_PRINT_AUTOTUNING=1`- **"Need to see MLIR passes"** → `MLIR_ENABLE_DUMP=1` (optionally filter: `MLIR_ENABLE_DUMP=_my_kernel`)- **"Need to see final PTX/LLVM"** → `LLVM_IR_ENABLE_DUMP=1` and/or `NVPTX_ENABLE_DUMP=1`- **"Cached result is stale"** → `TRITON_ALWAYS_COMPILE=1` to force recompilation## Common combos```bash# Full dump of best config with readable directory namesTRITON_KERNEL_DUMP_BEST_CONFIG=1 TRITON_PRINT_AUTOTUNING=1 python my_kernel.py# Debug register pressureTRITON_DUMP_PTXAS_LOG=1 TRITON_ALWAYS_COMPILE=1 python my_kernel.py# Inspect MLIR passes for a specific kernelMLIR_ENABLE_DUMP=_my_kernel TRITON_ALWAYS_COMPILE=1 python my_kernel.py# Full IR pipeline dumpTRITON_KERNEL_DUMP=1 TRITON_ALWAYS_COMPILE=1 python my_kernel.py```## Reference files- Full Python knobs: `python/triton/knobs.py`- C++ env vars: `include/triton/Tools/Sys/GetEnv.hpp`

Frequently asked questions