JDK-7088481 : JSR 292: remove the vm specific fields from the java.lang.invoke classes
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 8
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: solaris_10
  • CPU: x86
  • Submitted: 2011-09-08
  • Updated: 2013-06-17
  • Resolved: 2013-06-14
Related Reports
Relates :  
JDK-7086585 - make Java field injection more flexible
Relates :  
JDK-7023639 - JSR 292 method handle invocation needs a fast path for compiled code
Description
There are many vm specific fields declared in the java.lang.invoke classes that would be better injected by the JVM as needed.  Once the support for injecting them is in these should all be removed from the JDK code.  That bug is 7086585.
Comments
The following change set got rid of JVM-entangled fields vmentry, vmtarget, vmindex, vmargslot, vmlayout: changeset: 5574:050116960e99 user: twisti date: Tue Jul 24 10:47:44 2012 -0700 summary: 7023639: JSR 292 method handle invocation needs a fast path for compiled code The remaining fields like these are: MethodTypeForm.vmslots -- simple int, not used by JVM LambdaForm.vmentry -- a MemberName carrying an injected metadata pointer, used by JVM stub for invokeBasic The intention of this bug report was fulfilled by JDK-7023639.
14-06-2013