RFR 8038418 New tests development for type profiling and speculation

[Igor Ignatyev]

Hi Roland,

>> Using your own class loaders should. The call to set_arg_modified() itself doesn’t affect type profiling.
unfortunately, it's hard to use new class loaders for all scenarios in 
our current design, so it's not enough, what's why we decided to use WB 
API to clear method state.

is there any way to clear type profiling data? could please you point me 
to the code where type profiling is stored? I'll add clearing type 
profiling data to WB:clearMethodState.

Thanks
Igor

On 04/09/2014 12:38 PM, Roland Westrelin wrote:
> Hi Igor,
>
>> No we use new class loader for each execution and clear state of all methods in scenario through WhiteBox::clearMethodState():
>>>   MethodData* mdo = mh->method_data();
>>>
>>>   if (mdo != NULL) {
>>>     mdo->init();
>>>     ResourceMark rm;
>>>     int arg_count = mdo->method()->size_of_parameters();
>>>     for (int i = 0; i < arg_count; i++) {
>>>       mdo->set_arg_modified(i, 0);
>>>     }
>>>   }
>> I think it should also clear type profiling data. Am I right?
>
> Using your own class loaders should. The call to set_arg_modified() itself doesn’t affect type profiling.
>
> Roland.
>