-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8261846: [JVMCI] c2v_iterateFrames can get out of sync with the StackFrameStream #2594
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
Conversation
|
👋 Welcome back never! A progress list of the required criteria for merging this PR into |
|
@tkrodriguez 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
|
vnkozlov
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.
Update copyright year in vframe.hpp.
Otherwise good.
|
@tkrodriguez 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 26 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 Tom. This code could be simplified and made faster using vframeStream as the iterator and vframeStream:asJavaVFrame to get the vframe. If you don't need the locals of every frame, then vframeStream::next is faster than vframe::sender. See JDK-8214329. |
|
@dean-long I think it would be possible to rewrite this to use vframeStream though it would still need to build vframes because of the introspection it does on compiled frames. It would be a major rewrite though and in general this code is working just fine so I don't think I want to tackle that. |
|
Looks good to me. |
|
@tkrodriguez OK, I filed a separate RFE for my suggestion. |
|
/integrate |
|
@tkrodriguez Since your change was applied there have been 26 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 97e1657. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
c2v_iterateFrames mixes a StackFrameSteam and vframes and the vframe factory method can silently skip stub frames. The could leave the StackFrameStream out of sync with the vframe walk. This can cause the iteration fail in strange ways and assert in fastdebug builds.
Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/2594/head:pull/2594$ git checkout pull/2594