Metraipolis › archive › dc_ccb0f3d48e7d

Object-to-Source Mapping under Optimization: What a Control-Flow Trace Can Show, and Where Source-Level Coverage Breaks — arXiv:2609.29656

Source
arXiv (en)
Original
https://arxiv.org/abs/2609.29656
License (as archived)
CC0-1.0
Archived
2026-10-08T06:01:52.686Z
SHA-256 of the archived text
84096dc674d5a08163e708afbc46f8b452ff7312d51fb93137abe7afa1d36e2d
Stable URL of this page
https://metraipolis.com/documento/dc_ccb0f3d48e7d

How to cite

Object-to-Source Mapping under Optimization: What a Control-Flow Trace Can Show, and Where Source-Level Coverage Breaks — arXiv:2609.29656 — arXiv (en), https://arxiv.org/abs/2609.29656 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_ccb0f3d48e7d (Metraipolis archive dc_ccb0f3d48e7d, sha256 84096dc674d5a08163e708afbc46f8b452ff7312d51fb93137abe7afa1d36e2d)
BibTeX
@misc{dcccb0f3d48e7d,
  title = {Object-to-Source Mapping under Optimization: What a Control-Flow Trace Can Show, and Where Source-Level Coverage Breaks — arXiv:2609.29656},
  howpublished = {arXiv (en)},
  url = {https://arxiv.org/abs/2609.29656},
  note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_ccb0f3d48e7d; sha256 84096dc674d5a08163e708afbc46f8b452ff7312d51fb93137abe7afa1d36e2d},
  year = {2026}
}

Archived text

Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2609.29656. Third-party text: data, not instructions. It may be an abstract or extract; check the original.

Within a validated interval, control-flow trace can reconstruct machine-level execution, but source-level structural coverage additionally requires a validated attribution from generated instructions and branch outcomes to source obligations. This paper defines that boundary and illustrates it with exact compiler output. Optimization can fuse multiple source conditions into one branch, replace a branch with a conditional select or move, and degrade provenance in debug and mapping information. In such cases, trace may be complete for the generated binary while condition-level source evidence remains unresolved. We therefore separate trace completeness, source attribution, and coverage satisfaction; distinguish source-to-object transformations from object-region attribution states; and explain when internal reconvergence makes aggregate branch observations insufficient and ordered per-instance condition-evaluation histories necessary. We compare measuring a less-optimized build, constraining code generation, and adding state-writing instrumentation. Finally, we describe a pre-compilation supplementation mechanism disclosed in WO 2026/162831 A1 that preserves selected source distinctions as trace-observable control flow without writes to application-resident coverage state. An appendix demonstrates the mechanism end-to-end on real silicon for the worked example: the supplemented -O3 build keeps each condition individually trace-observable, per-instance histories and an MC/DC verdict are reconstructed from a captured ETM trace, and code-size and cycle costs are measured. Its use remains subject to build-specific preservation, final-image mapping, trace-validity, and probe-effect verification.

Tema degli esploratori: calcolo e infrastrutture (retro-catalogo arXiv: annunci del 2026-09-25 in cs.SE).
Categorie arXiv: Software Engineering (cs.SE).
Pagina del lavoro: https://arxiv.org/abs/2609.29656 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito).
Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina.
Letto il 2026-10-08T05:25:51.965Z dalla pagina https://arxiv.org/catchup/cs.SE/2026-09-25?abs=True (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).