Skip to content
hw.dev
hw.dev/signal/zomboss-agentic-kernel-gen-compiler-boundary-2026
SignalarXiv

Zomboss Puts Agentic Kernel Generation Inside a Verified Compiler Boundary, Gets 3.34x Speedup on Gemmini

A compiler-verified boundary makes LLM-generated kernels for custom AI accelerators provably correct, collapsing the per-workload expert cost that every new chip currently requires.

#ai-hardware#tools#verification
Read Original

Agentic kernel generation for emerging AI accelerators keeps failing because agents re-derive the same machine semantics on every workload: instruction behavior, legality constraints, synchronization rules. Zomboss compiles those semantics once into a reusable mapping interface, then uses a neural agent to search workload-dependent mapping decisions inside that verified boundary.

On Gemmini, Zomboss returns correct kernels on all 20 tested instances, 3.34x geometric-mean speedup over the compiler default, and 71.2% fewer inference tokens than direct agentic generation. On PLENA (36 instances), correctness also holds at 100%. Direct agentic generation fails on some instances because an agent can generate a kernel that looks right and runs wrong. Zomboss cannot produce that failure mode: the compiler makes illegal states unreachable before the agent reaches them.

Custom accelerators (Gemmini, university designs, startup chips without mature LLVM backends) have been caught between expert-written kernels per workload and LLM-generated kernels that fail late. Both are expensive at scale. A verified compiler boundary changes the economics: legality is a one-time cost absorbed by the compiler, not a per-workload risk absorbed by the engineering team.

Teams shipping custom AI accelerators in 2026 should benchmark on workload coverage rate, not correctness rate. Zomboss answers correctness. At 71.2% fewer tokens per kernel, the remaining question is how many workloads fit the generation budget before product launch.