-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8314508: Improve how relativized pointers are printed by frame::describe #18102
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
8314508: Improve how relativized pointers are printed by frame::describe #18102
Conversation
|
👋 Welcome back fbredberg! A progress list of the required criteria for merging this PR into |
Webrevs
|
coleenp
left a comment
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 don't know this code that well but I had a couple of questions.
coleenp
left a comment
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.
Ok, this looks good. Thank you for the explanation. I had a couple of comment ideas that might make it make sense without reading the whole file.
|
@fbredber 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 109 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. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@coleenp, @pchilano) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
pchilano
left a comment
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.
Not a fan of printing a value that differs from the real one but I like that we still get it directly from the new description you added.
I see that we cannot do this derelativization for the fp of a heap frame since to know if it was actually relativized we need the caller frame info to check if it's interpreted.
|
Thanks for the review. |
|
/integrate |
|
/sponsor |
|
Going to push as commit 0db6231.
Your commit was automatically rebased without conflicts. |
The output from frame::describe has been improved so that it now prints the actual derelativized pointer value, regardless if it's on the stack or on the heap. It also clearly shows which members of the fixed stackframe are relativized. See sample output of a riscv64 stackframe below:
The output is was created by running
test/jdk/jdk/internal/vm/Continuation/Basic.javawith-Xlog:continuations=trace:frbr_log.txt.Output has been reviewed for x64, aarch64, ppc64le and riscv64.
The changes also passes tier1-tier5.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/18102/head:pull/18102$ git checkout pull/18102Update a local copy of the PR:
$ git checkout pull/18102$ git pull https://git.openjdk.org/jdk.git pull/18102/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 18102View PR using the GUI difftool:
$ git pr show -t 18102Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/18102.diff
Webrev
Link to Webrev Comment