-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8320139: [JVMCI] VmObjectAlloc is not generated by intrinsics methods which allocate objects #16980
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
Conversation
|
Hi @rmosaner, welcome to this OpenJDK project and thanks for contributing! We do not recognize you as Contributor and need to ensure you have signed the Oracle Contributor Agreement (OCA). If you have not signed the OCA, please follow the instructions. Please fill in your GitHub username in the "Username" field of the application. Once you have signed the OCA, please let us know by writing If you already are an OpenJDK Author, Committer or Reviewer, please click here to open a new issue so that we can record that fact. Please use "Add GitHub user rmosaner" as summary for the issue. If you are contributing this work on behalf of your employer and your employer has signed the OCA, please let us know by writing |
…a CompilerToVM::Data.
e662a40 to
0b430d8
Compare
|
@rmosaner Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information. |
Webrevs
|
|
@rmosaner This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be: You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 166 new 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 this automatic rebasing, please check the documentation for the /integrate command for further details. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@tkrodriguez, @dougxc) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
|
/integrate |
|
/integrate |
|
Looks good. /sponsor |
|
Going to push as commit 84c2379.
Your commit was automatically rebased without conflicts. |
|
@tkrodriguez @rmosaner Pushed as commit 84c2379. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
|
Hi, the build failure was observed after this patch. |
This PR exports a pointer to
JvmtiExport::_should_notify_object_allocvia JVMCI to enable intrinsification of unsafe allocations in accordance to C2.Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/16980/head:pull/16980$ git checkout pull/16980Update a local copy of the PR:
$ git checkout pull/16980$ git pull https://git.openjdk.org/jdk.git pull/16980/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 16980View PR using the GUI difftool:
$ git pr show -t 16980Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/16980.diff
Webrev
Link to Webrev Comment