Proves the absence of overflow, divide-by-zero, out-of-bounds array access, and other critical runtime errors using mathematical proofs. Key Features and Enhancements in R2021a
: While 16 GB RAM is often cited as a minimum for MATLAB-based tools, 32 GB or 64 GB
Execute Polyspace Code Prover on stable code modules. Focus your attention on isolating and resolving any (proven error) and Orange (unproven) checks. Convert orange checks to green by adding defensive assertions or refining configuration constraints (e.g., bounding input variables). Step 4: Generate Compliance Reports
post always publishPolyspace results: 'results.pscp', thresholds: [unproven: 10, error: 0] polyspace r2021a
Code Prover uses formal methods to prove the mathematical safety of C and C++ source code.
: Conducts fast semantic analysis to catch bugs, security threats, and style violations early.
Platform: Intel Xeon E5-2680 v4, 64 GB RAM, SSD. Convert orange checks to green by adding defensive
With Polyspace R2021a on their side, the team began to tackle the errors one by one. The tool helped them prioritize the most critical issues and provided a clear plan of action. As they worked through the fixes, the team noticed something remarkable: their code was becoming not only more reliable but also more maintainable.
This bridges the gap between analysis results and traceability matrices required for DO-178C certification.
: 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. Platform: Intel Xeon E5-2680 v4, 64 GB RAM, SSD
Enforces industry standard rulesets, checking code against coding guidelines like MISRA C/C++, AUTOSAR C++14, and CERT C/C++.
Identifies numerical bugs, memory leaks, data races, and dead code.