Polyspace R2021a ^new^ Info

Mathematically proven safe under all runtime conditions.

Code Prover uses formal methods to prove the mathematical safety of C and C++ source code.

This new feature allows engineers to analyze code generated from an earlier release of Simulink using a later release of Polyspace. For example, if a project uses Simulink R2020b to generate code, but the organization has standardized on Polyspace R2021a for verification, the cross-release workflow handles the integration seamlessly. This flexibility enables teams to upgrade their static analysis toolchain without being forced to simultaneously upgrade their modeling environment, reducing disruption and validation overhead. polyspace r2021a

serves as a fast, scalable static analysis tool designed to identify hundreds of types of software defects, including critical runtime errors, concurrency issues, and security vulnerabilities. Bug Finder efficiently scans large codebases to help developers triage and fix high-impact coding flaws early in the development lifecycle, making it ideal for continuous integration and daily development workflows.

is a major update to the MathWorks static code analysis suite, designed to help developers prove the absence of critical run-time errors and uncover defects early in C and C++ projects. This release focuses on performance optimizations for large-scale embedded systems, particularly those using the AUTOSAR standard, and introduces new tools to manage code complexity. Key Advancements in Polyspace R2021a Mathematically proven safe under all runtime conditions

: Identifying complex modules before integration reduces code refactoring delays later in the development cycle. What's New in Polyspace R2021a? - MATLAB & Simulink

Prior to R2021a, engineers working on projects containing both C and C++ source files often faced a cumbersome workflow: they were forced to separate C files from C++ projects to ensure successful compilation and analysis. For example, if a project uses Simulink R2020b

: The web interface now includes a filter to view findings from a baseline run that have been fixed in the current run, providing clear evidence of progress during remediation.

: Developers can now run a single Polyspace Code Prover analysis on projects containing a mix of C and C++ source files, simplifying the verification of modern multi-language codebases.

For medical device software, R2021a improves the documentation workflow. The generated reports now include more granular traceability links, specifically tailored to the software lifecycle requirements of IEC 62304. This reduces the manual effort required to map static analysis results to the Software Development Plan (SDP).

This category includes customizable complexity checkers that evaluate quantifiable metrics, such as the number of execution paths in a function and the cyclomatic complexity (a measure of the number of linearly independent paths through a program's source code). By integrating these checks early in the development cycle, teams can detect overly complex modules and refactor them before they become deeply embedded in a project, ultimately reducing long-term technical debt.