Everything published about KDA so far had been on NVIDIA hardware, with excellent documentation, a mature profiler and a large public corpus of prior kernels. That is a reasonable place to start and a bad place to stop, because it leaves the obvious objection open: perhaps the agent is retrieving, not reasoning.
So we pointed it at hardware with much less to retrieve: AMD's MI350X (gfx950), through FlyDSL, AMD's Python kernel language, driven by rocm-KDA-pilot. Two of its pull requests are merged.
Opened to merged
Swipe the plot sideways to see all of it →
#685: send each shape to the faster kernel
FlyDSL has two attention forward kernels on gfx950: a software-pipelined one that wins on long sequences, and a generic one that wins on very short ones. The old rule picked between them by sequence length alone. #685 makes the rule batch-aware, because the pipeline's fixed cost is paid back over batch × sequence length. The shapes it re-routes get faster:
#711: a correct fp8 attention forward
#711 adds an fp8 (e4m3fn) forward to the pipelined kernel, with three operand-precision modes. All three pass the fp8 accuracy gate, and the existing bf16 and fp16 paths are byte-identical.
It does not reach the hand-written assembly. The pull request says so: a further 19 rounds of profile-driven tuning did not beat the default path, which is held back by register-limited occupancy, not by compute.
- TFLOPS
Swipe the diagram sideways to see all of it →
1/0 The agent writes a FlyDSL kernel with little prior code to copy.
This is the property that decides whether any of this lasts. New accelerators arrive with no corpus at all. A loop that works only where the answers already exist on the internet is a search engine with extra steps. A loop that works on thin documentation, and says plainly where it stopped, is a method.