hg: mlvm/mlvm/hotspot: meth-conv: fixes for LP64

Changeset: f48f569485ff Author:jrose Date: 2011-04-15 13:32 -0700 URL: http://hg.openjdk.java.net/mlvm/mlvm/hotspot/rev/f48f569485ff meth-conv: fixes for LP64 ! meth-conv-6939861.patch ___ mlvm-dev mailing list mlvm-dev@openjdk.java.net

hg: mlvm/mlvm/hotspot: meth-conv: more fixes for compressed oops

Changeset: 51ec35404c88 Author:jrose Date: 2011-04-15 10:01 -0700 URL: http://hg.openjdk.java.net/mlvm/mlvm/hotspot/rev/51ec35404c88 meth-conv: more fixes for compressed oops ! meth-conv-6939861.patch ___ mlvm-dev mailing list mlvm-dev@o

Re: Are there restrictions on the 'name' string for invokeDynamic?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-04-15 02.25, Mark Roos wrote: > I ran into this error today and was wondering if "<" was not allowed as > the name string for an invokeDynamic instruction? > > An if there are restrictions where might I find the definitive > reference? I was

Are there restrictions on the 'name' string for invokeDynamic?

I ran into this error today and was wondering if "<" was not allowed as the name string for an invokeDynamic instruction? An if there are restrictions where might I find the definitive reference? I was using it for the Smalltalk method name and as a template for constants. Thanks mark java.l