Evidence-guided method improves debugging of hardware code failures
Evidence-Guided Repository-Level RTL Repair
Hardware Architecture
Summary
Fixing bugs in hardware descriptions can be tricky because the problem might spread over multiple files and moments in time. The authors created a new way that uses actual failure data to pinpoint where things go wrong and then carefully checks that the fix truly solves the problem across the entire hardware design. Their approach uses evidence from hardware run simulations to guide the repair process more accurately than methods that only look at the code. Tests showed their method worked better on a known benchmark.
What this means in practice
- •For hardware verification engineers: Automatically locate and fix complex hardware design bugs that span multiple files and clock cycles using failure evidence from simulations.
- •For embedded systems developers: Ensure that fixes in hardware description languages propagate correctly and do not introduce new faults during design iterations.
Authors
Yuxin Du, Juxin Niu, Zhe Jiang, Nan Guan
Abstract
Repository-level RTL repair must localize a failure that spans files, modules, and clock cycles, then propagate the fix consistently. Existing methods reason over source code, which reveals possible behaviors but not the failed execution, and cannot tell whether a local fix was propagated consistently. We therefore present an evidence-guided framework with three modules. Failure grounding converts a problem statement into a reproduced failing run and a failure anchor. Waveform-guided localization uses a localization toolbox to narrow the observed violation into a candidate mechanism and an evidence trail. Consistency-aware repair and validation then expand that seed into a coordinated patch and replay the same scenario to check that the violation disappears. We conducted experiments on HWE-Bench and achieved better performance than the baseline.