Prevent use of run-time floating point math functions for compile-time integer constants #252
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Not all compilers are smart enough to evaluate
pow()
function and cast the result to integer at compile time, which leads to unresolved dependencies on libm at link-time. Better use standardUINTxx_C()
macros for explicitly define long integer constants, and bit-shifting operations as long as powers of 2 are considered.