In Polyspace R2021a, reports are used to document the results of static analysis for C and C++ projects, typically covering defects, coding standard violations, and code metrics Report Types and Contents The R2021a release of Polyspace Bug Finder Polyspace Code Prover allows you to generate several types of reports: Defect Reports
Before dissecting the R2021a update, it is crucial to understand the two core products within the Polyspace family:
to review results on a web-based interface, which facilitates collaboration between developers and QA teams. Automation polyspace r2021a
: Analysis of code using the AUTOSAR RTE API is faster and more precise. New "smart stubs" for AUTOSAR libraries allow users to check for standard compliance without losing precision or needing complex manual setups.
For developers and organizations looking to leverage the capabilities of Polyspace R2021a, MathWorks provides comprehensive resources: In Polyspace R2021a, reports are used to document
| Codebase (LOC) | Tool | R2020b time | R2021a time | Memory Δ | |---------------|------|-------------|-------------|-----------| | 200k (C, automotive) | Code Prover | 28 min | 24 min | -8% | | 500k (C++, aerospace) | Bug Finder | 17 min | 14 min | -5% | | 50k (C, MISRA) | Bug Finder | 4.2 min | 3.5 min | -10% |
Rachel shook her head. "No, what's that?" For developers and organizations looking to leverage the
Here is how you can generate a professional report of your results: Generate a Report from the UI