RFR: Value types consistency checks

[Karen Kinnear]

Frederic,

Many thanks for doing this and doing this so cleanly.

Couple of questions:
1. instanceKlass.cpp: 
  if (has_value_types_attribute) line 632 — does this want to also be if EnableValhalla?
  my understanding is that extra attributes are ignored so classFileParser should just allow them

2. instanceKlass.cpp check_symbol/signature_for_value_types_consistency
  In the array part, did you want to check for “L” or is that just me being over cautious?

3. klassVtable.cpp
In update_inherited_vtable when you override a method (this is the vtable part),
there is a if (check constraints & !targer_method()->is_overpass() - which needs
a declarer/overridder match check. Also in initialize_itable_for_interface under if (check constraints)

4. Thank you for adding the ValueTypes attributes in the class files for the tests.
Did you add any tests that fail consistency?

many thanks,
Karen

> On Jun 28, 2018, at 4:38 PM, Frederic Parain <frederic.parain at oracle.com> wrote:
> 
> Please review this changeset implementing consistency checks based on the
> ValueTypes attribute. These checks ensure that the assumptions a class has
> about value types, as encoded in its ValueTypes attribute, match the
> reality, or the assumptions of another class it links to.
> 
> The details of the consistency checks have been summarized by Karen in
> this document:
> http://cr.openjdk.java.net/~acorn/value-types-consistency-checking-details.pdf
> 
> If the implementation doesn’t match the document, this is likely to be bug,
> so please, report it.
> 
> Some tests using the Bytecodes API have been updated to include a
> ValueTypes attribute in the class files they generate (thanks to Srikanth
> for adding this feature to the Bytecodes API).
> 
> Webrev:
> http://cr.openjdk.java.net/~fparain/VTAttributeChecks/webrev.01/
> 
> Thank you,
> 
> Fred
>