-
Notifications
You must be signed in to change notification settings - Fork 108
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
8343846: [lworld] implement spec changes to stack map tables #1373
Conversation
👋 Welcome back matsaave! A progress list of the required criteria for merging this PR into |
@matias9927 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 331 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, @fparain) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/contributor add @vicente-romero-oracle |
@matias9927 |
Do we require complete ClassFile API support for the spec change immediately? Currently ClassFile support is reading-only, still need some tweaks to support writing the correct assert_unset_fields (either through user-specified or through auto generation) |
Webrevs
|
it would be a nice to have I think but I don't think it is a must as part of this PR. This is still an experimental feature and we don't know what the final version will be, it could even be possible for this feature to be dropped, so |
Sure, we can always add them later. |
if (fd.access_flags().is_strict()) { | ||
ResourceMark rm(THREAD); | ||
if (!current_frame->satisfy_unset_field(fd.name(), fd.signature())) { | ||
log_info(verification)("Attempting to initialize field not found in initial stict instance fields: %s%s", |
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.
typo: stict -> strict
} else if (new_fields->number_of_entries() > 0) { | ||
_prev_frame->verifier()->verify_error( | ||
ErrorContext::bad_strict_fields(_prev_frame->offset(), _prev_frame), | ||
"Cannot have uninitialzied strict fields after class initialization"); |
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.
typo: uninitialzied -> uninitialized
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.
This looks really good! I have a few comment and name suggestions, and was wondering if your Hashtable could be <NameAndSig, bool> where satisfied is the value?
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.
This looks really good, and the design fits very nicely with the work of the verifier in verifying stackmap tables. I reviewed the Hotspot changes.
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.
LGTM. Nice integration with the verifier code.
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.
The language and tooling changes look fine.
Thank you for the discussions and review @coleenp @fparain and @liach! Also thank you @vicente-romero-oracle for the javac component! |
@matias9927 |
/sponsor |
@fparain Only the author (@matias9927) is allowed to issue the |
Going to push as commit 7a1ff29.
Your commit was automatically rebased without conflicts. |
@fparain @matias9927 Pushed as commit 7a1ff29. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This patch implements the spec changes needed to realize the ACC_STRICT flag. See the JBS issue for more details.
The patch is divided across 3 major commits:
Verified with tier 1-3 tests
Progress
Issue
Reviewers
Contributors
<vromero@openjdk.org>
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/valhalla.git pull/1373/head:pull/1373
$ git checkout pull/1373
Update a local copy of the PR:
$ git checkout pull/1373
$ git pull https://git.openjdk.org/valhalla.git pull/1373/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 1373
View PR using the GUI difftool:
$ git pr show -t 1373
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/valhalla/pull/1373.diff
Using Webrev
Link to Webrev Comment