To match your run-time environment, specify the target and compiler options. The analysis uses these options to determine variable sizes, language extensions and compiler-specific behavior. If you still get compilation errors, you can work around specific errors with options from the Macros and Environment Settings category.
|Specify the compiler that you use to build your source code|
|Specify size of data types and endianness by selecting a predefined target processor|
|Specify size of data types and endianness by creating your own target processor|
|Specify the underlying data type of size_t|
|Specify the underlying data type of wchar_t|
|Disable Polyspace definitions for char16_t or char32_t|
|Specify sizes of sfr types for code developed with Keil or IAR compilers|
|Specify default structure packing alignment for code developed in Visual C++|
|Ignore #pragma pack directives|
|Round down quotients from division or modulus of negative numbers instead of rounding up|
|Specify how to represent an enum with a base type|
|Specify how to treat the sign bit for logical right shifts on signed variables|
Specify Polyspace® analysis options in Polyspace user interface, other IDE-s or scripts.
Learn the workflow for specifying Target & Compiler options.
Learn why automatic Polyspace project creation might not work for your build system and how to work around some of the causes.
Find paths to C or C++ standard library headers from your compiler and specify the paths in your Polyspace project.
See supported language standards and the default standard used in Polyspace analysis.
Find which Keil or IAR-specific extensions of the C language standard are supported for verification.