...

Suppressions and False Positives

Suppressions refer to code analysis violations that you have determined to be acceptable. False positives, however, are violations that match the coding pattern as described in the analysis rule, but do You may determine that some violation are acceptable because, for example, they are associated with non-safety-critical parts of the application or will not lead to actual defects when the application runs. In these instances, MISRA allows you to suppress violations and document a rationale. These violations are added to the Deviations Report.  The False positives, however, are violations reported in error. The standard also allows you to mark violations as false positives when the code analysis tool incorrectly reports them.  

...

Your code can contain violations and still be MISRA-compliant as long as the deviations from the standard are documented and that the safety of the software is unaffected. Deviations are code analysis rules that violations that have been suppressed either in C/C++test or in the DTP Violations Explorer. See the C/C++test documentation for details on suppressing violations using the C/C++test suppression mechanism. See Suppressing Violations in the Violations Explorer documentation for information about suppressing violations in DTP.

...

When DTP receives the next build, suppression information will be processed. If the message in the Suppression details field begins suppression reason begins with 'false positive', the violation will be excluded from MISRA Compliance reports, including from the Deviation report.  

...