-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
8252518: cache result of CompilerToVM.getComponentType #172
Conversation
👋 Welcome back dnsimon! A progress list of the required criteria for merging this PR into |
@dougxc The following label will be automatically applied to this pull request: When this pull request is ready to be reviewed, an RFR email will be sent to the corresponding mailing list. If you would like to change these labels, use the |
Good. |
@dougxc This change now passes all automated pre-integration checks. In addition to the automated checks, the change must also fulfill all project specific requirements After integration, the commit message will be:
Since the source branch of this PR was last updated there have been 102 commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid automatic rebasing, please merge ➡️ To integrate this PR with the above commit message to the |
/integrate |
@dougxc Since your change was applied there have been 102 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 0f26ab1. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Linux perf profiles of CompileTheWorld with libgraal show that
CompilerToVM.getComponentType
is the most expensive JVMCI VM entry point with almost 2% of total execution time:It's worth caching the result of this call.
Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/172/head:pull/172
$ git checkout pull/172