[lworld] RFR: 8275606: [lworld] ClassInitializationFailuresTest triggers assert with -XX:-UseTLAB

[Frederic Parain]

On Wed, 27 Oct 2021 16:19:03 GMT, Frederic Parain <fparain at openjdk.org> wrote:

> Please review those small changes fixing the handling of values with a class that failed to initialized properly.
> Changes in the test file are only code formatting.
> Tested with Mach5, tiers 1 to 3.
> 
> Thank you,
> 
> Fred

Classes that failed their initialization is a corner case that adds a lot of complexity.
During initialization, a class should be able to create instances of itself, but once the class is in an initialization error state, no more new instance creation should be allowed (impacts new arrays and withfield). Regarding accesses to instances that escaped during the class initialization, I've tried to align the behavior with the current behavior of identity classes: if an instance has been created, it is legal to access its fields, even if the class itself failed to successfully initialize.

Thank you for the review.

-------------

PR: https://git.openjdk.java.net/valhalla/pull/574