[11] RFR(S) 8195632: [Graal] Introduce EagerJVMCI flag to force eager JVMCI initialization

Vladimir Kozlov vladimir.kozlov at oracle.com
Thu Mar 1 17:00:44 UTC 2018


Thank you, Tobias

Vladimir

On 2/28/18 11:35 PM, Tobias Hartmann wrote:
> Hi Vladimir,
> 
> looks good, thanks for updating!
> 
> Best regards,
> Tobias
> 
> On 01.03.2018 03:12, Vladimir Kozlov wrote:
>> Update: http://cr.openjdk.java.net/~kvn/8195632/webrev.01/
>>
>> Added EagerJVMCI to 3 failed test. Flag check code in jvmci_globals.cpp was modified to allow
>> specify this flag when JVMCI is disable.
>>
>> Ran 3 test with all combinations of JVMCI flags.
>>
>> Thanks,
>> Vladimir
>>
>> On 2/28/18 9:32 AM, Vladimir Kozlov wrote:
>>> On 2/28/18 5:30 AM, Tobias Hartmann wrote:
>>>> Hi Vladimir,
>>>>
>>>> looks good to me. Why not already add that flag to the failing tests?
>>>
>>> Right, we should. I asked Katya to provide list. 3 listed tests are not all failed tests as I
>>> understand.
>>>
>>> I will re-post RFR when I update tests.
>>>
>>> Thanks,
>>> Vladimir
>>>
>>>>
>>>> Best regards,
>>>> Tobias
>>>>
>>>> On 28.02.2018 02:56, Vladimir Kozlov wrote:
>>>>> http://cr.openjdk.java.net/~kvn/8195632/webrev.00/
>>>>> https://bugs.openjdk.java.net/browse/JDK-8195632
>>>>>
>>>>> Added flag and tested it with listed in bug tests.
>>>>>
>>>>> Thanks,
>>>>> Vladimir


More information about the hotspot-compiler-dev mailing list