FIX: avoid overflow on overflow check in halley_step on Apple M1#937
FIX: avoid overflow on overflow check in halley_step on Apple M1#937mckib2 wants to merge 1 commit intoboostorg:developfrom
Conversation
|
I'm sure I'm missing something obvious here, but if denom >=1 there can be no overflow, and if its < 1 then denom*numeric_limits<>::max() can't overflow either? Or is a logical branch which should never be taken being speculatively evaluated? |
That's what I thought at first because we have seen that before on Apple Silicon, but splitting the expression out into two if statements (which resolved this previously) didn't resolve it locally for me and I don't know of another way to prevent the speculative execution. So if it might be executed, the change in this PR was the only thing I could find that avoided the |
include/boost/math/tools/roots.hpp
Outdated
| // |denom| >= |num| * max_value | ||
| // RHS may overflow on Apple M1, so rearrange: | ||
| // |denom| * 1/max_value >= |num| | ||
| constexpr T inv_max_value = 1.0 / tools::max_value<T>(); |
There was a problem hiding this comment.
| constexpr T inv_max_value = 1.0 / tools::max_value<T>(); | |
| const T inv_max_value = 1.0 / tools::max_value<T>(); |
There was a problem hiding this comment.
Even better make that static const and then it's evaluated just the once.
There was a problem hiding this comment.
I wanted static constexpr, but wasn't sure that is supported everywhere we want, and indeed, it appears even constexpr is problematic. Will implement this right away
mckib2
force-pushed
the
halley-step-mac-m1-overflow-fix
branch
from
99773d8 to
4a8903e
Compare
|
Superceded by #945 |
3 participants
[number]*tools::max_value<T>()to prevent overflows on Apple M1 precessors