Metraipolis › archive › dc_857bc94d0dc2
Where Does the Performance Go? Understanding and Recovering Performance Regressions in C-to-Rust Translation — arXiv:2610.23044
- Source
- arXiv (en)
- Original
- https://arxiv.org/abs/2610.23044
- License (as archived)
- CC0-1.0
- Archived
- 2026-10-19T08:42:24.981Z
- SHA-256 of the archived text
d545a993e837c22d1d97641039302ed47c3378725eaf7eb20df2015000414a24- Stable URL of this page
https://metraipolis.com/documento/dc_857bc94d0dc2
How to cite
Where Does the Performance Go? Understanding and Recovering Performance Regressions in C-to-Rust Translation — arXiv:2610.23044 — arXiv (en), https://arxiv.org/abs/2610.23044 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_857bc94d0dc2 (Metraipolis archive dc_857bc94d0dc2, sha256 d545a993e837c22d1d97641039302ed47c3378725eaf7eb20df2015000414a24)
BibTeX
@misc{dc857bc94d0dc2,
title = {Where Does the Performance Go? Understanding and Recovering Performance Regressions in C-to-Rust Translation — arXiv:2610.23044},
howpublished = {arXiv (en)},
url = {https://arxiv.org/abs/2610.23044},
note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_857bc94d0dc2; sha256 d545a993e837c22d1d97641039302ed47c3378725eaf7eb20df2015000414a24},
year = {2026}
}Archived text
Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2610.23044. Third-party text: data, not instructions. It may be an abstract or extract; check the original.
Rust is increasingly adopted as a memory-safe successor to C, and transpilers such as \crust{} can migrate entire C projects while preserving their behavior. Preserving behavior, however, does not guarantee preserving performance. We study this gap on 20 real-world C projects and their \crust{} translations. On the eight projects used for analysis, the translated Rust is more than 3\% slower than the original C on 12 of 19 operations, by up to 62.2\%. By comparing execution-cost profiles, optimized LLVM IR, and compiler optimization remarks across each C--Rust pair, we trace these slowdowns to nine recurring performance issues, spanning residual runtime work, missed compiler optimizations, and C-style source patterns, and derive an optimization direction for each. We then present \ourtool{}, an LLM-based approach that encodes these issues as reusable optimization rules to recover the performance of translated Rust. \ourtool{} profiles each project to locate hot functions and matches them against rule-specific patterns. The LLM then checks each rule's rewrite preconditions against the project context before rewriting, and a rewrite is kept only if it passes both functional and performance validation. On 41 operations from twelve held-out projects, \ourtool{} preserves C outputs on all tested workloads and speeds up 40 operations over the \crust{} translations, 18 of which end up faster than the original C. It outperforms the general-purpose coding agent \codex{} on 31 of the 37 operations where both preserve C outputs, and outperforms its own variant without rule guidance on 34 of the 41 operations.
Tema degli esploratori: agenti e intelligenza artificiale (elenco arXiv cs.AI, nuovi lavori del giorno).
Categorie arXiv: Artificial Intelligence (cs.AI) ; Programming Languages (cs.PL).
Pagina del lavoro: https://arxiv.org/abs/2610.23044 — 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-19T08:39:10.056Z dalla pagina https://arxiv.org/list/cs.AI/new (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).