Misra Parallelism Safety-critical Guidelines for C++11, 17, Then C++20, 23
summary
Group work documents a concrete, tool-focused effort: a phase‑one spreadsheet of ~81 candidate rules, 18 accepted and 20 deferred toward MISRA NEXT for C++11/14/17 with eyes on C++20/23. Rules are classified by decidability categories (human vs tool, local vs whole‑program), examples include mutex adapters, std::call_once and lock‑order graphs, and AUTOSAR async/future patterns. Outputs are machine‑checkable rules, directive rules, and recommendations for static analysis and intent attributes.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 0:50Why do we need it
- 2:35Standards
- 4:15Standard Comparison
- 5:25Most Important Guidelines
- 6:35Type Resource Safety
- 8:18What is still missing
- 9:57History
- 10:55Decidability
- 13:02Where should parallel concurrency rules go
- 14:16Categories of parallel concurrency rules
- 16:28Use case 3 13
- 22:10Use case 3 15
- 26:34Why concurrency
- 31:09Concurrency
- 33:25Adaptive Autozone
- 37:29Sharing Data
- 41:53Conclusion
- 43:38Where are we
- 48:15Summary
- 49:20Questions
- 53:47Verb Verbals
related talks
57mThe Misra C++:2023 Guidelines
01h 20mSafer C++: MISRA-C++ : 202X Rules and Beyond
01h 05mSafer C++ with MISRA-C++ 2023
01h 29mC++ Safety And Security Panel 2024
53mFrom Chaos to Control: Overcoming C and C++’s Inherent Unsafety
01h 02mHow to deal with static analysis findings: MISRA
49mC++ (Core) Guidelines - Safer C++
01h 35mSafety and Security for C++: Panel Discussion