Show impact analysis results only (-impact-analysis-only
)
Skip regular Code Prover checks for run-time errors and perform impact analysis only
Since R2023b
Description
This option affects a Code Prover analysis only.
If you enable the impact analysis mode in Code Prover, use this option to skip the regular Code Prover analysis for run-time errors and perform impact analysis only.
The impact analysis mode determines if two objects in your program have an impact on each other. In this mode, if you designate a pair of objects as source and sink, Code Prover can prove if the source has no impact on the sink.
Set Option
User interface (desktop products only): In your project configuration, the option is on the Check Behavior node.
User interface (Polyspace Platform, desktop products only): In your project configuration, the option is on the Static Analysis tab on the Run Time Errors > Check Behavior node.
Command line and options file: Use the option -impact-analysis-only
. See Command-Line Information.
Why Use This Option
The impact analysis mode takes additional time on top of the regular Code Prover analysis. If you want to perform impact analysis only and leave the regular Code Prover analysis for a separate run, enable this option.
Settings
- On
Code Prover checks only for the presence or absence of impact between sources and sinks in your program. Depending on your source-sink specifications, you see the results of one or more of these checks:
- Off (default)
Code Prover performs impact analysis, in addition to regular Code Prover run-time checks.
Dependencies
This option is available only if you set the following options:
Enable impact analysis using the option
Enable impact analysis (-impact-analysis)
.Specify the sources and sinks for impact analysis using the option
Specify sources and sinks (-impact-specifications)
.
Command-Line Information
Parameter:
-impact-analysis-only |
Default: Off |
Example (Code Prover):
polyspace-code-prover -sources |
Example (Code Prover Server):
polyspace-code-prover-server -sources |
Version History
Introduced in R2023b