-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8323657: Compilation of snippet results in VerifyError at runtime with --release 9 (and above) #17483
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
…h --release 9 (and above)
|
👋 Welcome back jlahoda! A progress list of the required criteria for merging this PR into |
vicente-romero-oracle
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.
lgtm
|
@lahodaj 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 28 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 |
|
/integrate |
|
Going to push as commit c9cacfb.
Your commit was automatically rebased without conflicts. |
|
/backport jdk22u |
|
@lahodaj the backport was successfully created on the branch backport-lahodaj-c9cacfb2 in my personal fork of openjdk/jdk22u. To create a pull request with this backport targeting openjdk/jdk22u:master, just click the following link: The title of the pull request is automatically filled in correctly and below you find a suggestion for the pull request body:
If you need to update the source branch of the pull then run the following commands in a local clone of your personal fork of openjdk/jdk22u: |
Consider code like:
This should print:
but it prints:
The correct semantics can be achieved by using
--source 8:Or
-XDstringConcat=inlinewhen compiling.The reason is that when
StringConcat.IndyConstantsconverts String concatenation parameters, it will short-circuit any expressions whose type is BOT (i.e. basically thenulltype). But, in this case, the expression that has the BOT type is a complex expression with a side-effect, so short-circuiting it leads to a broken semantics.My proposal is to "short-circuit" only
nullliterals, and generate other expressions normally. There may be some corner cases where we'd generate the expression unnecessarily (if it does not have any side-effect), but looking for side-effects seems unnecessarily complex and fragile given I'd expect non-trivial expressions with the BOT type are very rare. (The only case which comes to mind is exactly the above one - a conditional expressions, whose both result values arenull.)Please note that when the expression is incorrectly short-circuited, it may lead to various other effects - the original bug report shows a case where the resulting code does not pass the verification.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/17483/head:pull/17483$ git checkout pull/17483Update a local copy of the PR:
$ git checkout pull/17483$ git pull https://git.openjdk.org/jdk.git pull/17483/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 17483View PR using the GUI difftool:
$ git pr show -t 17483Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/17483.diff
Webrev
Link to Webrev Comment