RFR: 8216262: Remove develop flag DelayCompilationDuringStartup

Claes Redestad claes.redestad at oracle.com
Mon Jan 7 13:31:42 UTC 2019



On 2019-01-07 14:01, Claes Redestad wrote:
>>
>> Normally we would follow a staged removal process: deprecate, 
>> obsolete, then expire - see arguments.cpp and special_jvm_flags table. 
>> In this case we can probably start at obsoletion, but that would leave 
>> expiration for JDK 14. Or compiler folk can argue for / justify 
>> immediate full expiration/removal.
> 
> I'm under the impression this process does not apply to develop flags
> (which are not visible an anything but debug builds)?

We've removed develop flags without obsoletion + expiry many times in
the past[1], and while this goes against the written down expiration
in arguments.cpp, I believe it to be a misguided recommendation for
develop flags.

/Claes

[1]
https://bugs.openjdk.java.net/browse/JDK-8191870
https://bugs.openjdk.java.net/browse/JDK-8132318
https://bugs.openjdk.java.net/browse/JDK-8186042
https://bugs.openjdk.java.net/browse/JDK-8180423
https://bugs.openjdk.java.net/browse/JDK-8058259


More information about the hotspot-compiler-dev mailing list