Lost Performance: Analyzing and Fixing C-to-Rust Translation Regressions
In brief
- 20 C projects translated to Rust show slowdowns up to 62% on 12 of 19 operations.
- Nine recurring causes explain losses: residual work, missed optimizations, and lingering C patterns.
- An LLM tool automatically identifies and fixes 40 of 41 operations, 18 of which outperform the original C.
A study finds Rust projects translated from C suffer significant performance losses, up to 62%. Nine recurring causes are identified, and an LLM-based tool proposes targeted optimizations to fix them.
This summary gives you the essentials. The full article, its figures and quotes are on cs.AI updates on arXiv.org.
Read the original articleAI-generated summary of the source, checked by rules. Report an error