RFR 8152065: TraceBytecodes breaks the interpreter expression stack

Coleen Phillimore coleen.phillimore at oracle.com
Fri Mar 18 18:53:08 UTC 2016


Thanks, Jiangli!
Coleen

On 3/18/16 1:53 PM, Jiangli Zhou wrote:
> Hi Coleen,
>
> Thank you for the answers.
>
> Thanks,
> Jiangli
>
>> On Mar 18, 2016, at 5:18 AM, Coleen Phillimore <coleen.phillimore at oracle.com> wrote:
>>
>>
>> Thank you, Jiangli!  I answered the JRT_LEAF question in my reply to David.
>> Coleen
>>
>> On 3/17/16 8:08 PM, Jiangli Zhou wrote:
>>> Hi Coleen,
>>>
>>> This looks like a safe fix, but I probably can’t serve as a very good reviewer for this area. I have a question. Would ‘JRT_LEAF’ work also in this case?
>>>
>>> Thanks,
>>> Jiangli
>>>
>>>> On Mar 17, 2016, at 2:39 PM, Coleen Phillimore <coleen.phillimore at oracle.com> wrote:
>>>>
>>>> Summary: Move trace_bytecode to InterpreterRuntime and make trace_bytecode an IRT_LEAF so that safepoints are not allowed.
>>>>
>>>> open webrev at http://cr.openjdk.java.net/~coleenp/8152065.01/webrev
>>>> bug link https://bugs.openjdk.java.net/browse/JDK-8152065
>>>>
>>>> Tested with test program for bug https://bugs.openjdk.java.net/browse/JDK-8151256 and runThese with -XX:+TraceBytecodes for a few minutes (output file got too big).
>>>>
>>>> Thanks,
>>>> Coleen



More information about the hotspot-runtime-dev mailing list