arXiv (All)
open access
Object-to-Source Mapping under Optimization: What a Control-Flow Trace Can Show, and Where Source-Level Coverage Breaks
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
Conceptio Open Archive
Analyze & explore related research in Conceptio
Connect this record directly into your research workflow or AI agent. Explore citations across open repositories, query full text, and export structured proof bundles.
This document is indexed with metadata only: full text is not available in the archive for this record. Open the official source ↗
Related documents
- RunAgent: Interpreting Natural-Language Plans with Constraint-Guided Execution#151716
- Safe and Scalable Data Integration Using LLMs for Schema Harmonization and Rule Synthesis#80147
- Why Do LLMs Fail at OCL Generation? A Graph Reasoning Perspective#1062025
- Towards Behavior Tree-Guided Vulnerability Detection with Lightweight LLMs#632795
- Beyond Fixed Fault Models: Comparing LLM-Based and Rule-Based Fault Injection in OpenStack#668102
Record · ID 1077584
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Bring this data into your agent: Connect via MCP or API · 20 free credits to start · no card required
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive