MISRA C:2012 Rule 11.4
A conversion should not be performed between a pointer to object and an integer type
Description
Rule Definition
A conversion should not be performed between a pointer to object and an integer type1 .
Rationale
Conversion between integers and pointers can cause errors or undefined behavior.
If an integer is cast to a pointer, the resulting pointer can be incorrectly aligned. The incorrect alignment causes undefined behavior.
If a pointer is cast to an integer, the resulting value can be outside the allowed range for the integer type.
Polyspace Implementation
Casts or implicit conversions from NULL
or (void*)0
do
not generate a warning.
Troubleshooting
If you expect a rule violation but do not see it, refer to Diagnose Why Coding Standard Violations Do Not Appear as Expected.
Examples
Check Information
Group: Pointer Type Conversions |
Category: Advisory |
AGC Category: Advisory |
Version History
Introduced in R2014b
See Also
MISRA C:2012 Rule 11.3
| MISRA C:2012 Rule 11.7
| MISRA C:2012 Rule 11.9
| Check MISRA C:2012 (-misra3)
1 All MISRA coding rules and directives are © Copyright The MISRA Consortium Limited 2021.
The MISRA coding standards referenced in the Polyspace® Bug Finder™ documentation are from the following MISRA standards:
MISRA C:2004
MISRA C:2012
MISRA C:2023
MISRA C++:2008
MISRA C++:2023
MISRA and MISRA C are registered trademarks of The MISRA Consortium Limited 2021.