Checkers Deactivated in Polyspace as You Code Analysis

Polyspace^® as You Code finds bugs and coding rule violations in the currently active file in your IDE. If finding an issue requires multiple source files, the analysis cannot flag the issue by design. To help you with the checkers selection strategy:

• Checkers that typically produce most results in a multi-file context are completely deactivated in Polyspace as You Code.

• Some coding standard checkers cover both single and multi-file issues. These checkers are not deactivated but have a reduced scope and show fewer issues in Polyspace as You Code compared to a full integration analysis.

You can detect these multi-file issues by running an integration analysis on your project by using Polyspace Bug Finder™ or Polyspace Bug Finder Server™.

To find the defect checkers and coding rule checkers that are deactivated in a Polyspace as You Code analysis:

1. Locate the file polyspaceroot\polyspace\resources\Polyspace R2025a Results List.xlsx. Here, polyspaceroot is the Polyspace installation folder. The default installation folder is C:\Program Files\Polyspace\R2025a.

2. Find coding rule and defect checkers in the tabs. Bug Finder defect checkers are in the tab Bug Finder and coding rule checkers are in the tab corresponding to the standard to which they belong.

3. For the checker, look up the value in the column Available with PaYC . Checkers that are deactivated in Polyspace as You Code have a value of no in this column.

If you enable the deactivated checkers in your Polyspace as You Code IDE extension settings (or by using the option Checkers activation file (-checkers-activation-file) (Polyspace Bug Finder)), they are internally deactivated during analysis. No results corresponding to these checkers are shown after a Polyspace as You Code analysis.