Different Results for Polyspace as You Code (PaYC) and "normal" Polyspace

We use following:

1. Polyspace in our GitLab CI/CD pipeline, which triggers Polyspace analyses over the whole C project when pushing Code to Bitbucket
2. The plugin Polyspace as You Code (PaYC) within Eclipse IDE to analyze quickly during coding, before pushing buggy code

Since you cannot analyze the whole project with PaYC (or I don't know how), only individual files, how can it check weaknesses thoroughly?

Because it does not have the context (the big picture), for example:

I define in one file an entity (variable, macro etc.) and use it in another file. If I check only the file where the entity is defined, Polyspace would say "unused variable/macro".

So my quesiton is, is the use case for both versions of Polyspace not the same or is it expected that both versions work the same way?

Can I analyze the whole project with PaYC, if yes, how? Is it maybe a setting issue (Build settings for PaYC in Eclipse)?

[Tapio Kramer]

Hi,

I'll let my colleagues from advanced or tech support provide you with an official answer.

PaYC is meant to only do file-scope analyses. I guess you have seen this in the documentation:

Comparing Polyspace Bug Finder analysis to Polyspace as You Code

Twice a year we invite Polyspace users (whom we know) to the 'Polyspace Users Meetup' to share news and best practices. Last March PaYC was the major topic. Maybe you'd be interested to watch the recording?

Here are the past events. The next one will be about "Polyspace Access Best Practices for Effective Review Workflows"

regards,

Tapio

[Ismet]

Many thanks!

Answer 1

[Christian Bard]

As you mentioned, Polyspace as You Code is a plug-in for certain IDEs that analyzes one file at a time. This allows you to select findings that are not influenced by contextual causes. For more details, refer to the scope of analysis and the checkers deactivated for Polyspace as You Code in the documentation.

If you wish to extend the scope of analysis, you will need to use Polyspace Bug Finder. Additionally, you can link Polyspace Bug Finder results with Polyspace as You Code using the baseline associated with the plug-in and Polyspace Access.

[Ismet]

Many thanks!