Backend
ProCerDCL: Query-Efficient Black-Box Probabilistic Verification of Deep Learning Compiler Optimization
arXiv cs.SE0 views
arXiv:2610.36499v1 Announce Type: new Abstract: We present \tool, a query-efficient framework for black-box probabilistic verification. Given a fixed, sampleable input distribution and a binary property oracle, \tool assesses the property's violation probability $p$ against a threshold $\theta$. Under independent sampling and stateless oracle behavior, acceptance asserts $p\le\theta$, rejection asserts $p>\theta+\eta$ for a user-specified separation margin, and an inconclusive verdict indicates insufficient evidence for either conclusion. The probability of each type of erroneous verdict is bounded by its specified error budget. To support this three-valued contract efficiently, \tool uses a single sequential test, eliminating the interval family required by the baseline. The test accounts for repeated sampling checks through either corrected exact binomial confidence intervals or an anytime-valid confidence sequence. We apply \tool to probabilistic local model semantic consistency, where the property oracle detects decision-level inconsistencies between reference and compiled executions under a specified perturbation distribution. Our evaluation covers 24 tasks across TorchInductor and TensorRT and examines sampling efficiency, conclusiveness, and diagnostic behavior. For sampling efficiency, we use paired one-model clean-label radius searches: the baseline requires 3.6-4.2 times as many unique samples under matched numerical parameters while providing a weaker decision contract. For model semantic consistency, checks at $\theta=10^{-3}$ yield 817 acceptances, 19 inconclusive verdicts, and 4 rejections across 840 input--backend instances from 21 tasks. Case studies of two documented compiler faults further demonstrate what these local verdicts can diagnose.
Source:https://arxiv.org/abs/2610.36499PreviousWhen AI Can Build It, What Should We Assess? Rethinking Evidence of Engineering CompetenceNextFrom Ripple to Boundary: Deterministic Impact Boundaries for LLM-Based Software Evolution
Related posts
I used to dream about coding on the train. Now I'm managing agents from my phone. 🚉🍁🍂
0dev.to Productivity
Streamlining GitHub Activity: Why Lost Filters Impact Software Engineering Measurement
0dev.to Productivity

The Roofline Model for LLM Inference
0dev.to Machine Learning
Deduplicate Your RAG Corpus Without Losing Its Citations
0dev.to Machine Learning

scm2cpp-learn: 44 scikit-learn estimators, same results, up to ~1000x faster
0dev.to Machine Learning
Marvell is buying Lumentum for $115B: what the optical bet means for AI cluster power, and what a fixed 4.5x exchange ratio really locks in
0dev.to Machine Learning