Coding Standards and Code Metrics
MISRA, AUTOSAR, CERT, and JSF coding rule sets, custom coding rules, code metrics
To specify which coding standards you want to check, for instance, MISRA C™:2012 or AUTOSAR C++14, use the coding standard options. To see code complexity metrics in your analysis results, for instance, cyclomatic complexity and number of calling or called functions, use the code metrics option.
Polyspace Options
Topics
Getting Started
- Specify Polyspace Analysis Options
Specify Polyspace® analysis options in Polyspace user interface, other IDE-s or scripts. - Check for and Review Coding Standard Violations
Check for violations of AUTOSAR C++14, CERT® C, CERT C++, CWE, MISRA C, MISRA™ C++, JSF AV C++, or ISO-17961 standards with Polyspace Bug Finder. - Enforce Naming Conventions for C/C++ Variables and Functions
Enforce naming conventions and other style guidelines on C/C++ code with Polyspace. - Reduce Software Complexity by Using Polyspace Checkers
Enable and configure the software complexity checkers to identify issues that make your code difficult to read, understand, and debug.
MISRA or JSF Rules
- Avoid Violations of MISRA C Rules 8.x
Avoid conflicting declarations or unintended modification of variables. - Coding Rule Subsets Checked Early in Analysis
Adjust your coding rules checking for a faster analysis.
Code Complexity Metrics
- Compute Code Complexity Metrics Using Polyspace
Enforce limits on code complexity metrics such as cyclomatic complexity and depth of nesting. - HIS Code Complexity Metrics
See which code complexity metrics supported in Polyspace are part of the Hersteller Initiative Software (HIS) standard.
User Defined Coding Standards
- Find Polyspace Bug Finder Checkers That Map to Coding Rules in User-Defined Coding Standard
Find Bug Finder checkers that can check for the coding rules in your user-defined coding rule standard. - Create User-Defined Coding Standard by Using Polyspace Bug Finder Checkers
Map Bug Finder checkers to coding rules in a user-defined coding standard in a sharable.pschk
file.
Modify Checker Behavior
- Modify Default Behavior of Bug Finder Checkers
Extend or constrain the default behavior of defect or coding standard checkers using Polyspace analysis options.
- Modify Bug Finder Checkers Through Code Behavior Specifications
- Flag Deprecated or Unsafe Functions, Keywords, or Macros Using Bug Finder Checkers
- Extend Bug Finder Checkers for Standard Library Functions to Custom Libraries
- Extend Bug Finder Checkers to Find Defects from Specific System Input Values
- Extend Concurrency Defect Checkers to Unsupported Multithreading Environments
- Extend Checkers for Initialization to Check Function Arguments Passed by Pointers
- Extend Data Race Checkers to Atomic Operations