Overflow when converting between integer types
This defect occurs when converting an integer to a smaller integer type. If the variable does not have enough bytes to represent the original value, the conversion overflows.
The exact storage allocation for different floating point types depends on your
processor. See Target processor type (-target).
Integer conversion overflows result in undefined behavior.
The fix depends on the root cause of the defect. Often the result details show a sequence of events that led to the defect. Use this event list to determine how the variables in the overflowing computation acquire their current values. You can implement the fix on any event in the sequence. If the result details do not show the event history, you can trace back using right-click options in the source code and see previous related events. See also Interpret Bug Finder Results in Polyspace Desktop User Interface.
You can fix the defect by:
Using a bigger data type for the result of the conversion so that all values can be accommodated.
Checking for values that lead to the overflow and performing appropriate error handling.
In general, avoid conversions to smaller integer types.
See examples of fixes below.
If you do not want to fix the issue, add comments to your result or code to avoid another review. See Address Polyspace Results Through Bug Fixes or Justifications.
| Group: Numerical |
| Language: C | C++ |
| Default: On |
Command-Line Syntax: INT_CONV_OVFL |
| Impact: High |
| CWE ID: 128, 189, 190, 191, 192, 197 |
Find
defects (-checkers) | Float conversion overflow | Sign change integer conversion overflow | Unsigned integer conversion overflow