RFR: 8216262: Remove develop flag DelayCompilationDuringStartup

Vladimir Kozlov vladimir.kozlov at oracle.com
Tue Jan 8 06:27:24 UTC 2019

This mechanism was added before I joined the team. I see that it is present from day one.
I speculate it was added to avoid allocating CPU (very limited at that time) cycles to compilation during VM startup.
I agree that currently it is not the case since we have enough cyles and need to compile MHs very eagerly.
JVMCI has other mechanism which delay compilation until it is initialized.
And I don't think we should delay usage of AOT code.

In short - I agree with changes and removal this archaic feature.
I would suggest immediate removal (or shortest available).


On 1/7/19 4:36 AM, Claes Redestad wrote:
> Hi,
> DelayCompilationAtStartup doesn't delay any compilations.
> Webrev: http://cr.openjdk.java.net/~redestad/8216262/open.00/
> Bug:    https://bugs.openjdk.java.net/browse/JDK-8216262
> Testing: tier1
> Thanks!
> /Claes

More information about the hotspot-compiler-dev mailing list