Polyspace R2021a: ~upd~

: Load your analysis results in the Polyspace Platform.

: These checkers monitor metrics such as cyclomatic complexity and the number of execution paths.

The R2021a suite is divided into two primary products, each serving a distinct purpose in the software development lifecycle. Polyspace Bug Finder Polyspace Code Prover Pattern matching and dataflow analysis Abstract interpretation (Formal methods) Analysis Speed Fast (Minutes) Thorough (Hours) Code Color-Coding Defects highlighted individually Green, Red, Gray, and Orange visual proofs False Negatives Possible (May miss complex bugs) Zero (Guarantees absence of specific errors) Best Used For Early development, styling, coding standards Certification, safety-critical compliance The Power of Color-Coded Verification

Approx. March 2021 (MathWorks) Purpose: To provide a structured overview of capabilities, workflow optimizations, and key updates in Polyspace R2021a for high-integrity software development (ISO 26262, DO-178C, IEC 61508, ISO 62304). polyspace r2021a

Developers configure the analysis environment by specifying the compiler dialect, target hardware properties (such as word sizes), include paths, and macro definitions. In R2021a, this can be automated by extracting build options directly from build systems like CMake or makefiles. Step 2: Execution

Polyspace R2021a: Advancing Static Code Analysis for Safety-Critical Software

Exhaustive formal verification to prove the absence of run-time errors. : Load your analysis results in the Polyspace Platform

: Proven to cause a run-time error (e.g., division by zero, array out-of-bounds) every time the line is reached. Gray : Dead code or unachievable execution paths.

option, helping to reduce false violations based on specific compiler capabilities. Core Products in the R2021a Suite Polyspace Bug Finder

┌───────────────────────────────┐ │ Polyspace R2021a │ └───────────────┬───────────────┘ │ ┌─────────────────────────────────┼────────────────────────────────┐ ▼ ▼ ▼ ┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐ │ AUTOSAR RTE API │ │ Guidelines │ │ Mixed C and C++ │ │ Faster Analysis │ │ Checkers │ │ Single Project │ └─────────────────┘ └─────────────────┘ └─────────────────┘ 1. AUTOSAR RTE API Awareness Polyspace Bug Finder Polyspace Code Prover Pattern matching

R2021a adds support for additional rules within the MISRA C++ , AUTOSAR C++14, and CERT C++ standards. Workflow and Tool Integration Improvements

The Simulink interface has been redesigned, allowing users to right-click on model components to quickly trigger "Prove Code for Model" or "Find Bugs in Model Code".