AI & ML
Validating Concurrent Correctness Witnesses with Ghosts by Thread-Modular Abstract Interpretation
arXiv cs.SE0 views
arXiv:2611.23792v1 Announce Type: cross Abstract: Concurrent programs are notoriously difficult to write and to reason about, and even tools based on sound theoretical foundations can produce incorrect results due to implementation bugs. Correctness witnesses have been proposed as a way to increase the confidence in the verdicts of software verifiers by enabling independent validation. Recently, correctness witnesses have been extended to the concurrent setting, by introducing ghost variables to allow encoding more expressive invariants. While different approaches to producing witnesses with ghosts exist, validation techniques are still lacking; instead of leveraging the information encoded in the ghosts to guide the validation process, validators merely treat ghost instrumentation and invariants over ghost variables as additional proof obligations. We propose a novel framework for the validation of concurrent correctness witnesses that exploits the semantic information encoded in ghost variables. It combines a checking phase, which establishes the semantic content of the ghost instrumentation, with an exploitation phase making use of this information. Both phases are formulated as thread-modular abstract interpretation. In particular, we consider two different classes of ghost variables and techniques for exploiting them, one based on resource invariants and one based on phases. Phase ghosts guide the degree to which the abstract interpretation considers interleavings instead of always abstracting them coarsely. In this way, the abstract interpreter can validate witnesses containing invariants beyond the reach of unguided thread-modular analysis, while still retaining its scalability benefits. We have implemented our framework in a static analyzer and evaluate it on witnesses encoding resource invariants obtained from a state-of-the-art software verifier, as well as on hand-crafted witnesses encoding phase information.
Source:https://arxiv.org/abs/2611.23792PreviousEvaluating Governed LLM-Driven ML Experimentation: Lifecycle, Provenance, and Failure MetricsNextAsking but Missing: Decision Coverage in Natural-Language Data Querying
Related posts
Fuzzy name matching for sanctions screening: normalisation, transliteration and Jaro-Winkler
0dev.to
The Claude Architect Professional exam changes on 7 December - Here is what's different
0dev.to
SEO Isn't Enough Anymore. Meet GEO.
0dev.to

Prompt Engineering vs. Context Engineering vs. Harness Engineering: What’s the Difference?
0dev.to
P_SAPEA Exam Practice Questions: The Comparisons That Decide SAP Enterprise Architect Scenarios
0dev.to
Olala 7A1B says 8 GB, but the BF16 file is 13.59 GB: what a 1B-active hybrid MoE needs to run
0dev.to