Polyspace R2021a [new]
DevOps pipelines require automation. R2021a introduces optimized command-line interfaces and plugins for popular CI/CD servers like Jenkins and GitLab. Developers can trigger silent Polyspace analysis on code commits, blocking insecure code from entering the main repository branch. 4. Improved Review UI and Collaboration
Furthermore, the R2021a release can flag violations when arguments passed to an RTE API function do not adhere to AUTOSAR specifications. For instance, if a function expects an initialized buffer but the developer passes an uninitialized buffer by pointer, the analysis will mark this as a red-check violation. The analysis results also include a comprehensive list of recognized RTE API functions and events, allowing engineers to quickly navigate from an API call to its description in the official AUTOSAR standard.
Deeper vulnerability detection to secure code against cyber threats at the source level. 2. Enhanced Access via Polyspace Access
Code quality and security dominate the software development landscape. Embedded systems grow more complex daily. Software failures in automotive, aerospace, and medical devices carry massive consequences. Developers need automated tools to guarantee code safety. polyspace r2021a
What’s New in Polyspace R2021a? - MATLAB & Simulink - MathWorks
polyspace-analysis: stage: test script: - polyspace-bug-finder -sources src/ -lang c++14 -checkers-selection "all" - polyspace-report-generator -results polyspace_results.psx -format junit -o report.xml artifacts: reports: junit: report.xml
: You can customize existing templates to include only specific "stories" like memory safety or coding standards (MISRA/AUTOSAR). DevOps pipelines require automation
:
When generating production C code from a Simulink model, Embedded Coder adds special comments linking each line of C back to the Simulink block. Polyspace R2021a reads these comments and propagates traceability into its reports. Thus, if Code Prover finds a red check in generated code, the engineer can click directly to the offending Simulink block.
Open the results in the desktop UI or Polyspace Access. Navigate through the findings using the color-coded system provided by the Code Prover: The analysis results also include a comprehensive list
Manual code reviews fail to catch deep, multi-threaded concurrency bugs or obscure overflow errors. Polyspace R2021a acts as a tireless mathematical peer reviewer. By identifying defects before code leaves the developer’s desktop or enters physical hardware testing, organizations save millions of dollars in debugging time, recall risks, and software patch deployments.
: Features enhanced logging for services within the Admin UI, aiding team collaboration and project tracking. Core Tool Comparison Polyspace R2021a continues to rely on two primary engines: What's New in Polyspace R2021a? - MATLAB & Simulink
The R2021a release delivers faster analysis and more precise results for code utilizing the AUTOSAR Runtime Environment (RTE) API. This is a crucial update for automotive engineers aiming to verify complex AUTOSAR components.
Integration with MATLAB and Simulink is more seamless, reducing the steps needed to set up analysis for generated code.
Based on internal MathWorks data and user reports (2021–2022):