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.
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
Skip FP registers processing if method don't have floating points use #85744
Skip FP registers processing if method don't have floating points use #85744
Changes from 1 commit
fe09c7f
8a7d379
e295312
de985d6
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 safe change would be to have
needFloatingRegisters |= (theRegisterType != IntRegisterType);
innewInterval()
method but want to see if my current changes achieve the purpose.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 think this bit in particular is a bit difficult as we need to pre-emptively set
compFloatingPointUsed
for any SIMD code. But that can't really account for dead code elimination or other factors that might later remove or transforms the nodes to no longer need it.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.
Would it instead be possible to have
regMaskTP LinearScan::internalFloatRegCandidates()
lazily do the below, or is there other factors that require it?That is, have it do something like:
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.
Unfortunately we need the physRegRecord early right after identifying candidates.
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.
True, but this is the best we can do I suppose, unless you are proposing to just start from scratch in LSRA and set it to
true
duringBuildNode()
iftree->GetType() != TYP_INT
.Edit: Doing the check in
BuildNode()
might prove costly though because we will be doing that for every singleGenTree*
node and not sure how many cases we will optimize for the scenarios where we didn't account for dead code elimination.