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
8271309: [lworld] FieldModification event: new_value is invalid for Q objects #499
Conversation
|
@alexmenkov 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 31 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 (@fparain) but any other Committer may sponsor as well.
|
Webrevs
|
Hi Alex,
Thank you for fixing this. Overall, looks good to me.
Many of the tests related to the FieldModification event are still not working (they are commented with a KNOWN ISSUE comment) because the withfield bytecode still doesn't support JVMTI FieldModification event. Do you have a CR to track this issue?
Regards,
Fred
|
||
// For FieldModification event print current value. | ||
// Note: this will cause FieldAccess event. | ||
if (modified) { |
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.
It would be cleaner to have modified be declared as a bool, or to re-write the test to modified == 1.
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.
Many of the tests related to the FieldModification event are still not working (they are commented with a KNOWN ISSUE comment) because the withfield bytecode still doesn't support JVMTI FieldModification event. Do you have a CR to track this issue?
Filed JDK-8271355
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.
It would be cleaner to have modified be declared as a bool, or to re-write the test to modified == 1.
C-style detected :)
Will fix it.
Thank you for the changes. |
/integrate |
@alexmenkov |
@fparain could you please sponsor the fix |
/sponsor |
Going to push as commit 1282380.
Your commit was automatically rebased without conflicts. |
@MrSimms @alexmenkov Pushed as commit 1282380. |
The fix adds handling of Q-type fields the same way as L-type
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/valhalla pull/499/head:pull/499
$ git checkout pull/499
Update a local copy of the PR:
$ git checkout pull/499
$ git pull https://git.openjdk.java.net/valhalla pull/499/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 499
View PR using the GUI difftool:
$ git pr show -t 499
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/valhalla/pull/499.diff