loci-post-edit

To measure energy and timing impact, you can diff pre-edit and post-edit artifacts to extract per-function assembly and CFG data, then run an MCP timing service to produce timing and energy deltas for modified functions.

Yes, analyzing control flow graph changes is supported by extracting per-function CFG data from modified and added functions, providing a unified post-edit report even when hardware timing data is unavailable.

Generating per-function timing and energy deltas requires access to pre-edit and post-edit object files, an MCP-backed timing service, and the ability to generate assembly and CFG data for the modified functions.

If the MCP timing service is unavailable, the post-edit analysis handles the missing data gracefully by degrading to CFG-only analysis, still extracting and reporting control flow graph impacts for the modified functions.

Post-edit analysis identifies functions to evaluate by diffing pre-edit and post-edit artifacts to detect exactly which functions were modified or added, then isolating their assembly and CFG data for timing and energy measurement.

Getting a unified report of assembly, CFG, and timing deltas is the core function of post-edit analysis, combining extracted hardware traces and control flow data into a single document quantifying the impact of code changes.