[14]RFR: 8227439: Turn off AOT by default
Gustavo Romero
gromero at linux.vnet.ibm.com
Mon Jul 22 13:14:50 UTC 2019
Hi Claes,
On 07/22/2019 08:40 AM, Claes Redestad wrote:
> Hi,
>
> On 2019-07-19 23:27, Gustavo Romero wrote:
>> Hi,
>>
>> On 07/19/2019 01:32 PM, Igor Ignatyev wrote:
>>> thanks for taking care of this and all the tests, appreciate that. As UseAOT used to be true by default, you should add to all places where AOTLibrary is used, e.g. in make/RunTests.gmk, and as it seems like an easy error (for our users) to make, I think we need to check that AOTLibrary has value only if UseAOT is true and generate an error at initialization time if it's not a case. this will help us and all the users to spot places where AOT was expected to kick in.
>>
>> I just would like to understand better that decision.
>>
>> JEP says (I assume since its beginning) that AOT was experimental,
>> but then it was turned on by default and now turned off by default.
>>
>> Is it (turn it off by default on 14) only because AOT should always
>> be as experimental and turned off by default or it reflects some
>> shift on plans to support AOT in the future?
>
> as filer of this bug, my view is that it is simply righting a wrong:
> AOT was (and is) experimental and should have been disabled by default
> and guarded by -XX:+UnlockExperimentalVMOptions from the start. As such
> this bug is not a statement about any current or future plans to support
> JEP 295.
Thanks for clarifying.
Best regards,
Gustavo
More information about the hotspot-compiler-dev
mailing list