JIT: Move executor to a register #143072
Open
JIT: Move executor to a register #143072
+11
−13
Conversation
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
diegorusso
requested review from
brandtbucher,
markshannon and
savannahostrowski
as code owners
Member
|
Hmmm, I would think that maybe instead of this, we allocate one more register to TOS caching instead for AArch64? I think that would probably provide bigger gains? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
With this change we put the executor in one of the register so that _MAKE_WARM and _CHECK_VALIDITY don't need to patch the executor and they become 1-2 machine instructions (depending on the platform)
On AArch64 there is a small uplift of 1% and in x86_64 the net effect is about 0% (even though we are using a caller saved register)