Polyspace 'Verification'/'source code compliance' phase - why not parallel?

One of the slowest part of any Polyspace analysis is the source code verification step but this performed sequentially, one file at a time. Is there any good reason this phase does not make use of any multi-core environment and verify the code in parallel?

TIA Martin

Answer 1

[Alexandre De Barros]

Hello Martin,

Since R2014b, the compliance checking of the source files is parallelized.

See the release notes on this page : https://www.mathworks.com/help/codeprover/release-notes.html and look at the paragraph R2014b for more information.

Best regards,

Alexandre

[Martin Dowie]

Ok, but I don't see this behaviour - never have on R2014b and I'm now on R2017b freshly installed on a brand new PC.

Just to be clear - it recognizes the 8 cores...but it only ever uses 1 during the 'source code compliance' phase. Actual analysis phases do make use of the multi-cores.

[Alexandre De Barros]

Hi Martin,

The compilation phase is made of different stages, and not all the compilation phase can be parallelized.

It is done for the source files compliance phase (and so you should see that several cores are used during this stage) but it is difficult to do it for the cross-files compliance phase because in this phase, all the results are "inter-dependant".

Best regards,

Alexandre

[Martin Dowie]

Only in parallel for C not for C++ (or Ada presumably)...

...R2018a please!!