Measuring the Checker: Mutation Analysis for GPU-Kernel Benchmark Oracles
Not on the map. Why?
Abstract (arXiv)
Benchmarks for LLM-generated GPU kernels decide correctness with a few random inputs and a loose floating-point tolerance, and their verdicts now feed leaderboards and reinforcement-learning rewards. Recent work agrees these checkers are weak and patches them by hand---extra input distributions, fuzzing recipes, tighter tolerances---with no way to measure whether any patch suffices. We introduce mutation analysis as an adequacy metric for kernel-benchmark oracles: deterministic rules inject 10,303 compilable faults into verified CUDA implementations of 188 KernelBench problems, 7,384 of them with an independent kill witness; any test protocol is scored by the fraction it detects. The official check misses one in six witnessed faults (16.9%), deterministically, and the misses are skewed by family: 8.7% of arithmetic faults escape, but 78.6% of precision faults do. The metric explains why (a tolerance blind band growing with reduction size; a measured ceiling on input aggressiveness set by legitimate floating-point variance), audits the strongest existing patch (KernelBench-Verified's gain splits into +4.0 points from hidden inputs and +4.5 from tighter tolerance, a split its authors could not compute), and exposes a published fuzzing recipe that rejects correct kernels 107 times. Optimizing suites over the kill matrix reaches 98.0% detection with two inputs per problem (94.8% held-out), and the measurement's fault taxonomy teaches a test generator more than the raw faults themselves. Across 48 whole architectures, the blindness grows with scale, concentrating in deep homogeneous pipelines, and two problems prove unrefereeable: their official references violate the benchmark's own tolerance against fp64. We release everything as hrefhttps://huggingface.co/datasets/Elfsong/KernelBench-MKernelBench-M.
Key facts. No citing papers in the map yet (data through 14 Oct 2026). Builds on 13 of its 29 references that are in the map. First posted on arXiv 2 Sep 2026.
Builds on
13 of 29 references.
References · 13
- 2023Is Your Code Generated by ChatGPT Really Correct? Rigorous Evaluation of Large Language Models for Code Generationcited by 1,391
- 2025KernelBench: Can LLMs Write Efficient GPU Kernels?cited by 225
- 2025Kevin: Multi-Turn RL for Generating CUDA Kernelscited by 78
- 2025TritonBench: Benchmarking Large Language Model Capabilities for Generating Triton Operatorscited by 75
- 2024Evaluating Language Models for Efficient Code Generationcited by 73
- 2025Towards Robust Agentic CUDA Kernel Benchmarking, Verification, and Optimizationcited by 56
- 2022NNSmith: Generating Diverse and Valid Test Cases for Deep Learning Compilerscited by 30
- 2025Mutation-Guided LLM-based Test Generation at Metacited by 25
- 2024Impacts of floating-point non-associativity on reproducibility for HPC and deep learning applicationscited by 24
- 2026KernelBench-Verified: Do LLM-Generated Kernels Actually Beat PyTorch?cited by 8
- 2026The Correctness Illusion in LLM-Generated GPU Kernelscited by 6
- 2026Probe to Generate: Program Variant-Guided Test Augmentation for Repository-Level Repair Benchmarkscited by 3
1 more
Built on by
Not cited yet.