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
8266368: Inaccurate after_unwind hook in C2 exception handler #6405
Conversation
|
/cc hotspot-compiler |
@dean-long |
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!
/reviewers 2 |
@fisk This change now passes all automated pre-integration checks. 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 156 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.
|
@dean-long |
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 the reviews, @TobiHartmann and @dean-long. |
/integrate |
Going to push as commit 2c06bca.
Your commit was automatically rebased without conflicts. |
When we throw an exception and unwind into a frame, the exception handler of that frame needs to call an after_unwind hook for the StackWatermark code, to support for concurrent stack processing. Unfortunately, for C2 frames, I inaccurately do this in OptoRuntime::rethrow_C, but the exception handler when unwinding into a C2 frame really is OptoRuntime::handle_exception_C.
The handle_exception_C code does walk frames to the caller though, which also pokes the StackWatermark code. So in the end, there is no real bug here, but it works for the wrong reasons. So I'd like to move the hook in rethrow_C to handle_exception_C.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/6405/head:pull/6405
$ git checkout pull/6405
Update a local copy of the PR:
$ git checkout pull/6405
$ git pull https://git.openjdk.java.net/jdk pull/6405/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 6405
View PR using the GUI difftool:
$ git pr show -t 6405
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/6405.diff