Use generated code requirements (-misra3-agc-mode)

Check for violations of MISRA C:2012 rules and directives that apply to generated code

Description

Specify whether to use the MISRA C™:2012 categories for automatically generated code. This option changes which rules are mandatory, required, or advisory.

Set Option

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

User interface (Polyspace Platform, desktop products only): In your project configuration, in the Static Analysis tab, click Defects and Coding Standards and then select Use generated code requirements for MISRA C:2012.

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

Why Use This Option

Use this option to specify that you are checking for MISRA C:2012 rules in generated code. The option modifies the MISRA C:2012 subsets so that they are tailored for generated code.

Settings

Off (default)

Use the normal categories (mandatory, required, advisory) for MISRA C:2012 coding guideline checking.

On (default for analyses from Simulink^®)

Use the generated code categories (mandatory, required, advisory, readability) for MISRA C:2012 coding guideline checking.

For analyses started from the Simulink plug-in, this option is the default value.

 Category changed to Advisory

These rules are changed to advisory:

• 5.3

• 7.1

• 8.4, 8.5, 8.14

• 10.1, 10.2, 10.3, 10.4, 10.6, 10.7, 10.8

• 14.1, 14.4

• 15.2, 15.3

• 16.1, 16.2, 16.3, 16.4, 16.5, 16.6, 16.7

• 20.8

 Category changed to Readability

These guidelines are changed to readability:

• Dir 4.5

• 2.3, 2.4, 2.5, 2.6, 2.7

• 5.9

• 7.2, 7.3

• 9.2, 9.3, 9.5

• 11.9

• 13.3

• 14.2

• 15.7

• 17.5, 17.7, 17.8

• 18.5

• 20.5

Dependency

To use this option, activate at least one MISRA C:2012 rule. To activate MISRA C:2012 rules, use either of these:

• Use the option Check MISRA C:2012 (-misra3) to activate a preselected subset of the rules.

• Use the option Set checkers by file (-checkers-selection-file) alongside Check MISRA C:2012 (-misra3) to activate a custom selection that is specified in an XML file.

When using an XML file to specify a custom selection, select at least one MISRA C:2012 rule in the file.

In the Polyspace Platform user interface, this option is shown only when you select Use custom checkers file

Command-Line Information

Use the command -misra3-agc-mode in the command line to check for violations of MISRA C:2012 rules and directives that apply to generated code.

Parameter: -misra3-agc-mode

Default: Off

Example (Bug Finder): polyspace-bug-finder -sources file_name -misra3 all -misra3-agc-mode

Example (Bug Finder Server): polyspace-bug-finder-server -sources file_name -misra3 all -misra3-agc-mode

Alternatively, activate the rules and directives in an activation XML file. See Checkers activation file (-checkers-activation-file).