Safety compliance of Rust libraries
summary
Describes a reproducible path to qualify Rust core for ISO26262 by generating structural coverage: adds a --coverage bootstrap flag to build a profiler runtime that removes the cyclic dependency via profiler_builtins without core, compiles with LLVM C-instrumentation, collects .prof data at runtime and produces reports with grcov + llvm-cov. Statement coverage is already generated, branch coverage sits in a draft PR, and MCDC work is started; demo of the flow runs successfully.
AI-written summary · about
chapters (10)
- 0:00Safety compliance in Rust
- 1:45Automotive safety compliance
- 3:11ISO 26262 requirements
- 5:20Documenting Rust core requirements
- 8:06Code coverage types and standards
- 10:24Rust coverage tools and flow
- 17:28Coverage challenges in Rust core
- 22:33Demo: Rust coverage generation
- 24:42Rust core library status
- 26:09Q&A
related talks
31mValidating Rust for industry: Certification meets formal analysis
32mBuilding and Maintaining Rust at Scale
56mRust for Foundation Software
26mFerrocene - qualifying the Rust compiler using a fully open source tool stack
32mrustc in userland
56mRust for Safe and Scalable Automotive: Insights from
36mInching ever closer to the Rust standard library with gccrs
28mC2Rust: Migrating Legacy Code to Rust