HotspotProfilingInfo for xxx-morphic inlining

Doug Simon doug.simon at oracle.com
Mon May 12 21:38:03 UTC 2014


On May 12, 2014, at 11:14 PM, Deneau, Tom <tom.deneau at amd.com> wrote:

> Doug --
> 
> Not sure if I am reading ProfilingInfoTest correctly but it seems to only execute methods 10 times?
>    private static final int N = 10;

Ah yes, I see that we force creation of a profile there with a call to ResolvedJavaMethod.reprofile(). This is another option you can use in a test scenario but is probably best avoid for non-test code.

> Anyway, in my case bumping up to 10000 did get us past the no profiling info point.

Great.

-Doug

>> -----Original Message-----
>> From: Doug Simon [mailto:doug.simon at oracle.com]
>> Sent: Monday, May 12, 2014 3:32 PM
>> To: Deneau, Tom
>> Cc: graal-dev at openjdk.java.net
>> Subject: Re: HotspotProfilingInfo for xxx-morphic inlining
>> 
>> 
>> On May 12, 2014, at 9:35 PM, Deneau, Tom <tom.deneau at amd.com> wrote:
>> 
>>> I am interested in getting HotspotProfilingInfo for a method that we
>> will be compiling in the HSAIL backend.
>>> (after running the method on the cpu first to get profiling info)
>> 
>> You have to ensure the method has been run enough for the interpreter to
>> create a profile for a method. Usually, executing it about 10000 times
>> is a sure thing. For more info, see ProfilingInfoTest.
>> 
>>> When I get to HotSpotResolvedJavaMethod.getProfilingInfo, the
>> metaspaceMethodData is always 0 and methodData is always null, so we get
>> DefaultProfilingInfo instead.
>>> 
>>> I am using
>>>   -XX:TypeProfileWidth=3 -
>> G:MegamorphicInliningMinMethodProbability=0.001
>>> 
>>> and my OptimisticOptimizations include UseTypedCheckInlining and
>> UseTypeCheckHints.
>>> 
>>> Is there some hotspot or graal option I am missing?
>> 
>> -Doug



More information about the graal-dev mailing list