Integrated: 8358580: Rethink how classes are kept alive in training data

Igor Veresov iveresov at openjdk.org
Fri Jul 11 18:09:59 UTC 2025


On Thu, 10 Jul 2025 02:37:05 GMT, Igor Veresov <iveresov at openjdk.org> wrote:

> Use OopStorage directly instead of JNI handles. Note that we never destroy TrainingData objects, so we don't need to concern ourselves with freeing the OopStorage entries. Also, keeping the klasses alive is only necessary during the training run. During the replay the klasses TD objects refer to are always alive.

This pull request has now been integrated.

Changeset: 59bec29c
Author:    Igor Veresov <iveresov at openjdk.org>
URL:       https://git.openjdk.org/jdk/commit/59bec29c35361b7b256a2d435ced3458b0c5ea58
Stats:     7 lines in 2 files changed: 1 ins; 3 del; 3 mod

8358580: Rethink how classes are kept alive in training data

Reviewed-by: coleenp, shade

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

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


More information about the hotspot-dev mailing list