Settings from (C)

R2026b

(To be removed) Settings to use for the Polyspace analysis of C code

Model Configuration Pane: Polyspace

This option will be removed in a future release. In R2026b, it moved into the Advanced parameters section.

Description

The Settings from parameter determines Polyspace^® analysis settings for C code. You can choose to add C coding rules to your analysis using this parameter.

Dependencies

This setting overrides custom configuration settings in Project configuration and Use custom project file. If you want to use your custom coding rule settings, specify them in the Project configuration or in a custom project file.

Settings

Project configuration (default) | Project configuration and MISRA AC AGC checking | Project configuration and MISRA C 2004 checking | Project configuration and MISRA C 2012 checking | MISRA AC AGC checking | MISRA C 2004 checking | MISRA C 2012 checking

Project configuration

Run Polyspace with the options specified in Project configuration or Use custom project file.

Polyspace does not check for coding rule violations unless you select a rule set in the configuration.

Project configuration and MISRA AC AGC checking

(Removed) Polyspace Code Prover™ no longer supports checking for coding rule violations. This setting is deprecated in Polyspace Bug Finder™.

Project configuration and MISRA C 2004 checking

(Removed) Polyspace Code Prover no longer supports checking for coding rule violations. This setting is deprecated in Polyspace Bug Finder.

Project configuration and MISRA C 2012 checking

(Removed) Polyspace Code Prover no longer supports checking for coding rule violations. Use this setting when running Polyspace Bug Finder.

MISRA AC AGC checking

(Removed) Polyspace Code Prover no longer supports checking for coding rule violations. This setting is deprecated in Polyspace Bug Finder.

MISRA C 2004 checking

(Removed) Polyspace Code Prover no longer supports checking for coding rule violations. This setting is deprecated in Polyspace Bug Finder.

MISRA C 2012 checking

(Removed) Polyspace Code Prover no longer supports checking for coding rule violations. Use this setting when running Polyspace Bug Finder.

Recommended Settings

Application	Setting
Debugging	No Impact
Traceability	No Impact
Efficiency	No Impact
Safety precaution	No Impact

Programmatic Use

Parameter: VerificationSettings for use with pslinkoptions

Parameter: PSVerificationSettings for use with set_param()

Values: 'PrjConfig' | 'PrjConfigAndMisraAGC' | 'PrjConfigAndMisra' | 'PrjConfigAndMisraC2012' | 'MisraAGC' | 'Misra' | 'MisraC2012'

Default: 'PrjConfig'

Example: opt = pslinkoptions(modelname); opt.VerificationSettings = 'PrjConfigAndMisraC2012'

Version History

Introduced in R2016b

R2026b: Support for MISRA C:2004 and MISRA AC AGC standards is removed

Support for the MISRA™ C:2004 and MISRA AC AGC standards is removed. Running an analysis with any of these options will produce an error:

• MISRA AC AGC checking

• Project configuration and MISRA AC AGC checking

• MISRA C 2004 checking

• Project configuration and MISRA C 2004 checking

Use the newer MISRA C standards instead. When analyzing generated code, use a newer MISRA C standard with the option Use generated code requirements for MISRA standards (-misra-agc-mode) enabled in the Polyspace configuration.

R2026b: Settings from parameter will be removed

The Settings from parameter will be removed in a future release. In R2026b, this parameter moved into the Advanced parameters section of the Configuration Parameters dialog box.