RFR JDK-8182678: add javac and method handle support for mangled value class names in CONSTANT_ClassInfo
paul.sandoz at oracle.com
Fri Jun 23 17:15:42 UTC 2017
> On 22 Jun 2017, at 09:52, Maurizio Cimadamore <maurizio.cimadamore at oracle.com> wrote:
> On 22/06/17 17:36, Paul Sandoz wrote:
>>> On 22 Jun 2017, at 04:35, Maurizio Cimadamore <maurizio.cimadamore at oracle.com> wrote:
>>> On 22/06/17 02:22, Paul Sandoz wrote:
>>>> Looks good, although it would be nice if the javac and java properties were the same name as it’s hard to remember the plethora of such properties that are available.
>>> Sure - note that I tried to use the same name - but the javac convention is not to use any qualified name for options, while it seems like all the MVT-related options in the JDK starts off with 'valhalla.' - which is why I landed there, as the option name is kind of the same (mangleClassInfo is contained in both), and the scheme is consistent with both javac and jdk unwritten rules.
>>> That said, if you think it's too confusing, I can change it no problem.
>> Thinking more, my objection is really that i don’t have a holistic view of all the possible flags for javac, and hotspot.
>> It would be useful if we have a page somewhere listing all such flags with a small description. We cold use a dummy issue and edit the description?
> Sounds like a good idea - flags always introduce a certain non-determinism to the dev experience; any attempt to keep them under check is welcome on my part ;-)
I’ll start another thread on this.
More information about the valhalla-dev