Analysis Setup
Starting in R2024b, you can choose to use Polyspace Platform, an integrated environment for Polyspace® Bug Finder™, Polyspace Code Prover™, and Polyspace Test™. Polyspace Platform supports static analysis and dynamic testing of C/C++ code in one common interface. This means that:
You can perform a single one-time setup for static analysis and dynamic testing.
You can view results of static analysis and dynamic testing on a common dashboard.
The static analysis products provide information that makes the dynamic testing workflow easier.
Benefits of Polyspace Platform
The following table explains some benefits the integrated environment of Polyspace Platform provides.
| Benefit | Details |
|---|---|
| Shared project setup | You can add C/C++ source files to the project, configure build options, optionally change defaults for static analysis or testing options, and start running static analysis or tests. Adding sources and configuring build options is required only once, irrespective of whether you want to find bugs or write and run tests. |
| Shared build configuration | You can use your build configuration for both static analysis and running tests. Polyspace Bug Finder and Polyspace Code Prover use the build information to emulate your compiler and check your sources for compliance with the C/C++ language standard, before running static analysis. Polyspace Test uses the build information to build and run your sources and tests using your compiler. |
| Same layout for static analysis, dashboards, and test results | Polyspace Platform displays all results in a similar layout, whether or not the results are from static analysis or dynamic tests. You can see an overview of all results on a single dashboard. The dashboards for various families of results (defects, coding standard violations, tests, coverage) follow a similar layout. Opening a set of results from a project or result dashboard displays a Results List. Click a result to bring up explanation and review information in the Result Details pane and highlight the error in your code within the Source Code pane. You can start reviewing results by clicking on items on the Results List pane and drilling down to the details on the Result Details and Source Code pane. Once you review a result, you can add review information, such as the Status, Severity, and optional notes. This workflow is similar for all families of results (defects, coding standard violations, tests, coverage). |
| Static analysis products that complement dynamic testing | The static analysis products can provide information that makes the dynamic testing workflow easier. In particular:
|
New Features in the Polyspace Platform user interface
In addition, the Polyspace Platform user interface supports several new features that are not available in the desktop user interface.
| Feature | Learn more |
|---|---|
| Utilize basic source control abilities such as diff and merge for projects and configurations | Compare and Merge Polyspace Platform Projects and Configurations Before Submission to Source Control (Polyspace Test) |
| Create workspaces capable of opening multiple projects at once | Manage Related Projects in Polyspace Platform User Interface Using Workspaces |
| View project overview and review dashboards previously only available in Polyspace Access | |
| Review and address identical findings | |
| View file specific options in your project configuration | |
| Add resources such as source files, external test files, include paths, and xUnit test files using relative paths | Share Polyspace Platform Projects, Workspaces, and Configurations |
For more information about Polyspace Platform, see Polyspace Platform: A Unified Platform for Static Analysis and Dynamic Testing.
To migrate your current Polyspace projects (.psprj files) to
Polyspace Platform projects (.psprjx files), see Benefits and Limitations of Switching to Polyspace Platform User Interface.
Some capabilities are not yet supported in the Polyspace Platform user interface. For more information on unsupported workflows and changes in workflows, see Capabilities Not Yet Supported in Polyspace Platform User Interface.
In R2024b, Polyspace supports version C++20 of the C++ Standard (ISO®/IEC 14882:2020).
You can now setup a Polyspace analysis for code that uses C++20-specific features. Previously, Polyspace did not recognize some C++20 features, resulting in compilation errors.
See also C++ standard version
(-cpp-version).
Analysis Results
In R2024b, Polyspace supports all the rules and directives from the new MISRA C++:2023 standard. The MISRA C++:2023 guidelines target ISO/IEC 14882:2017, commonly referred to as C++17. This new standard is an update of MISRA C++:2008 and incorporates the AUTOSAR C++14 rules. To check for violations of coding rules from this new standard, use one of these workflows:
Polyspace Platform user interface — In the Static Analysis tab of Configuration, click the Defects and Coding Standards node and select Use custom checkers file. Open the Checkers Selection window by clicking
next to the option Checkers activation
file. In the Checkers Selection window, enable coding rules from the
MISRA C++:2023 standard. See Check for and Review Coding Defects and Coding Standard Violations In Polyspace
Platform.Polyspace desktop user interface — In the Configuration pane, navigate to the Coding Standards & Code Metrics node. Select the option Check MISRA C++:2023. You can choose to enable subsets of the standard by a selecting a value from the drop-down list.
Command line — Use the option
Check MISRA C++:2023 (-misra-cpp-2023)orCheckers activation file (-checkers-activation-file).Polyspace as You Code™ — Use the Checkers Selection window. See Setting Checkers in Polyspace as You Code (Polyspace Access).
For a list of MISRA C++:2023 rules, see MISRA C++:2023 Rules and Directives.
Reviewing Results
In R2024b, you can check for violations of coding rules from the new MISRA C++:2023 standard. The MISRA C++:2023 standard is an update and consolidation of the MISRA C++:2008 and AUTOSAR C++14 standards. If you have existing annotations and justification for MISRA C++:2008 and AUTOSAR C++14 results in your project, Polyspace automatically imports them for the corresponding MISRA C++:2023 results.
Consider this code that contains several MISRA C++:2008 and AUTOSAR C++14 violations:
int f1(int input) {
int x;
int a = 2, i = 0, b[10] = {0, 10, 20, 30, 40, 50, 60, 70, 80, 90};
/* polyspace +1 AUTOSAR-CPP14:M2-13-2 [To investigate:High] "Justification for M2-13-2" */
const int b2 = a + 00 ;
if (input)
x = 2;
/* polyspace +1 AUTOSAR-CPP14:A5-0-1 [To investigate:High] "Justification for A5-0-1" */
x = b[i] + i++;
}
void f2(void) {
int r, x=1, *p = &x;
float *q;
/* polyspace +1 AUTOSAR-CPP14:A5-2-2 [To investigate:High] "Justification for A5-2-2" */
q = (float*)p;
}
int f3(int input) {
int x;
int a = 2, i = 0, b[10] = {0, 10, 20, 30, 40, 50, 60, 70, 80, 90};
/* polyspace +1 MISRA-CPP:2-13-2 [To investigate:High] "Justification for 2-13-2" */
const int b2 = a + 00 ;
if (input)
x = 2;
/* polyspace +1 MISRA-CPP:5-0-1 [To investigate:High] "Justification 5-0-1" */
x = b[i] + i++;
}MISRA C++:2008 Rule
2-13-2 in the Results Details pane for MISRA C++:2023 Rule
5.13.3:
Polyspace also imports annotations and justifications from MISRA C++:2008 and AUTOSAR C++14 results to MISRA C++:2023 results if you upload your MISRA C++:2023 results to a Polyspace Access database that contains MISRA C++:2008 and AUTOSAR C++14 results.
For details about importing justifications, see Import Justifications from Older Standard to Newer Standard.