Latest mlvm giving me trouble with +EnableMethodHandles

[Frank Wierzbicki]

When I try to use the latest mlvm (with guard="buildable testable") -- I get

Unrecognized VM option '+EnableMethodHandles'

My command line looks like:

java -XX:+EnableMethodHandles -XX:+EnableInvokeDynamic -classpath . FidgetDemo

which works for my old build. The current build does javac just fine
with -XDinvokedynamic

Here are the patches I have applied for hotspot and jdk:

$ cd hotspot; hg qapplied
6833129.patch
6873116.patch
meth-6862576.patch
nonperm-6863023.patch
meth-6815692.patch
indy-6858164.patch
meth.walker.patch
indy.compiler.patch

$ cd ../jdk; hg qapplied
indy.tests.patch
indy.pack.patch
indy.patch

$cd ../langtools; hg qapplied
meth.patch

-Frank

[Frank Wierzbicki]

On Wed, Aug 26, 2009 at 1:16 PM, Frank Wierzbicki<fwier...@gmail.com> wrote:
> When I try to use the latest mlvm (with guard="buildable testable") -- I get
>
> Unrecognized VM option '+EnableMethodHandles'

On #mlvm, twisti (Christian Thalinger) answered my question:

You need to use -XX:+UnlockExperimentalVMOptions

jrose changed the options to experimental ones with the last commit.

I'm back on track.

Thanks again Christian!

-Frank

[Rémi Forax]

EnableMethodHandles (and EnableInvokeDynamic) are now marked as
experimental.

in vm/runtime/globals.hpp:
experimental(bool, EnableInvokeDynamic, false, \
"recognize the invokedynamic
instruction") \
experimental(bool, EnableMethodHandles, false, \
"support method handles (true by default under JSR
292)") \

Use -XX:+UnlockExperimentalVMOptions to unlock these options.

BTW, EnableInvokeDynamic implies EnableMethodHandles so you can
only set EnableInvokeDynamic.

Rémi

[Frank Wierzbicki]

On Wed, Aug 26, 2009 at 4:41 PM, Rémi Forax<fo...@univ-mlv.fr> wrote:
> BTW, EnableInvokeDynamic implies EnableMethodHandles so you can
> only set EnableInvokeDynamic.

Great, I'll strip out the EnableMethodHanldes.

Thanks,

-Frank