-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8341444: Unnecessary check for JSRs in CDS #21330
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 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 359 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 |
|
@matias9927 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
|
dholmes-ora
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.
Again apologies for commenting and running off on vacation, but this one does not look right to me based on the description.
| if (len == 0) len = Bytecodes::length_at(_method(), bcp); | ||
| if (len <= 0 || (_bci > _end_bci - len) || (_bci - len >= _next_bci)) { | ||
| raw_code = code = Bytecodes::_illegal; | ||
| fatal("Should have been caught by verifier"); |
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.
Verification may be disabled, This may be a risky change in behaviour.
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.
If verification is disabled, this fatal is better than what might come next. But there may be callers now or in the future that check for Bytecodes::_illegal, so I don't think we should have this assert even though we don't have any code that hits it.
| // don't have any methods share the Universe::_the_empty_method_array which is in the RO region. | ||
| if (_methods != nullptr && _methods->length() > 0 && | ||
| !can_be_verified_at_dumptime() && methods_contain_jsr_bytecode()) { | ||
| if (_methods != nullptr && _methods->length() > 0 && !can_be_verified_at_dumptime()) { | ||
| // To handle jsr bytecode, new Method* maybe stored into _methods |
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.
Based on the comment we only need to do this if the method does contain a JSR bytecode - now we will do it for all cases where verification can't be done at dumptime. ??
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.
Yes, we will put these in RW space the time. Using the BytecodeStream to look for JSRs in unverified code is risky, so we avoid doing this optimization.
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.
So shouldn't the comment be updated to indicate that we cannot safely check if the jsr bytecode exists and so all methods that can't be verified are made writeable?
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 think you should take out the 'fatal' error in bytecodeStream.
| if (len == 0) len = Bytecodes::length_at(_method(), bcp); | ||
| if (len <= 0 || (_bci > _end_bci - len) || (_bci - len >= _next_bci)) { | ||
| raw_code = code = Bytecodes::_illegal; | ||
| fatal("Should have been caught by verifier"); |
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.
If verification is disabled, this fatal is better than what might come next. But there may be callers now or in the future that check for Bytecodes::_illegal, so I don't think we should have this assert even though we don't have any code that hits it.
| // don't have any methods share the Universe::_the_empty_method_array which is in the RO region. | ||
| if (_methods != nullptr && _methods->length() > 0 && | ||
| !can_be_verified_at_dumptime() && methods_contain_jsr_bytecode()) { | ||
| if (_methods != nullptr && _methods->length() > 0 && !can_be_verified_at_dumptime()) { | ||
| // To handle jsr bytecode, new Method* maybe stored into _methods |
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.
Yes, we will put these in RW space the time. Using the BytecodeStream to look for JSRs in unverified code is risky, so we avoid doing this optimization.
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.
This looks good.
dholmes-ora
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.
Thank you!
|
Thanks for the reviews @dholmes-ora and @coleenp! |
|
Going to push as commit 28252bb.
Your commit was automatically rebased without conflicts. |
|
@matias9927 Pushed as commit 28252bb. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/21330/head:pull/21330$ git checkout pull/21330Update a local copy of the PR:
$ git checkout pull/21330$ git pull https://git.openjdk.org/jdk.git pull/21330/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 21330View PR using the GUI difftool:
$ git pr show -t 21330Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/21330.diff
Webrev
Link to Webrev Comment