JDK-8026478 : -XX:+VerifyAdapterSharing is broken
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: hs25
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2013-10-15
  • Updated: 2014-07-29
  • Resolved: 2013-12-19
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
8u20Fixed 9 b02Fixed
Related Reports
Relates :  
This flag is broken. The reason is that adapters (gen_i2c_adapter()) that are generated during VM startup do not include the range for StubRoutines::code2() if -XX:+VerifyAdapterCalls is specified. StubRoutines::code2() is only allocated later during startup;  consequently, code2() is NULL. As a result, the size of the generated adapter as well as the code itself does not mactch.
http://openjdk.java.net/guide/changePlanning.html article 6. '-sqe Change can be verified by running an existing SQE test suite; the bug should identify the suite and the specific test case(s).'

Albert, since you added noreg-sqe, could you please clarify which sqe-tests cover this issue?

AFAIK, we don't have such sqe-test. Could you please add that as a regression test (or just file an RFE for it and assign it to me) and remove the label?

Sorry, I forgot about that. java -XX:+VerifyAdapterSharing -version should already trigger the bug.

Further note: The patch also fixes a potential issue with -XX:+VerifyAdapterCalls, which is a diagnostic flag.

Note: 'VerifyAdapterSharing' is develop flag, so it doesn't affect product build.