We use cookies to make your experience better. To comply with the new e-Privacy directive, we need to ask for your consent to set the cookies. Learn more.
Polyspace — R2021a
Polyspace R2021a: A Deep Dive into Features, Bug Fixes, and Workflow Enhancements
The release of Polyspace R2021a marked a significant milestone for engineers and embedded software developers striving for compliance with high-integrity standards (ISO 26262, DO-178C, IEC 61508). As part of the MathWorks Spring 2021 release, Polyspace R2021a didn’t just introduce incremental bug fixes; it redefined how static analysis integrates into CI/CD pipelines and agile development workflows.
This article explores the new features, performance improvements, and specific code-checking capabilities introduced in Polyspace R2021a, while providing guidance for teams looking to upgrade from legacy versions. polyspace r2021a
Real-World Case Study: Aerospace Flight Controller
A Tier-1 aerospace supplier (anonymous due to ITAR) migrated from LDRA to Polyspace R2021a for a fly-by-wire controller. Polyspace R2021a: A Deep Dive into Features, Bug
Codebase: 1.2M LOC of C99, targeting DO-178C Level A. Real-World Case Study: Aerospace Flight Controller A Tier-1
Challenge: Previous static analysis produced 4,000+ warnings, requiring 6 person-months of manual triage per release.
Polyspace R2021a Results:
- Code Prover reduced proven-unproblematic findings to 120 true red checks.
- Incremental verification cut analysis time from 36 hours to 10 hours.
- Polyspace Access allowed distributed review across 8 engineers.
- The TQS Kit simplified FAA auditis.
Outcome: First-pass certification success. The verification team shrank from 12 to 7 engineers.
9. Upgrade Recommendations from R2020b or Earlier
- Run compatibility check –
polyspace-cxx-compatibility-checkon existing project configurations. - Rebaseline – New checkers may introduce additional findings; baseline to ignore legacy noise.
- Update CI scripts – Replace deprecated
-runwith-sourcesand-target-compiler. - Test on a representative module before full rollout.
Typical Use Cases
- Early defect detection during development to lower later rework and testing costs.
- Safety certification evidence (e.g., ISO 26262, DO-178C) — generating artifacts required by safety assessors.
- Enforcing coding standards (MISRA, CERT) across teams and releases.
- Root-cause analysis for sporadic or hard-to-reproduce bugs by reasoning about all possible runtime states.
- Verifying third-party or legacy code prior to integration.
6. Upgrading from Polyspace R2020b to R2021a
10. Compatibility Notes
- Requires MATLAB R2021a (license tied to MATLAB version).
- Backward compatible with Polyspace R2020b projects (upgrade warning).
- No longer supports Windows 7 (Windows 10 required).
- macOS support only Intel (no Apple Silicon native).