RFR: JDK-8136893: Improve early java.lang.invoke infrastructure initialization (original) (raw)
Paul Sandoz paul.sandoz at oracle.com
Tue Oct 13 11:47:35 UTC 2015
- Previous message: RFR: JDK-8136893: Improve early java.lang.invoke infrastructure initialization
- Next message: RFR: JDK-8136893: Improve early java.lang.invoke infrastructure initialization
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 13 Oct 2015, at 13:26, Claes Redestad <claes.redestad at oracle.com> wrote:
Thus it seems fixMethodType is not necessary. I think this is confirmed when looking at up calls to linkMethodHandleConstant and linkCallSite. +1 - this should be a separate cleanup, though.
Yes.
The reasoning is as follows: if callerClass.getClassLoader() is sufficient for resolving types that appear at the call site in a non-bootstrap callerClass, then bootstrap classloader should be sufficient to resolve types that appear at the call site in a bootstrap callerClass. Does anybody have any other opinion?
- sun.invoke.util.BytecodeDescriptor#parseMethod(java.lang.String, java.lang.ClassLoader) is only used from the newly introduced java.lang.invoke.MethodType#fromDescriptor Ok, i think you have things covered, thanks, I believe you meant "Ship it!"? :-)
Indeed!
Paul.
- Previous message: RFR: JDK-8136893: Improve early java.lang.invoke infrastructure initialization
- Next message: RFR: JDK-8136893: Improve early java.lang.invoke infrastructure initialization
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]