We are currently testing JSR292 (invoke dynamic) changes that require
the hotspot and jdk repos to be in sync. If testing goes well we will
integrate the changes into the jdk8 master[1] this coming Wednesday,
Aug 15. Once the changes have been integrated, the hotspot and jdk
repos must match - i.e., either both must have the JSR292 changes or
both must not have them.
A JDK with mismatched repos may build but will not be able to handle
invoke dynamics appropriately, and will fail with a message similar to this:
$ java -showversion -Xbootclasspath/p:$PWD/classes
-XX:+UnlockDiagnosticVMOptions -XX:+EnableInvokeDynamic
Invalid layout of java.lang.invoke.MemberName at vmindex
In particular, users of JPRT who have pulled the changes must build
*both* hotspot and jdk until the JSR292 changes are in a promoted
jdk8 build (expected Thu, Aug 16).
After we integrate, the simplest coping strategy is to avoid pulling
from the jdk8 master repo until the next jdk8 build is promoted.
If you do pull, make sure to pull both hotspot and jdk, and to build both.
[1] http://hg.openjdk.java.net/jdk8/jdk8
--
Alejandro E Murillo, Java Performance
Phone: (303) 955-2584.
Timezone: US/Mountain (UTC-0700)
