[native-image] Groovy closure coercion to functional interface throws UnsupportedFeatureException: Invoke with MethodHandle argument could not be reduced to at most a single call: java.lang.invoke.MethodHandle.bindTo(Object) #1306
Assignees
Labels
Comments
|
I just ran into this with Scala closures/lambdas. |
|
UPDATE: I can confirm that using the OpenJDK 11 variant of GraalVM CE 20.2.0 compiles to the native image and it works as expected. (I tested both Groovy 3.0.5 and Groovy 2.5.10.) The OpenJDK 8u262 one fails at the compilation with the same error as mentioned above. |
|
Thanks for the detailed reproducible. The underlying issue here is incomplete |
dmurat
added a commit
to croz-ltd/klokwrk-project
that referenced
this issue
Jan 3, 2021
It turns out that GraalVM JDK 8 version (sdkman version: 20.3.0.r8-grl) works. Previously I had a constraint because of oracle/graal#1306 Obviously it is fixed in Graal 20.3.0 version which also is suggested in release notes (https://www.graalvm.org/release-notes/20_3/#native-image) in the entry starting with "Added support for method handles that represent a call to a single method accessible by the Reflection API".
dmurat
added a commit
to croz-ltd/klokwrk-project
that referenced
this issue
Jan 24, 2021
It turns out that GraalVM JDK 8 version (sdkman version: 20.3.0.r8-grl) works. Previously I had a constraint because of oracle/graal#1306 Obviously it is fixed in Graal 20.3.0 version which also is suggested in release notes (https://www.graalvm.org/release-notes/20_3/#native-image) in the entry starting with "Added support for method handles that represent a call to a single method accessible by the Reflection API".
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Affected version: GraalVM CE 19.0.0
Context: Native image generation fails when we use a Groovy closure in place of a functional interface (or single abstract method class). This is one of the most popular Groovy idioms which allows us to put a closure in place of a Java's lambda expression (Groovy 2.x parser does not support lambda expressions). The simple example may look like this:
In this example, we pass a closure
{ int n -> n > 10 }in place of aIntPredicatefunctional interface. The bytecode generated from that Groovy code looks like this after decompiling to the Java code:This class was compiled with the static compilation enabled.
Code sample: https://github.com/wololock/graalvm-groovy-closures
How to reproduce:
The
build-native-image.shlooks like this:After running
shadowJartask, Gradle runs the application from generated JAR file using GraalVM'snative-image-agentto generate a reflection configuration file inconfig/native-imagefolder, and it removesjava.lang.reflect.Executablefrom JSON file as explained in #1260Native image generation fails with the following output:
Cédric Champeau (the author of Groovy static compiler) documented this issue on his blog some time ago - https://melix.github.io/blog/2019/03/simple-http-server-graal.html I'm posting it here so you can get a better context.
Anonymous classes
You can also find a use case with anonymous classes in the sample Groovy code. Using an anonymous class in place of the closure compiles to the native image. The bytecode of a Groovy class using an anonymous class instead of a closure decompiled to the Java looks like this:
And here is the log of compiling and running the example with an anonymous class instead of a closure.
It feels like this use case should be supported by the native image generation. Maybe supporting Groovy closures in this context requires some subtraction using SubstrateVM SDK? I can run some experiments, but I would need some guidance on where to start.
Thanks in advance!
The text was updated successfully, but these errors were encountered: