🤖 AI Summary
Despite Rust’s safety guarantees, rustc suffers from defects rooted in language-specific mechanisms—such as advanced traits, lifetime annotations, and unstable features—yet no systematic empirical study has characterized their root causes. Method: We conducted a large-scale manual root-cause analysis of 301 Rust-specific bugs reported between 2022 and 2024. We designed a Rust-semantics-aware defect taxonomy, mapped each bug to compiler phases (e.g., HIR, MIR), and evaluated the effectiveness of existing testing tools in detecting non-crashing semantic errors. Contribution/Results: Our study is the first empirical investigation revealing that over 70% of these defects originate in type checking and lifetime validation logic. We further find that current testing infrastructure exhibits significantly low detection rates for semantic errors—particularly those involving trait resolution and borrow-checker misbehavior. These findings provide reproducible, evidence-based guidance for improving rustc’s reliability and for designing targeted, semantics-aware test generation strategies.
📝 Abstract
Rust is gaining popularity for its well-known memory safety guarantees and high performance, distinguishing it from C/C++ and JVM-based languages. Its compiler, rustc, enforces these guarantees through specialized mechanisms such as trait solving, borrow checking, and specific optimizations. However, Rust's unique language mechanisms introduce complexity to its compiler, leading to Rust-specific compiler bugs that are less common in traditional compilers. With Rust's increasing adoption in safety-critical domains, understanding these language mechanisms and their impact on compiler bugs is essential for improving the reliability of both rustc and Rust programs. Yet, we still lack a large-scale, detailed, and in-depth study of Rust-specific bugs in rustc. To bridge this gap, this work conducts a comprehensive and systematic study of Rust-specific bugs in rustc, with a particular focus on the components that support its unique language features. Our analysis examines issues and fixes reported between 2022 and 2024, with a manual review of 301 valid issues. We categorize these bugs based on their causes, symptoms, affected compilation stages, and test case characteristics. Additionally, we evaluate existing rustc testing tools to assess their effectiveness and limitations. Our key findings include: (1) rustc bugs primarily arise from Rust's type system and lifetime model, with frequent errors in the High-Level Intermediate Representation (HIR) and Mid-Level Intermediate Representation (MIR) modules due to complex checkers and optimizations; (2) bug-revealing test cases often involve unstable features, advanced trait usages, lifetime annotations, standard APIs, and specific optimization levels; (3) while both valid and invalid programs can trigger bugs, existing testing tools struggle to detect non-crash errors, underscoring the need for further advancements in rustc testing.