Narrower arithmetic types can be cast to wider types without any effect on the magnitude of numeric values. However, whereas integer types represent exact values, floating-point types point types have limited precision. The C Standard, 66.3.1.4 paragraph 2 3 [ISO/IEC 9899:20112024], states
When a value of integer type is converted to a real standard floating type, if the value being converted can be represented exactly in the new type, it is unchanged. If the value being converted is in the range of values that can be represented but cannot be represented exactly, the result is either the nearest higher or nearest lower representable value, chosen in an implementation-defined manner. If the value being converted is outside the range of values that can be represented, the behavior is is undefined. Results of some implicit conversions may be represented in greater range and precision than that required by the new type (see 6.3.1.8 and 6.8.67.45).
Conversion from integral types to floating-point types without sufficient precision can lead to loss of precision (loss of least significant bits). No runtime exception occurs despite the loss.
...
Code Block | ||||
---|---|---|---|---|
| ||||
#include <stdio.h> int main(void) { long int big = 12345678901234567890L; float approx = big; printf("%ld\n", (big - (long int)approx)); return 0; } |
...
Code Block | ||||
---|---|---|---|---|
| ||||
#include <assert.h> #include <float.h> #include <limits.h> #include <math.h> #include <stdint.h> #include <stdio.h> extern size_t popcount(uintmax_t); /* See INT35-C */ #define PRECISION(umax_value) popcount(umax_value) int main(void) { assert(PRECISION(LONG_MAX) <= DBL_MANT_DIG * log2(FLT_RADIX)); long int big = 12345678901234567890L; double approx = big; printf("%ld\n", (big - (long int)approx)); return 0; } |
...
Conversion from integral types to floating-point types without sufficient precision can lead to loss of precision (loss of least significant bits).
Rule | Severity | Likelihood | Remediation Cost | Priority | Level |
---|---|---|---|---|---|
FLP36-C | Low | Unlikely | Medium | P2 | L3 |
Automated Detection
Tool | Version | Checker | Description | ||||||
---|---|---|---|---|---|---|---|---|---|
Astrée |
| Supported: Astrée keeps track of all floating point rounding errors and loss of precision and reports code defects resulting from those. | |||||||
CodeSonar |
| LANG.TYPE.IAT | Inappropriate Assignment Type | ||||||
Coverity |
| MISRA C 2004 Rule 10.x (needs investigation) | Needs investigation | ||||||
Cppcheck Premium |
| premium-cert-flp36-c | Fully implemented | ||||||
Helix QAC |
| C1260, C1263, C1298, C1299, C1800, C1802, C1803, C1804, C4117, C4435, C4437, C4445 C++3011 | |||||||
Klocwork |
| PORTING.CAST.FLTPNT | |||||||
LDRA tool suite |
| 435 S | Fully implemented | ||||||
Parasoft C/C++test |
| CERT_C-FLP36-a | Implicit conversions from integral to floating type which may result in a loss of information shall not be used | |||||||
PC-lint Plus |
| 915, 922 | Partially supported | ||||||
Polyspace Bug Finder |
| CERT-C: Rule FLP36-C | Checks for precision loss in integer to float conversion (rule fully covered) | ||||||
PVS-Studio |
| V674 |
Related Vulnerabilities
Search for vulnerabilities resulting from the violation of this rule on the CERT website.
Related Guidelines
Key here (explains table format and definitions)
Taxonomy | Taxonomy item | Relationship |
---|---|---|
CERT C Secure Coding Standard | DCL03-C. Use a static assertion to test the value of a constant expression | Prior to 2018-01-12: CERT: Unspecified Relationship |
CERT Oracle Secure Coding Standard for Java | NUM13-J. Avoid loss of precision when converting primitive integers to floating-point | Prior to 2018-01-12: CERT: Unspecified Relationship |
Bibliography
...
...