Sign inGet started
Paper · arXiv

Test-Input Generation for Tensor Programs: What Actually Finds Kernel Bugs

Test-input generation for tensor kernels is folkloric. Most projects pick a representative shape and dtype, run a fixed-shape allclose-style check, and ship. We make the choices explicit and measure them. Using the gpuemu op-schema-aware seeded fuzzer (arXiv:2606.20128), we evaluate seven test-generation strategies across a 26-op corpus (16 correct controls and 10 LLM-style buggy variants seeded with documented transcription patterns) on an RTX 3060 GPU instance. Strategies vary the shape candidate set, the dtype mix, and the input value distribution. We report each strategy on two axes: bug recall and control false-positive (FP) rate. Boundary-only shape sampling is the operationally saf...

AuthorsDipankar Sarkar
Primary categorycs.SE
Published23 June 2026
Last updated at source21 July 2026
cs.SEcs.LG
Embed this entry
<iframe src="https://silytics.si/embed/item/fb414242-5bf0-4d2f-92ca-b6ed0015de93" width="420" height="190" style="border:0" loading="lazy" title="Silytics entry"></iframe>

Free, no tracking. More about feeds and embeds.

Silytics shows public metadata from arXiv and links to the original. Information may be incomplete or out of date. Last refreshed 17 October 2026. Licenses and terms of the original apply to the work itself. Not financial, legal or professional advice.