RFR(S): 8139703 - compiler/jvmci/compilerToVM/MaterializeVirtualObjectTest fails using -Xcomp
Christian Thalinger
christian.thalinger at oracle.com
Thu May 12 18:39:00 UTC 2016
Kind of off-topic but could we move all compilerToVM tests into an mx controlled directory, jdk.vm.ci.hotspot.test?
> On May 12, 2016, at 6:45 AM, dmitrij pochepko <dmitrij.pochepko at oracle.com> wrote:
>
> Thank you!
>> Good.
>>
>> Thanks,
>> Vladimir
>>
>> On 5/12/16 8:26 AM, Dmitrij Pochepko wrote:
>>> Hi,
>>>
>>> I've changed compilation threshold according to previous discussions.
>>>
>>> please take a look at v02: http://cr.openjdk.java.net/~dpochepk/8139703/webrev.02/
>>>
>>> Thanks,
>>> Dmitrij
>>>
>>>> As we discussed in previous reviews CompilerWhiteBoxTest.THRESHOLD may be not enough to trigger compilation.
>>>>
>>>> Thanks,
>>>> Vladimir
>>>>
>>>> On 3/2/16 7:44 AM, Dmitrij Pochepko wrote:
>>>>> Hi,
>>>>>
>>>>> please review fix for https://bugs.openjdk.java.net/browse/JDK-8139703 - [TESTBUG]
>>>>> compiler/jvmci/compilerToVM/MaterializeVirtualObjectTest fails using -Xcomp
>>>>>
>>>>> A test compiler/jvmci/compilerToVM/MaterializeVirtualObjectTest failed in Xcomp. After investigation, a bug related to
>>>>> escape analysis was filed(https://bugs.openjdk.java.net/browse/JDK-8140018).
>>>>>
>>>>> So, i've switched this test to use Xmixed mode. Also, this test was changed to trigger method compilation by calling
>>>>> method multiple times instead of using WhiteBox.
>>>>>
>>>>> CR: https://bugs.openjdk.java.net/browse/JDK-8139703
>>>>> webrev: http://cr.openjdk.java.net/~dpochepk/8139703/webrev.01/
>>>>>
>>>>> Thanks,
>>>>> Dmitrij
>>>
>
More information about the hotspot-compiler-dev
mailing list