-
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
8326101: [PPC64] Need to bailout cleanly if creation of stubs fails when code cache is out of space #17902
8326101: [PPC64] Need to bailout cleanly if creation of stubs fails when code cache is out of space #17902
Conversation
…hen code cache is out of space
👋 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. |
Webrevs
|
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.
@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 16 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 |
Hi Martin, seems we miss the record_failure at some places too on s390 src/hotspot/cpu/s390/s390.ad
src/hotspot/cpu/s390/compiledIC_s390.cpp
do you agree ? Should we file another JBS bug ? |
@offamitkumar: I think Matthias is right and s390 should get the same fix. Yes, a new JBS issue would be good. |
This one probably too I guess
|
I created |
Thanks Matthias, I'll look into for s390x port. |
Thanks for the reviews and for filing the s390 issue! |
Going to push as commit a19314b.
Your commit was automatically rebased without conflicts. |
@TheRealMDoerr Pushed as commit a19314b. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
e834a48 had missed some PPC64 parts. Note that the PPC64 implementation is similar to SPARC, so we need almost the same changes as that platform.
LIR_Assembler::emit_static_call_stub()
,LIR_Assembler::emit_trampoline_stub_for_call
andCallStubImpl::emit_trampoline_stub
already record failures internally.Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/17902/head:pull/17902
$ git checkout pull/17902
Update a local copy of the PR:
$ git checkout pull/17902
$ git pull https://git.openjdk.org/jdk.git pull/17902/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 17902
View PR using the GUI difftool:
$ git pr show -t 17902
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/17902.diff
Webrev
Link to Webrev Comment