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
8253447: Remove buggy code introduced by 8249451 #292
Conversation
👋 Welcome back jcm! A progress list of the required criteria for merging this PR into |
@jamsheedcm |
@jamsheedcm |
@jamsheedcm 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 |
Webrevs
|
@dholmes-ora @veresov @fisk could you please have a look. |
@jamsheedcm 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 2 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 |
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, thanks for fixing this.
Thank you @dholmes-ora @veresov @fisk /integrate |
@jamsheedcm Since your change was applied there have been 2 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit f7b1ce4. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
if ((thread->has_pending_exception() || thread->frames_to_pop_failed_realloc() > 0) && exec_mode != Unpack_uncommon_trap) {
assert(thread->has_pending_exception(), "should have thrown OOME/Async");
introduced a buggy code checking, clearing pending exception and taking Unpack_exception route.
This can have consequences as the deopt entries may have additional logic depending on bci's. and the change introduced in 8249451 doesn't honor deopt exception checking and forward logic.
Thank you @fisk for pointing the bug in the code.
Request for review.
/cc hotspot-compiler
/cc hotspot-runtime
Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/292/head:pull/292
$ git checkout pull/292