Re: RFR: 8293980: Resolve CONSTANT_FieldRef at CDS dump time [v3]

2024-05-29 Thread Dan Heidinga
On Sat, 25 May 2024 06:48:26 GMT, Ioi Lam wrote: >> ### Overview >> >> This PR archives `CONSTANT_FieldRef` entries in the _resolved_ state when >> it's safe to do so. >> >> I.e., when a `CONSTANT_FieldRef` constant pool entry in class `A` refers to >> a *non-static* field `B.F`, >> - `B` is

Re: RFR: 8293980: Resolve CONSTANT_FieldRef at CDS dump time [v3]

2024-05-29 Thread Dan Heidinga
On Wed, 29 May 2024 16:03:35 GMT, Ioi Lam wrote: > We could walk `_resolved_field_entries` to find the `ResolvedFieldEntry` > whose `_cpool_index` is `123`. However, before the `ResolvedFieldEntry` is > resolved, we don't know which bytecode is used to resolve it, so we don't > know whether it

Re: RFR: 8293980: Resolve CONSTANT_FieldRef at CDS dump time [v3]

2024-05-31 Thread Dan Heidinga
On Fri, 31 May 2024 00:22:37 GMT, Ioi Lam wrote: >>> We could walk `_resolved_field_entries` to find the `ResolvedFieldEntry` >>> whose `_cpool_index` is `123`. However, before the `ResolvedFieldEntry` is >>> resolved, we don't know which bytecode is used to resolve it, so we don't >>> know wh

Re: RFR: 8293980: Resolve CONSTANT_FieldRef at CDS dump time [v3]

2024-06-06 Thread Dan Heidinga
On Mon, 3 Jun 2024 19:13:54 GMT, Ioi Lam wrote: >> This makes sense. I will try to prototype it in the Leyden repo and then >> update this PR. > > I tried skipping the `methodHandle` parameter to > `InterpreterRuntime::resolve_get_put` but it's more complicated than I > thought. > > 1. The `f

Re: RFR: 8293980: Resolve CONSTANT_FieldRef at CDS dump time [v5]

2024-06-06 Thread Dan Heidinga
On Mon, 3 Jun 2024 21:23:59 GMT, Ioi Lam wrote: >> ### Overview >> >> This PR archives `CONSTANT_FieldRef` entries in the _resolved_ state when >> it's safe to do so. >> >> I.e., when a `CONSTANT_FieldRef` constant pool entry in class `A` refers to >> a *non-static* field `B.F`, >> - `B` is

Re: RFR: 8355003: Implement JEP 515: Ahead-of-Time Method Profiling [v15]

2025-05-12 Thread Dan Heidinga
On Mon, 12 May 2025 19:29:18 GMT, Igor Veresov wrote: >> Improve warm-up time by making profile data from a previous run of an >> application instantly available, when the HotSpot Java Virtual Machine >> starts. Specifically, enhance the [AOT cache](https://openjdk.org/jeps/483) >> to store me

Re: RFR: 8355798: Implement JEP 514: Ahead-of-Time Command Line Ergonomics [v7]

2025-05-13 Thread Dan Heidinga
On Tue, 13 May 2025 03:06:44 GMT, Ioi Lam wrote: >> This is the implementation of the draft [JEP: Ahead-of-time Command Line >> Ergonomics](https://bugs.openjdk.org/browse/JDK-8350022) >> >> - Implemented new flag `AOTCacheOutput`, which can be used to create an AOT >> cache using the "one-com