RFR 8187742 Minimal set of bootstrap methods for dynamic constants

[forax at univ-mlv.fr]

> De: "John Rose" <john.r.rose at oracle.com>
> À: "Rémi Forax" <forax at univ-mlv.fr>
> Cc: "Paul Sandoz" <paul.sandoz at oracle.com>, "hotspot-dev"
> <hotspot-dev at openjdk.java.net>, "core-libs-dev"
> <core-libs-dev at openjdk.java.net>
> Envoyé: Mardi 7 Novembre 2017 23:20:01
> Objet: Re: RFR 8187742 Minimal set of bootstrap methods for dynamic constants

> On Nov 7, 2017, at 2:18 PM, [ mailto:forax at univ-mlv.fr | forax at univ-mlv.fr ]
> wrote:

>>>> Also, why it's not called in invoke ?

>>> What “it” are you referring to?

>> validateClassAccess.

> Because having a MH means you have already been granted
> access to invoke it. Having a Class does *not* mean you have
> been granted access to its members; that is a further step.

but here you are using the class to change the mh, so you can have access to the mh and still have no access to the Class if you do not call the BSM with a condy, which is the purpose of validateClassAccess, no ? 

> — John

Rémi