RFR(S): 8007144: Incremental inlining mistakes some call sites for dead ones and doesn't inline them

[Vladimir Kozlov]

Let me look on this. The question only about optimized case.

Vladimir

On 2/1/13 2:38 AM, Roland Westrelin wrote:
>
>>> What should PrintInlining do when the string operations are optimized? Should it print anything?
>>
>> Could you tell what currently happens (what PrintInlining output)?
>
> Either it is optimized and it's reported as;
>
>                              @ 54   java.lang.StringBuilder::append (8 bytes)   inline (hot)
>
> or if it's inlined:
>
>                              @ 140   java.lang.StringBuilder::append (8 bytes)   inline (hot)
>                                @ 2   java.lang.AbstractStringBuilder::append (29 bytes)   inline (hot)
>                                  @ 7   java.lang.AbstractStringBuilder::ensureCapacityInternal (16 bytes)   inline (hot)
>                                    @ 12   java.lang.AbstractStringBuilder::expandCapacity (50 bytes)   inline (hot)
>                                      @ 43   java.util.Arrays::copyOf (19 bytes)   inline (hot)
>                                        @ 11   java.lang.Math::min (11 bytes)   (intrinsic)
>
> Roland.
>