MISRA C:2012 Directives and Rules

Polyspace can check your code against the MISRA C:2012 coding rules and some directives. The subgroups listed map to the different subsets outlined in the MISRA C:2012 guidelines. Use the Check MISRA C:2012 (-misra3) analysis option to activate subsets of the rules. When MISRA C:2012 guidelines are violated, Polyspace provides messages with information about the violated rule or directive. Most violations are found during the compile phase of an analysis.

Each guideline is categorized into one of these categories: mandatory, required, or advisory. When you set up rule checking, you can select subsets of these categories to check. For automatically generated code, some rules change categories, including to one additional category: readability. The Use generated code requirements (-misra3-agc-mode) option activates the categorization for automatically generated code.

There are additional subsets of MISRA™ C:2012 guidelines defined by Polyspace called Software Quality Objectives (SQO) that can have a direct or indirect impact on the precision of your results. When you set up code checking, you can select these subsets. See Software Quality Objective Subsets for MISRA Coding Standards. To check Polyspace coverage of MISRA C:2012, see Polyspace Support for Coding Standards.

If you use a specific version of the C language such as C11 or C17/C18, specify the C version for a more accurate check for MISRA C:2012 violation. See C standard version (-c-version).