JDK-8173977 : Unify access checks or make lookup mode available to VM
  • Type: Enhancement
  • Component: core-libs
  • Sub-Component: java.lang.invoke
  • Priority: P3
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2017-02-06
  • Updated: 2019-07-26
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.
Other
tbd_majorUnresolved
Related Reports
Relates :  
JDK-8228671 - Fastdebug VM throws InternalError when publicLookup.in(T) is used to resolve a member
Description
The introduction of Lookup.UNCONDITIONAL means that access checking in the VM is no longer 100% aligned with the access checking in java.lang.invoke. This arises because the VM doesn't have the lookup mode and so can't distinguish a caller/accessor that is java.lang.Object from an access check creating a method handle with publicLookup().

This issue is created to re-examine this area, maybe to see if the access checking should be unified or else provide the lookup mode to the VM so that it can be used by the LinkResolver.