Add support for OSR jitted code #1584
Merged
Conversation
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
Parser support for OSR. OSR methods jit on foreground threads.
|
We have been setting the proper info in the ETW records for quite a while now. But OSR has always been an experimental feature, so I never bothered to update any tooling. Now we're getting close to enabling it by default for some architectures. Methods jitted this way should start showing up in .NET 7 Preview 3 or 4. Without this change, OSR methods show up as "ReadyToRun" in tiering annotated views, and mess up the jit stats report. |
kouvel
approved these changes
Mar 10, 2022
72 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Parser support for OSR.
OSR methods jit on foreground threads.