-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
types: fix undefined behavior in numeric types cast (cast 1<<64 to uint64) #11968
Conversation
Signed-off-by: H-ZeX <[email protected]>
Signed-off-by: H-ZeX <[email protected]>
Codecov Report
@@ Coverage Diff @@
## master #11968 +/- ##
===========================================
Coverage ? 80.0309%
===========================================
Files ? 465
Lines ? 107336
Branches ? 0
===========================================
Hits ? 85902
Misses ? 14943
Partials ? 6491 |
Signed-off-by: H-ZeX <[email protected]>
Signed-off-by: H-ZeX <[email protected]>
/release |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/build |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please fix the ci.
And do we also need to cherry pick this commit to release-3.1 |
…fix_ub_in_numeric_types
/run-all-tests |
@XuHuaiyu PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/run-all-tests |
cherry pick to release-3.0 failed |
cherry pick to release-2.1 failed |
cherry pick to release-3.1 failed |
@H-ZeX Please cherry-pick this PR manually. |
It seems that, not for sure, we failed to cherry-pick this commit to release-2.1 release-3.0. Please comment '/run-cherry-picker' to try to trigger the cherry-picker if we did fail to cherry-pick this commit before. @lonng PTAL. |
/run-cherry-picker |
Signed-off-by: sre-bot <[email protected]>
cherry pick to release-2.1 in PR #16238 |
Signed-off-by: sre-bot <[email protected]>
cherry pick to release-3.0 in PR #16239 |
Signed-off-by: H-ZeX [email protected]
What problem does this PR solve?
In go-spec-conversions, there is this paragraph
so,
float64(1<<64)
cast to uint64 is undefined behavor. although in current go compiler, it is(1<<63)
, which is not same as mysql5.7 does.Check List
Code changes
No.
Side effects
No.
Related changes