ir-override-ablation

name	ir-override-ablation
description	Design and run Triton TTGIR debugging ablations using ir_override. Use when reducing a provided or dumped TTGIR, trying user-provided or agent-generated ablation/oblation ideas, updating a test harness around ir_override, or preserving a compile/runtime failure while simplifying IR to expose a fundamental compiler or lowering gap.

IR Override Ablation

Use this skill to turn a noisy TTGIR reproducer into a smaller, evidence-backed set of IR variants. The goal is not only to simplify the IR; it is to preserve the debugging signal and keep the test oracle honest when edits intentionally change kernel semantics.

Setup

1. Identify the target signal before editing:
   • compile failure, pass assertion, crash, hang, wrong result, or diagnostic
   • the exact command and environment that reproduces it
   • the minimum architecture requirement, for example sm90 or sm100
2. Get a baseline TTGIR:
   • Use the provided .ttgir directly when available.
   • Otherwise dump it with:

     TRITON_ALWAYS_COMPILE=1 TRITON_KERNEL_DUMP=1 TRITON_DUMP_DIR=<dump_dir> <run_command>
     

3. Decide the override mechanism:
   • Prefer triton.Config(..., ir_override="<variant.ttgir>") when the harness already uses configs/autotune or can be cheaply adapted.
   • Use TRITON_KERNEL_OVERRIDE=1 TRITON_OVERRIDE_DIR=<dump_dir> when testing against the dumped override directory layout is simpler.

Ablation Loop

1. Build or accept a list of ideas. Each idea should state the hypothesis and the expected effect on the target signal.
2. Copy the baseline TTGIR to a named variant file before editing.
3. Classify the test oracle before running the variant: