Check MISRA C:2012 (`-misra3`)

(Removed) Check for violations of MISRA C:2012 rules and directives

Support for checking MISRA C™:2012 rules using Code Prover is removed. Use Check MISRA C:2012 (-misra3) in Bug Finder instead. For more information, see Version History.

Description

Specify whether to check for violations of MISRA C:2012 guidelines. Each value of the option corresponds to a subset of guidelines to check.

Set Option

User interface (desktop products only): In your project configuration, the option is on the Coding Standards & Code Metrics node. See Dependencies for other options that you must also enable.

Command line and options file: Use the option -misra3. See Command-Line Information.

Why Use This Option

Use this option to specify the subset of MISRA C:2012 rules to check for.

After analysis, the Results List pane lists the coding standard violations. On the Source pane, for every coding rule violation, Polyspace^® assigns a symbol to the keyword or identifier relevant to the violation.

Settings

Default: mandatory-required

mandatory

Check for mandatory guidelines.

mandatory-required

Check for mandatory and required guidelines.

Mandatory guidelines: Your code must comply with these guidelines.
Required guidelines: You may deviate from these guidelines. However, you must complete a formal deviation record, and your deviation must be authorized.
See Section 5.4 of the MISRA C:2012 guidelines. For an example of a deviation record, see Appendix I of the MISRA C:2012 guidelines.

Note

To turn off some required guidelines, instead of mandatory-required select custom. To clear specific guidelines, click . In the Comment column, enter your rationale for disabling a guideline. For instance, you can enter the Deviation ID that refers to a deviation record for the guideline. The rationale appears in your generated report.

single-unit-rules

Check a subset of rules that apply only to single translation units. These rules are checked in the compilation phase of the analysis.

system-decidable-rules

Check rules in the single-unit-rules subset and some rules that apply to the collective set of program files. The additional rules are the less complex rules that apply at the integration level. These rules can be checked only at the integration level because the rules involve more than one translation unit. These rules are checked in the compilation and linking phases of the analysis.

all

Check for mandatory, required, and advisory guidelines.

SQO-subset1

Check for only a subset of guidelines. In Polyspace Code Prover™, observing these rules can reduce the number of unproven results. For more information, see Software Quality Objective Subsets for MISRA Coding Standards.

SQO-subset2

Check for the subset SQO-subset1, plus some additional rules. In Polyspace Code Prover, observing these rules can further reduce the number of unproven results. For more information, see Software Quality Objective Subsets for MISRA Coding Standards.

from-file

Specify an XML file where you configure a custom selection of checkers for this coding standard. To create a configuration file, click , then select the rules and recommendations you want to check for this coding standard from the right pane of the Checkers selection window. Save the file.

To use or update an existing configuration file, in the Checkers selection window, enter the full path to the file in the field provided or click Browse.

If you set the option to from-file, enable Set checkers by file (-checkers-selection-file).

Dependencies

This option is available only if you set Source code language (-lang) to C or C-CPP.
For projects with mixed C and C++ code, the MISRA C:2012 checker analyzes only .c files.
If you set Source code language (-lang) to C-CPP, you can activate a C coding rule checker and a C++ coding rule checker. When you have both C and C++ coding rule checkers active, to avoid duplicate results, Polyspace does not produce the C coding rules found in the linking phase (such as MISRA C:2012 Rule 8.3).

Tips

To reduce unproven results in Polyspace Code Prover:
1. Find coding rule violations in SQO-subset1. Fix your code to address the violations and rerun verification.
2. Find coding rule violations in SQO-subset2. Fix your code to address the violations and rerun verification.
If you select the option single-unit-rules or system-decidable-rules and choose to detect coding rule violations only, the analysis can complete quicker than checking other rules. For more information, see Coding Rule Subsets Checked Early in Analysis.
Polyspace Code Prover does not support checking of the following:
- MISRA C:2012 Directive 4.13 and 4.14
- MISRA C:2012 Rule 21.13, 21.14, and 21.17 - 21.20
- MISRA C:2012 Rule 22.1 - 22.4 and 22.6 - 22.10
For support of all MISRA C:2012 rules including the security guidelines in Amendment 1, use Polyspace Bug Finder™.
In code generated by using Embedded Coder^®, there are known deviations from MISRA C:2012. See Deviations Rationale for MISRA C Compliance (Embedded Coder).

