On Tue, 30 Jun 2026 16:58:47 GMT, Alan Bateman <[email protected]> wrote:
> JVMTI ForceEarlyReturnVoid can be used to return early from a constructor or > class initializer. Early return from a constructor with strictly-initialized > instance fields is problematic, as is early return from a class initializer > when there are strictly-initialized static fields. The proposal for the > initial integration is to keep it simple and just disallow > ForceEarlyReturnVoid to return early from a value class constructor. > > --------- > - [x] I confirm that I make this contribution in accordance with the [OpenJDK > Interim AI Policy](https://openjdk.org/legal/ai). This pull request has now been integrated. Changeset: 6adeca93 Author: Alan Bateman <[email protected]> Committer: David Holmes <[email protected]> URL: https://git.openjdk.org/valhalla/commit/6adeca933a1361c6f44f51c9c266bd1a20a42380 Stats: 337 lines in 5 files changed: 333 ins; 0 del; 4 mod 8387540: [lworld] ForceEarlyReturnVoid should fail with OPAQUE_FRAME if target thread's top frame is value class constructor Reviewed-by: sspitsyn ------------- PR: https://git.openjdk.org/valhalla/pull/2604
