-
Notifications
You must be signed in to change notification settings - Fork 232
8339386: Assertion on AIX - original PC must be in the main code section of the compiled method #3998
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
8339386: Assertion on AIX - original PC must be in the main code section of the compiled method #3998
Conversation
👋 Welcome back mdoerr! A progress list of the required criteria for merging this PR into |
@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 6 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 |
This backport pull request has now been updated with issue from the original commit. |
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.
I do think the main issue here is using the wrong unextended_sp for a compiled sender if the current frame is interpreted. Then we would load an invalid original pc from the wrong slot.
This issue is solved with the backport. Thanks for doing it!
|
I agree. Thanks for the review! |
/approval request This backport makes frame::safe_for_sender more reliable on PPC64. The change only touches this function which is only used for profiling. The change has already been backported to 21.0.6 and there are no known issues. The 17u backport applies almost cleanly, but requires a modification which has been reviewed. The JFR tests have passed. |
@TheRealMDoerr |
/integrate |
Going to push as commit 6f50c6d.
Your commit was automatically rebased without conflicts. |
@TheRealMDoerr Pushed as commit 6f50c6d. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Backport of JDK-8339386. Applies almost cleanly, but needs a modification (see 2nd commit).
orig_pc_offset()
is not available in 17u. We can use theframe
constructor which doesn't have the problematic assertion in 17u (see comment in the new code).So, this backport doesn't fix the assertion mentioned in the title (because it doesn't exist in 17u). But, it makes checks more reliable.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev.git pull/3998/head:pull/3998
$ git checkout pull/3998
Update a local copy of the PR:
$ git checkout pull/3998
$ git pull https://git.openjdk.org/jdk17u-dev.git pull/3998/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 3998
View PR using the GUI difftool:
$ git pr show -t 3998
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/3998.diff
Using Webrev
Link to Webrev Comment