Add Review Information to Results in Polyspace Platform User Interface

Address Code Prover results through bug fixes or justifications

Once you understand the root cause of a Polyspace^® finding, you can fix your code. Otherwise, add review information to the Polyspace result to mark it for fixing later or to justify the result. You can use the review information to keep track of your review progress and avoid reviewing the same finding twice.

If you add review information to your results file, they carry over to the results of the next analysis on the same project. If you add the same information as comments to your code (annotate), they carry over to any subsequent analysis of the code, whether in the same project or not. You can also hide results using code annotations.

Topics

Getting Started

Address Results in Polyspace Platform User Interface Through Bug Fixes or Justifications
Add review information to results or code to justify why a bug fix is not required and hide from subsequent analyses.
Annotate Code and Hide Known or Acceptable Results

Look up the Polyspace code annotation syntax for justifying known issues.
Import Review Information from Previous Polyspace Analysis
Import information such as status, severity and additional notes from another Polyspace result file.

Justifying MISRA Rule Violations

Import Justifications from Older Standard to Newer Standard
Import existing review information when migrating from the older coding standard.
Justify Coding Rule Violations Using Code Prover Checks
Use green runtime checks in Code Prover to allow exceptions for coding rule violations.