The verification manager uses Polyspace Access to:
polyspace-bug-finder:
image: mathworks/polyspace-r2021a:latest
script:
- polyspace-bug-finder -sources $CI_PROJECT_DIR -output-format gitlab-json > gl-report.json
artifacts:
reports:
codequality: gl-report.json
The results database schema changed from SQLite embedded to a more robust PostgreSQL backend for server deployments. Note: This is a breaking change. If you upgrade a Polyspace Access server from R2020b to R2021a, automatic migration is not supported. You must export old results as JSON before upgrading. polyspace r2021a
| Area | Limitation | Workaround |
|------|------------|-------------|
| C++17 | No std::pmr (polymorphic allocators) analysis. | Exclude or stub. |
| MISRA C++ 2008 | Rule 15–5 (class destructor exceptions) not enforced. | Manual review. |
| Code Prover | Recursion without depth limit leads to ? (unproven). | Add recursion depth bound via -max-recursion-depth. |
| Floating-point | NaN detection requires -allow-nan flag; not on by default. | Set explicitly. |
| Polyspace Access | No LDAP group sync – only manual user management. | Use API scripts to sync. | The results database schema changed from SQLite embedded
polyspace-bug-finder -sources main.c \
-target-compiler gcc9 \
-misra3 misra_c_2012_config.json \
-report-output-name results \
-generate-report -format pdf