Skip to content

8356942: invokeinterface Throws AbstractMethodError Instead of IncompatibleClassChangeError #26122

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

Closed
wants to merge 4 commits into from

Conversation

dholmes-ora
Copy link
Member

@dholmes-ora dholmes-ora commented Jul 3, 2025

In JDK-8186092 (way back in JDK 10) we elided loader constraint checks for overpass methods related to default methods by skipping them when initializing the itable for the interface. But that was the wrong place to do that. The overpass method is setup when there is a resolution/selection error so that the correct exception is thrown if the problematic method is invoked (like the ICCE reporting conflicting methods) and by eliding that entry we instead get the AbstractMethhodError.

The fix here is to revert that change from JDK-8186092, and to address the loader constraint problem by adding the same check for overpass methods in klassItable::check_constraints that exists for klassVtable::check_constraints.

Testing:

  • modified existing regression test
  • tiers 1-4

EDIT: originally there was a new regression test for this, but this area is already covered by the vmTestBase "defmeth tests. That test was missing the necessary invocation modes to expose the bug, so they have been added.

Thanks

PS. The diff is much smaller if you disable whitespace differences.


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Warning

 ⚠️ Found leading lowercase letter in issue title for 8356942: invokeinterface Throws AbstractMethodError Instead of IncompatibleClassChangeError

Issue

  • JDK-8356942: invokeinterface Throws AbstractMethodError Instead of IncompatibleClassChangeError (Bug - P3)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/26122/head:pull/26122
$ git checkout pull/26122

Update a local copy of the PR:
$ git checkout pull/26122
$ git pull https://git.openjdk.org/jdk.git pull/26122/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 26122

View PR using the GUI difftool:
$ git pr show -t 26122

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/26122.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Jul 3, 2025

👋 Welcome back dholmes! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Jul 3, 2025

@dholmes-ora 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:

8356942: invokeinterface Throws AbstractMethodError Instead of IncompatibleClassChangeError

Reviewed-by: coleenp, iklam

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 229 new commits pushed to the master branch:

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 master branch, type /integrate in a new comment.

@openjdk openjdk bot added the rfr Pull request is ready for review label Jul 3, 2025
@openjdk
Copy link

openjdk bot commented Jul 3, 2025

@dholmes-ora The following label will be automatically applied to this pull request:

  • hotspot

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.

@dholmes-ora dholmes-ora changed the title 8356942: invokeinterface Throws AbstractMethodError Instead of IncompatibleClassChangeError 8356942: invokeinterface Throws AbstractMethodError Instead of IncompatibleClassChangeError Jul 3, 2025
@dholmes-ora
Copy link
Member Author

/label add hotspot-runtime

@openjdk
Copy link

openjdk bot commented Jul 3, 2025

@dholmes-ora
The hotspot-runtime label was successfully added.

@mlbridge
Copy link

mlbridge bot commented Jul 3, 2025

Webrevs

…the invokeinterface variants of the

test scenario. Also updated all tests therein to use `throwsExact` so that the wrong kind of ICCE does not
cause the test to pass by mistake.
Copy link
Contributor

@coleenp coleenp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Still so many questions...

Copy link
Contributor

@coleenp coleenp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Jul 8, 2025
@dholmes-ora
Copy link
Member Author

Thanks for the review @coleenp !

Copy link
Member

@iklam iklam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes look reasonable to me.

@dholmes-ora
Copy link
Member Author

Thanks for the review @iklam !

/integrate

@openjdk
Copy link

openjdk bot commented Jul 14, 2025

Going to push as commit f36147b.
Since your change was applied there have been 229 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Jul 14, 2025
@openjdk openjdk bot closed this Jul 14, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Jul 14, 2025
@openjdk
Copy link

openjdk bot commented Jul 14, 2025

@dholmes-ora Pushed as commit f36147b.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

@dholmes-ora dholmes-ora deleted the 8356942-invokeintf branch July 15, 2025 00:17
@dholmes-ora
Copy link
Member Author

/backport jdk jdk25

@openjdk
Copy link

openjdk bot commented Jul 15, 2025

@dholmes-ora the backport was successfully created on the branch backport-dholmes-ora-f36147b3-jdk25 in my personal fork of openjdk/jdk. To create a pull request with this backport targeting openjdk/jdk:jdk25, just click the following link:

➡️ Create pull request

The title of the pull request is automatically filled in correctly and below you find a suggestion for the pull request body:

Hi all,

This pull request contains a backport of commit f36147b3 from the openjdk/jdk repository.

The commit being backported was authored by David Holmes on 14 Jul 2025 and was reviewed by Coleen Phillimore and Ioi Lam.

Thanks!

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/jdk:

$ git fetch https://github.com/openjdk-bots/jdk.git backport-dholmes-ora-f36147b3-jdk25:backport-dholmes-ora-f36147b3-jdk25
$ git checkout backport-dholmes-ora-f36147b3-jdk25
# make changes
$ git add paths/to/changed/files
$ git commit --message 'Describe additional changes made'
$ git push https://github.com/openjdk-bots/jdk.git backport-dholmes-ora-f36147b3-jdk25

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants