RFR JDK-8232222: Set state to 'linked' when an archived class is restored at runtime
ioi.lam at oracle.com
Wed Jun 3 04:34:22 UTC 2020
Before we spend time on the CSR review, do you have any data that shows
the actual benefit of doing this? I am specifically asking about the
benefit to JVMTI agents.
As I mentioned before, there's an alternative, which is to not use the
optimization when JVMTI is enabled. I don't think we should spend time
worrying about the impact to JVMTI agents unless there's a compelling
reasons to do so.
On 6/2/20 5:19 PM, Jiangli Zhou wrote:
> Here is the CSR: https://bugs.openjdk.java.net/browse/JDK-8246289.
> David, I described that the JVM spec allows for eager or lazy linking
> and agents shouldn't rely on the timing/ordering, as you suggested.
> Please review the CSR. It's been a while since I've worked on a CSR,
> could you please remind me if the CSR should be proposed before
> reviewing? I can revert it to draft state if draft is the correct
> state before reviewing. Thanks!
> Best regards,
More information about the hotspot-runtime-dev