Why does Polyspace Code Prover generate a report even if compilation fails during analysis?

We generate Polyspace Reports on Code Prover R2018b. We have recently upgraded the version from R2015b to R2018b

We have found that reports get generated even when some files in the component fail compilation phase of Polyspace tool. This was not so when we run on R2015b.

Answer 1

[MathWorks Support Team]

This is an intended change to the behavior of Code Prover analysis introduced in R2017a. In that release, the default behavior was changed to allow analysis to continue to any remaining files if a compilation failure is detected. Hence, reports may be generated even if a compilation failure occurs.

Prior to R2017a, the default behavior was to stop analysis if any compilation failure was detected. To restore the old default behavior, you may specify the '-stop-if-compiler-error' option flag via the command line or in the Environment Settings page.

For more information on the compiler error flag option, please run the below command in the MATLAB R2018b command window to get the release specific documentation:

web(fullfile(docroot, 'codeprover/ref/stopanalysisifafiledoesnotcompilestopifcompileerror.html'))

Please follow the below link to search for the required information regarding the current release:

https://www.mathworks.com/help/