-
Notifications
You must be signed in to change notification settings - Fork 6.1k
JDK-8310425: [JVMCI] compiler/runtime/TestConstantDynamic: lookupConstant returned an object of incorrect type: null #14582
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
…icConstant in error.
|
👋 Welcome back davleopo! A progress list of the required criteria for merging this PR into |
|
@davleopo 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 72 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 (@dougxc, @tkrodriguez) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
|
/integrate |
|
/sponsor |
|
Going to push as commit 1587836.
Your commit was automatically rebased without conflicts. |
Fix JVMCI handling of null dynamic constants and dynamic constant errors.
For null dynamic constants, the JVMCI code was checking for
Universe::the_null_sentinelbutConstantPool::resolve_possibly_cached_constant_atreturnsnullptrfor null constants.In the case of errors thrown by a bootstrap method,
ConstantPool::resolve_possibly_cached_constant_atalready propagates theBootstrapMethodErrorso there's no need to check fortag.is_dynamic_constant_in_error().Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/14582/head:pull/14582$ git checkout pull/14582Update a local copy of the PR:
$ git checkout pull/14582$ git pull https://git.openjdk.org/jdk.git pull/14582/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 14582View PR using the GUI difftool:
$ git pr show -t 14582Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/14582.diff
Webrev
Link to Webrev Comment