Rust for Morello: Always-On Memory Safety, Even in Unsafe Code

1 Introduction 2 Background 2.1 Rust 2.1.1 Move and Drop 2.1.2 References and lifetimes 2.1.3 unsafe 2.2 The Rust Compiler 2.3 Capability hardware 2.3.1 Morello prototype 3 Adjustments to the Rust compiler and standard library 3.1 Rust semantics open question: usize 3.2 Target specification 3.3 Constant evaluation 3.4 Pointer code generation 3.5 Tweaks to LLVM 3.6 MPSC 3.7 FFI types 4 Performance analysis methodology 4.1 Test hardware 4.2 Operating system 4.3 Disabling bounds checking 4.4 cargo bench 4.5 Line counts 4.6 Test suites 5 Results 5.1 The cost of software bounds checking 5.2 The cost of hardware bounds checking 5.3 Benchmarks 5.4 Validity of results 5.4.1 Prototype hardware 5.4.2 Choice of benchmark suite 6 Related Work 6.1 Rust and type-safe systems programming 6.2 Prior work porting Rust to CHERI 6.3 Bounds checking 7 Future work 8 Conclusions A Test suite