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
[X86] Support EGPR (R16-R31) for APX #67702
[X86] Support EGPR (R16-R31) for APX #67702
Changes from 3 commits
1935d2d
3082e2f
3e9649c
35e488a
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.
It's not clear to me when we need to distinguish
X86::GR8_NOREX2RegClassID
fromX86::GR8RegClassID
and when not. We have some other places, e.g., here that usingX86::GRxxRegClassID
, shouldn't need to update withX86::GRxx_NOREX2RegClassID
Besides, we also have some place to
createVirtualRegister(&X86::GRxxRegClass)
, should they need to update too?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.
We have comments in X86BaseInfo.h about when we need to distinguish them.
PREFETCH
instructions are in map TB and they can use r16-r31, soX86::GRxxRegClassID
does not need to be updated.Yes,
createVirtualRegister(&X86::GRxxRegClass)
needs to be updated if the instruction can not encode r16-r31. But I haven't found such place so far.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.
Will you update in this patch or a follow up?
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.
Didn't look through one by one, but here seems have risk since it itrates different instructions.
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.
There is no
createVirtualRegister(&X86::GRxxRegClass)
for instructions that can not encode EGPR so far. If there is any in the future, we will directly usecreateVirtualRegister(&X86::GRxx_NOREX2RegClass)
at those places.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.
What's the risk?
The code calls
getRegClass
to get the register class and then build the machine instruction with the same opcode. It looks safe to me.In X86, (If I remember correctly) pseudo instruction
COPY
is either aMOV
orKMOV
. Both of them can encode r16-31.