←back to thread

JEP draft: Prepare to make final mean final

(openjdk.org)
204 points mfiguiere | 1 comments | 31 Mar 25 19:35 UTC | HN request time: 0.204s | source
Show context
nightpool ◴[31 Mar 25 21:22 UTC] No.43540125[source]▶

    [Speculative optimizations] may not suffice in this case as future planned optimizations may wish to rely not only on immutability within the lifetime of the process, but also on the immutability of fields from one run of the application to the next.
Can someone elaborate a little more on what this means? I'm very surprised to hear that this was considered a blocker important enough to add all of this complicated machinery (and breaking several deserialization libraries...), when I've never even heard of such an optimization and can't imagine what sort of form it would take
replies(3): >>43540170 #>>43540492 #>>43540608 #
1. pron ◴[31 Mar 25 22:08 UTC] No.43540492[source]▶
There's ongoing work, as part of Project Leyden, to cache certain computations -- either performed by the user code or the JVM -- from one run of the program to the next, including the caching of JIT-compiled machine code. The early parts of this work were discussed here: https://www.morling.dev/blog/jep-483-aot-class-loading-linki...