Command-Line Information

Parameter: -misra3

Example (Bug Finder):

polyspace-bug-finder -lang c -sources file_name
                    -misra3 mandatory-required

Example (Code Prover):

polyspace-code-prover -lang c -sources file_name
                    -misra3 mandatory-required

Example (Bug Finder Server):

polyspace-bug-finder-server -lang c
                    -sources file_name -misra3
                    mandatory-required

Example (Code Prover Server):

polyspace-code-prover-server -lang c -sources
                        file_name -misra3
                mandatory-required

Version History

expand all

R2024a: Option removed from Code Prover

If you use the option -misra3 in a Code Prover analysis, Polyspace issues a warning and ignores the options in the analysis. The workflow for checking coding rule violation is removed from Code Prover in a future release. To check for coding rule violations, use Bug Finder. For instance, at the command line, replace this command:

polyspace-code-prover -sources file_name -misra3 all

with this command:

polyspace-bug-finder -sources file_name -misra3 all

See Migrate Code Prover Workflows for Checking Coding Standards and Code Metrics to Bug Finder.

R2022a: Option to be removed from Code Prover

If you use the option -misra3 in a Code Prover analysis, Polyspace issues a warning. The workflow for checking coding rule violation will be removed from Code Prover in a future release. To check for coding rule violations, use Bug Finder. For instance, at the command line, replace this command:

polyspace-code-prover -sources file_name -misra3 all

with this command:

polyspace-bug-finder -sources file_name -misra3 all

See Migrate Code Prover Workflows for Checking Coding Standards and Code Metrics to Bug Finder.

R2021b: Using text format for coding rules file not supported

Since R2019a, the file where you define a custom selection of coding standard checkers uses the XML format. You can save custom selections for all the coding standards that Polyspace supports in the same file. Using a text formal file for this purpose results in an error.

Desktop interface:

If you have a project that contains custom coding standard selection files in text format, Polyspace automatically updates and consolidates those files into a single XML file. If your project has conflicting configurations that refer to the same custom selection file, the software saves the consolidated coding standard selection for each configuration to separate XML files.

To update your text files to the XML format manually, in the Coding Standards & Code Metrics node of the Configuration pane, click . In the Checkers selection window, select the files then click Save Changes. Polyspace consolidates the files into a single XML files, and saves this file as filename.xml, where filename is the name of the first selected file alphabetically. For instance, if you select foo.conf and bar.conf, they are saved as bar.conf.xml.

Command-line/ IDEs:

In the command-line or in the IDE extensions, using text files as input to -misra3 results in an error. To select a custom selection of MISRA C:2012 rules and directives, use an XML file.

Use the file misra_c_2012_rules.xml as a template to create the XML file where you define the custom selection. This template file is located in polyspaceroot\polyspace\examples\doc_cxx\coding_standards_XML. Here, polyspaceroot is the root installation folder for the Polyspace products, for instance, C:\Program Files\Polyspace\R2024b. To update your script, see this table

Option	Use Instead
`-misra3 "custom_standard.conf"`	`-checkers-selection-file misra_c_2012_rules.xml -misra3 from-file`

See:

Note

The XML format of the checker configuration file can change in future releases.

Example of Configuration File in XML Format

R2021b: Option to be removed from Code Prover

Using -misra3 in a Code Prover analysis is not recommended. To check for coding rule violations, use Bug Finder.

R2019b: Use of text format for coding rules file will not be supported

Since R2019a, the file where you define a custom selection of coding standard checkers uses the XML format. You can save custom selections for all the coding standards that Polyspace supports in the same file. If you use a text file, Polyspace issues a warning and converts the text file to XML.