MISRA C and C++ in OSS: Yes, We Can!
summary
MISRA C/C++ gets applied to large open‑source stacks using a three‑step program of training, tailoring, tooling. Projects reported: Xen drops from >1,000,000 violations to ~2,000 on x86_64 and <1,000 on arm64, Zephyr falls from >1,000,000 to <10,000, and 120 MISRA guidelines are upstream‑accepted for Xen. Compliance is checked in CI with ECLAIR static analyzer and regressions blocked; where static fixes are impractical, sanitizers run test suites to catch overflows.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:27Advantages and challenges of C and C++
- 3:37Undefined behaviors in C/C++
- 10:22C/C++ lack of full definition
- 15:07Embedded C/C++ readability issues
- 19:05MISRA C/C++ standards overview
- 27:07MISRA compliance for OSS
- 30:00Case studies: XEN, Zephyr, Trusted Firmware, Linux
- 35:01MISRA compliance strategies for OSS
- 38:56Conclusion: MISRA in OSS feasibility
- 40:02Q&A: MISRA for Rust and others
- 41:28Q&A: MISRA for libraries
- 44:36Q&A: MISRA tooling
- 46:24Q&A: Open source MISRA tools
- 47:32Q&A: Bugs found in MISRA work
- 48:15Q&A: Sanitizers vs static analysis
related talks
52mBringing Existing Open-Source Code into MISRA Compliance
01h 02mA Critical Look at the Coding Standards Landscape
01h 20mSafer C++: MISRA-C++ : 202X Rules and Beyond
57mMISRA C++202x: It ain't your grandpa's MISRA any more
46mSafety-Certifying Open Source Software: The Case of the Xen Hypervisor
45mSafety Certifying an Open Source Project: The Example of Xen
40mBOF: Open Source Projects in Safety Critical Applications
52mOSS Security Maturity: Time to Put on Your Big Boy Pants!