Polyspace R2021a stands as a solid and well-rounded release that delivers meaningful improvements across performance, usability, and integration. Its enhancements in AUTOSAR RTE API analysis, mixed C/C++ project support, customizable complexity guidelines, and Polyspace Access web interface make it a worthwhile upgrade for teams engaged in safety-critical embedded development.
Polyspace R2021a introduces , a feature that brings static analysis results directly into popular IDEs: Visual Studio, Visual Studio Code, and Eclipse. The polyspace‑bug‑finder‑access system command enables running Polyspace as You Code analyses from the command line on Windows, Linux, and macOS.
Users can now utilize customized guidelines checkers to reduce software complexity, ensuring compliance with coding standards such as MISRA C/C++, CERT C, and AUTOSAR C++14.
With the new pslinkrunCrossRelease function, engineers can analyze code generated in earlier Simulink releases using the R2021a Polyspace engine. polyspace r2021a
This command generates a CSV file containing all analysis findings, facilitating integration with external reporting and metric collection systems.
Best for early development stages. It scans code quickly to find bugs and coding standard violations (similar to linting but more advanced).
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 Polyspace R2021a stands as a solid and well-rounded
: Polyspace is computationally demanding. For R2021a, MathWorks generally recommends 4 GB of RAM per core to maintain performance during complex proofs. Learning Curve : While the
: The error "Limitation: fixed‑point type is not supported" may occur when working with fixed‑point data types. A workaround is to substitute unsupported types with more familiar types (e.g., ‑D__sfract=float , ‑D__fract=float , ‑D__laccum=double ) for analysis purposes, though these substitutions do not reflect actual runtime behavior.
: Tracks untrusted data inputs to prevent injection vulnerabilities. This command generates a CSV file containing all
These improvements significantly streamlined the verification of component-based AUTOSAR software without sacrificing precision.
Enhanced coverage for modern C++ object-oriented patterns.
: Detail the use of Polyspace Server and Polyspace Access for automated verification within CI pipelines (e.g., using Bitbucket or Bamboo) [10].