Qualification of the C and C++ Standard Libraries for Safety-critical Applications
summary
Explains how the C/C++ library is turned into labeled, testable requirements mapped to tests and reports to meet ISO 26262; delivers a commercial requirements-based suite called SuperGuard for C that includes test specs, traceability and evidence. Requires MC/DC coverage for ASIL D and highlights tooling gaps: compile-time constexpr/header code issues break coverage metrics, so additional analysis or tool improvements are needed. Work in progress targets a C++ subset with a first release expected next year.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:16About Solid Sands
- 1:08Compiler Testing
- 2:39Compiler Qualification
- 5:45Specification of the strncpy function
- 8:20Testable requirements for strncpy
- 10:41C++ Standard Library Qualification
- 12:20Code coverage in C++
- 15:14SuperGuard
related talks
01h 35mWriting a Base Level Library for Safety Critical Code in C++
01h 29mWhat Does It Take to Implement the C++ Standard Library?
01h 28mKeynote: Safety, Security, Safety and C / C++ - C++ Evolution
57mHow To Implement the C++ Standard Library - (Part 1 of 2)
01h 31mWhat C++ Needs to be Safe
45mThe existential threat against C++ and where to go from here
43mC++ and Security: Can We Do Better?
50mWhen Human Life Depends on Software - Introduction to Safety-Critical Systems