 
                            Recommendations
FLP00-C. Understand the limitations of floating point numbers
FLP01-C. Take care in rearranging floating point expressions
FLP02-C. Avoid using floating point numbers when precise computation is needed
FLP03-C. Detect and handle floating point errors
FLP04-C. Check floating point inputs for exceptional values
 
Rules
FLP30-C. Do not use floating point variables as loop counters
FLP31-C. Do not call functions expecting real values with complex values
FLP32-C. Prevent or detect domain and range errors in math functions
FLP33-C. Convert integers to floating point for floating point operations
FLP34-C. Ensure that floating point conversions are within range of the new type
FLP35-C. Take granularity into account when comparing floating point values
FLP36-C. Beware of precision loss when converting integral types to floating point
Risk Assessment Summary
| Recommendation | Severity | Likelihood | Remediation Cost | Priority | Level | 
|---|---|---|---|---|---|
| FLP00-C | medium | probable | high | P4 | L3 | 
| FLP01-C | low | probable | high | P2 | L3 | 
| FLP02-C | low | probable | high | P2 | L3 | 
| FLP03-C | low | probable | high | P2 | L3 | 
| FLP04-C. | low | probable | high | P6 | L2 | 
| Rule | Severity | Likelihood | Remediation Cost | Priority | Level | 
|---|---|---|---|---|---|
| FLP30-C | low | probable | low | P6 | L2 | 
| FLP31-C | low | probable | medium | P4 | L3 | 
| FLP32-C | medium | probable | medium | P8 | L2 | 
| FLP33-C | low | probable | low | P6 | L2 | 
| FLP34-C | low | unlikely | low | P3 | L3 | 
Related Rules and Recommendations
INT35-C. Evaluate integer expressions in a larger size before comparing or assigning to that size CERT C Secure Coding Standard FLP00-C. Understand the limitations of floating point numbers