-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Simplify/optimize Int128 comparison operators #101848
Merged
tannergooding
merged 4 commits into
dotnet:main
from
lilinus:optimize-int128-comparisons
May 9, 2024
Merged
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
70e457c
Optimize In128 comparison operators
lilinus 848c12b
Merge branch 'main' into optimize-int128-comparisons
lilinus 75a3579
Document how Int128 comparison operators work
lilinus 0630152
Merge branch 'main' into optimize-int128-comparisons
lilinus File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
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.
A comment (in the code) explaining why this is valid would be beneficial.
Actually brute forcing this for some
struct S16 { byte _lower; byte _upper; }
is pretty trivial to do, but so is describing why this works out given the two's complement representation. -- Notably this comes down to the fact that all negative values have the sign bit set, so iflhs.upper < rhs.upper
in signed form, then either lhs/rhs have different signs, and the single comparison was sufficient or they have the same sign and the same was true.There may be other optimizations available here as well... In particular, comparisons
x cmp y
in general are done as ifx - y
and then setting CPU flags, without actually producing the result. That general premise is why the "most optimal" pattern is actuallycmp lower; sbb upper; setcc
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.
I tried my best documenting it with comments.