dropArguments still NYI?
Charles Oliver Nutter
charles.nutter at sun.com
Fri May 29 09:29:35 PDT 2009
I saw jrose land a dropArguments fix a day or two ago, but it still
seems to be coming up NYI for me:
~/projects/jruby ➔ JAVA_HOME=$MLVM_HOME JAVA_OPTS=$INDY_OPTS jruby -d -e
"puts 1"
could not compile: -e because of: "null"
java.lang.ExceptionInInitializerError
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:186)
at
org.jruby.compiler.impl.StandardASMCompiler.<clinit>(StandardASMCompiler.java:127)
at org.jruby.Ruby.tryCompile(Ruby.java:536)
at org.jruby.Ruby.tryCompile(Ruby.java:524)
at org.jruby.Ruby.runNormally(Ruby.java:505)
at org.jruby.Ruby.runFromMain(Ruby.java:361)
at org.jruby.Main.run(Main.java:268)
at org.jruby.Main.run(Main.java:113)
at org.jruby.Main.main(Main.java:97)
Caused by: java.lang.UnsupportedOperationException: NYI
at sun.dyn.MethodHandleImpl.dropArguments(MethodHandleImpl.java:301)
at java.dyn.MethodHandles.dropArguments(MethodHandles.java:1021)
at
org.jruby.runtime.invokedynamic.InvokeDynamicSupport.<clinit>(InvokeDynamicSupport.java:388)
Here's the code in syn/dyn/MethodHandleImpl.java:
public static
MethodHandle dropArguments(Access token, MethodHandle target,
MethodType newType, int argnum) {
Access.check(token);
throw new UnsupportedOperationException("NYI");
}
I certainly could have things applied incorrectly, but I could find no
updates to MethodHandleImpl.java in patches/jdk/indy.patch
- Charlie
More information about the mlvm-dev
mailing list