Long-term maintenance of verifier

[Chen Liang]

Hello,
I have noted that the classfile API's copy of migrated verifier seems to
naturally diverge from the c++ code: for example, JDK-8350029 that
restricts invokespecial to not allow invoking arbitrary interface methods
is not shadowed to the classfile verifier. This problem will only get more
serious once strict fields are added. Meanwhile, people expect
ClassFile.verify to be up-to-date with the runtime verifier.

What should we do to resolve this discrepancy? Should we have a separately
maintained Java-based verifier implementing JVMS 4.10, or should we just
increase our frequency of synchronizing with runtime?

Regards,
Chen Liang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/classfile-api-dev/attachments/20250606/df3fc75c/attachment.htm>