-
Notifications
You must be signed in to change notification settings - Fork 5.5k
JIT: Use faster mod for uint16 values #128509
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
Draft
MihaZupan
wants to merge
7
commits into
dotnet:main
Choose a base branch
from
MihaZupan:uint16-mod
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from 4 commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
cea3809
JIT: Use faster mod for uint16 values
MihaZupan 56f1398
Add a MinOpts check
MihaZupan 897296a
Fix unsound IntegralRange refinement for NOL small-type locals
MihaZupan a222b5c
Move detection to range checks
MihaZupan ee631cf
Reduce the number of cases that are deferred to range check
MihaZupan e57ffd1
Add back the type check
MihaZupan d7d304f
Skip some of the new logic under minopts
MihaZupan 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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.
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.
I've been thinking about this particular problem a bit recently.
That is, the general problem where we have some operation
Xwhich has to be morphed into a different pattern for VN/CSE or other purposes, particularly when part of the expression is complex and/or expensive.I wonder if it would be beneficial in such cases to either have a flag on the "root" of the expression - i.e. a flag on the
SUBinSUB(x, MUL(DIV(x, y), y))indicating sayGTF_MOD_ROOTor even a custom node that exists only in HIR (you could identify it as aMODwith only 1 operand, for example).This would allow us to still do the morph but also allow any other code to trivially see "hey, this is actually a
MODexpression and so you can extract the x/y and do what you need optimization wise with it"The same would also apply to some other cases where we have data we want to CSE, like say
-floatwhere it has to emit asXOR(x, -0.0)on xarch orAbs(float)where it isANDN(x, -0.0)