Integrated: 8301996: Move field resolution information out of the cpCache

[Matias Saavedra Silva]

On Wed, 24 May 2023 16:55:47 GMT, Matias Saavedra Silva <matsaave at openjdk.org> wrote:

> The current structure used to store the resolution information for fields, ConstantPoolCacheEntry, is difficult to interpret due to its ambigious fields f1 and f2. This structure can hold information for fields and methods and each of its fields can hold different types of values depending on the entry type.
> 
> This enhancement introduces a new data structure that stores the necessary resolution data in an intuitive an extensible manner. These resolved entries are stored in an array inside the constant pool cache in a very similar manner to invokedynamic entries in JDK-8301995.
> 
> Instances of ConstantPoolCache entry related to field resolution have been replaced with the new ResolvedFieldEntry. Verified with tier 1-9 tests. 
> 
> This change supports the following platforms: x86, aarch64, PPC. and RISCV

This pull request has now been integrated.

Changeset: 86783b98
Author:    Matias Saavedra Silva <matsaave at openjdk.org>
URL:       https://git.openjdk.org/jdk/commit/86783b985175de3a0c02215a862b2a2749d8b408
Stats:     1454 lines in 45 files changed: 908 ins; 171 del; 375 mod

8301996: Move field resolution information out of the cpCache

Co-authored-by: Gui Cao <gcao at openjdk.org>
Co-authored-by: Dingli Zhang <dzhang at openjdk.org>
Co-authored-by: Martin Doerr <mdoerr at openjdk.org>
Reviewed-by: coleenp, fparain

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

PR: https://git.openjdk.org/jdk/pull/14129