-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
8325326: [PPC64] Don't relocate in case of allocation failure #17744
8325326: [PPC64] Don't relocate in case of allocation failure #17744
Conversation
👋 Welcome back mdoerr! A progress list of the required criteria for merging this PR into |
@TheRealMDoerr 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 /label pull request command. |
Pre-submit tests have an unrelated problem: [ERROR] None of JAVA_HOME, JDK_ARCHIVE_URL or JDK_ARCHIVE_URL_BASE are set |
Am I mistaken or have you eliminated all uses of |
Correct, I did a little bit of cleanup and wanted to make the oop case like the metadata case. We can use |
Hi, |
Yes. When we use the same oop constant several times, we should better share the TOC slot for efficiency reasons (space and GC overhead). We're doing this already at other places. And also for metadata. Seems like the 2 usages had been forgotten when making improvements. The allocate_* versions are only needed when we want to replace the object by a different one, typically null by the desired object. |
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.
LGTM
you might want to change the JBS title to something more meaningful
[ppc] Don't relocate in case of out-of-memory
or the like.
@TheRealMDoerr 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 126 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. ➡️ To integrate this PR with the above commit message to the |
Thanks for the review! I have changed the title. |
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.
Looks good.
Cheers, Richard.
Thanks! |
Going to push as commit 4388095.
Your commit was automatically rebased without conflicts. |
@TheRealMDoerr Pushed as commit 4388095. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
relocate
should be called after the result ofaddress_constant
has been checked. Otherwise, we may run into "assert(allocates2(pc)) failed: relocation addr must be in this section". SAP internal tests have passed.Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/17744/head:pull/17744
$ git checkout pull/17744
Update a local copy of the PR:
$ git checkout pull/17744
$ git pull https://git.openjdk.org/jdk.git pull/17744/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 17744
View PR using the GUI difftool:
$ git pr show -t 17744
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/17744.diff
Webrev
Link to Webrev Comment