-
Notifications
You must be signed in to change notification settings - Fork 738
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
Test-sanity.functional-JDK12-linux_x86-64 jsr335_interfacePrivateMethod_mode100_0 VerifyError: JVMCFRE116 invoke bytecode must reference a Methodref #5107
Comments
This must be caused by either #5073 or #5067. The failure is not occurring in jdk8 or jdk11, only in the 0.13 branch testing. |
Agreed - both of our changes take place long after verification. Mine does have to do with interfaces. Is this possibly related to allowing invoke bytecodes other than invokeinterface to target InterfaceMethodRef? Saw this in the report associated with my change, but we clearly allowed invokestatic of InterfaceMethodRef in that case - perhaps we shouldn't? |
I had a build with recent |
My best theory is that the path taken for defining proxies isn't given the exemptions it needs in jdk12; in past versions, proxies were defined via Unsafe which granted many exemptions. |
https://ci.eclipse.org/openj9/job/Test-sanity.functional-JDK12-linux_x86-64/24 Note this fails consistently, but only on the 64-bit (not compressed refs) build. |
That's just because the test is only configured to run in mode 100 ( |
https://ci.eclipse.org/openj9/job/Test-sanity.functional-JDK12-linux_x86-64/22
The text was updated successfully, but these errors were encountered: