Home

Motivation

No more excuses for not checking your embedded projects against the MISRA rules.

Intended Workflow

This project should/could be used in the following way:

• Compiling the project using Clang with all MISRA-checking warnings (listed in this wiki) and -Werror enabled
• Running clang-tidy with all our MISRA checkers enabled

With very little effort this can be implemented in your CI setup.

Progress

The documents linked below describe if and how each rule can be checked.

Explanation for the "Supported by" column:

• TBD: "To Be Determined" - Rule has not yet been looked at at all
• unchecked: Rule can not yet be checked at all
• unchecked (document): Unchecked and likely uncheckable by a compiler
• -W...: Enforceable by enabling this option when invoking the compiler
• clang-tidy: ...: Checkable by the vanilla clang-tidy checker
• clang-tidy-misra: Checker developed by us is able to check this rule

Links:

• MISRA C++:2008
• MISRA C:2012