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
8252881: [JVMCI] ResolvedJavaType.resolveMethod fails in fastdebug when invoked with a constructor #407
Conversation
…en invoked with a constructor
|
Webrevs
|
@dougxc 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 24 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.
|
/integrate |
@dougxc Since your change was applied there have been 25 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 424d7d6. |
@dougxc Can you explain why changes in TestResolvedJavaType.java test were not ported? |
Oversight. I'll fix this now. |
This change prevents a call to
CompilerToVM.resolveMethod
with an argument representing a constructor. Such a call triggers an assertion in a fastdebug VM.Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/407/head:pull/407
$ git checkout pull/407