On Sun, 30 Apr 2023 06:14:28 GMT, Chen Liang wrote:
> Try to intrinsify MethodHandles.arrayConstructor for java.lang,
> java.lang.invoke, and java.util types, which InvokerBytecodeGenerator can
> refer to directly in a class constant.
>
> In fact, the performance difference of Array.newInstanc
On Sun, 30 Apr 2023 21:34:46 GMT, Jorn Vernee wrote:
> What kind of performance improvement are you seeing? Could you add a
> comparison with a method handle that calls `Array::newInstance` bound to the
> array type? (that should have the same performance as the current
> implementation).
Tha
On Sun, 30 Apr 2023 06:14:28 GMT, Chen Liang wrote:
> Try to intrinsify MethodHandles.arrayConstructor for java.lang,
> java.lang.invoke, and java.util types, which InvokerBytecodeGenerator can
> refer to directly in a class constant.
>
> In fact, the performance difference of Array.newInstanc
Try to intrinsify MethodHandles.arrayConstructor for java.lang,
java.lang.invoke, and java.util types, which InvokerBytecodeGenerator can refer
to directly in a class constant.
In fact, the performance difference of Array.newInstance and anewarray is quite
negligible per benchmark:
Benchmark
