Bringing Existing Open-Source Code into MISRA Compliance
summary
Retrofitting MISRA to large open‑source codebases (Xen, Zephyr) proves feasible but costly: toolable tailoring of rule 10.1 and rule 16.3 plus targeted macros cuts noisy violations dramatically (Xen reports about a 97% reduction on some branches), finds real bugs, and enables CI gates that block regressions. Key concrete moves are Kconfig + qualified compiler use instead of wholesale preprocessor elimination, documented global deviations (deviations published in the Xen repo), maintainer training, and funded engineering (AMD support).
AI-written summary · about
chapters (7)
- 0:00MISRA introduction
- 2:59Open-source in safety systems
- 12:54Adopted vs existing code
- 16:51Tailoring MISRA guidelines
- 19:24Xen hypervisor case study
- 34:06Lessons from compliance
- 41:10Q&A
related talks
01h 02mA Critical Look at the Coding Standards Landscape
44mCoding Guidelines – to Comply or Not Comply – Some Myth Busting
48mDeveloping Open-Source Software RTOS with Functional Safety in Mind
27mContinuous Compliance: Agile Practices for Software Compliance
27mInfiltrating a Code Base: Moving Toward a Better C
47mPrepping your Open Source Project for Multi-Platform
01h 02mProgram Manipulation of C Code
21mDriving Innovation: Evolving the Role of Software in the RISC-V Ecosystem Beyond...